commit 49ac3254fe4f07d0b7adc2ded9c30565c0a36f86
Author: Jaromir Hradilek <jhradile(a)redhat.com>
Date: Tue May 24 16:53:48 2011 +0200
Added the Deployment Guide.
fedoradocs.db | Bin 521216 -> 521216 bytes
public_html/Sitemap | 42 +-
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.xml | 10 +-
public_html/as-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/bg-BG/toc.html | 20 +-
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.xml | 10 +-
public_html/bn-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/bs-BA/toc.html | 20 +-
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.xml | 10 +-
public_html/ca-ES/toc.html | 16 +-
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.xml | 10 +-
public_html/cs-CZ/toc.html | 20 +-
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.xml | 10 +-
public_html/da-DK/toc.html | 20 +-
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.xml | 10 +-
public_html/de-DE/toc.html | 16 +-
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.xml | 10 +-
public_html/el-GR/toc.html | 20 +-
.../Deployment_Guide/Common_Content/css/common.css | 1495 ++
.../Common_Content/css/default.css | 3 +
.../Deployment_Guide/Common_Content/css/lang.css | 2 +
.../Common_Content/css/overrides.css | 51 +
.../Deployment_Guide/Common_Content/css/print.css | 16 +
.../Deployment_Guide/Common_Content/images/1.png | Bin 0 -> 710 bytes
.../Deployment_Guide/Common_Content/images/1.svg | 27 +
.../Deployment_Guide/Common_Content/images/10.png | Bin 0 -> 985 bytes
.../Deployment_Guide/Common_Content/images/10.svg | 31 +
.../Deployment_Guide/Common_Content/images/11.png | Bin 0 -> 810 bytes
.../Deployment_Guide/Common_Content/images/11.svg | 31 +
.../Deployment_Guide/Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../Deployment_Guide/Common_Content/images/12.svg | 31 +
.../Deployment_Guide/Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../Deployment_Guide/Common_Content/images/13.svg | 31 +
.../Deployment_Guide/Common_Content/images/14.png | Bin 0 -> 914 bytes
.../Deployment_Guide/Common_Content/images/14.svg | 31 +
.../Deployment_Guide/Common_Content/images/15.png | Bin 0 -> 989 bytes
.../Deployment_Guide/Common_Content/images/15.svg | 31 +
.../Deployment_Guide/Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../Deployment_Guide/Common_Content/images/16.svg | 31 +
.../Deployment_Guide/Common_Content/images/17.png | Bin 0 -> 888 bytes
.../Deployment_Guide/Common_Content/images/17.svg | 31 +
.../Deployment_Guide/Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../Deployment_Guide/Common_Content/images/18.svg | 31 +
.../Deployment_Guide/Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../Deployment_Guide/Common_Content/images/19.svg | 31 +
.../Deployment_Guide/Common_Content/images/2.png | Bin 0 -> 896 bytes
.../Deployment_Guide/Common_Content/images/2.svg | 27 +
.../Deployment_Guide/Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../Deployment_Guide/Common_Content/images/20.svg | 31 +
.../Deployment_Guide/Common_Content/images/21.png | Bin 0 -> 994 bytes
.../Deployment_Guide/Common_Content/images/21.svg | 31 +
.../Deployment_Guide/Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../Deployment_Guide/Common_Content/images/22.svg | 31 +
.../Deployment_Guide/Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../Deployment_Guide/Common_Content/images/23.svg | 31 +
.../Deployment_Guide/Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../Deployment_Guide/Common_Content/images/24.svg | 31 +
.../Deployment_Guide/Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../Deployment_Guide/Common_Content/images/25.svg | 31 +
.../Deployment_Guide/Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../Deployment_Guide/Common_Content/images/26.svg | 31 +
.../Deployment_Guide/Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../Deployment_Guide/Common_Content/images/27.svg | 31 +
.../Deployment_Guide/Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../Deployment_Guide/Common_Content/images/28.svg | 31 +
.../Deployment_Guide/Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../Deployment_Guide/Common_Content/images/29.svg | 31 +
.../Deployment_Guide/Common_Content/images/3.png | Bin 0 -> 958 bytes
.../Deployment_Guide/Common_Content/images/3.svg | 27 +
.../Deployment_Guide/Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../Deployment_Guide/Common_Content/images/30.svg | 31 +
.../Deployment_Guide/Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../Deployment_Guide/Common_Content/images/31.svg | 31 +
.../Deployment_Guide/Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../Deployment_Guide/Common_Content/images/32.svg | 31 +
.../Deployment_Guide/Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../Deployment_Guide/Common_Content/images/33.svg | 31 +
.../Deployment_Guide/Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../Deployment_Guide/Common_Content/images/34.svg | 31 +
.../Deployment_Guide/Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../Deployment_Guide/Common_Content/images/35.svg | 31 +
.../Deployment_Guide/Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../Deployment_Guide/Common_Content/images/36.svg | 31 +
.../Deployment_Guide/Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../Deployment_Guide/Common_Content/images/37.svg | 31 +
.../Deployment_Guide/Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../Deployment_Guide/Common_Content/images/38.svg | 31 +
.../Deployment_Guide/Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../Deployment_Guide/Common_Content/images/39.svg | 31 +
.../Deployment_Guide/Common_Content/images/4.png | Bin 0 -> 849 bytes
.../Deployment_Guide/Common_Content/images/4.svg | 27 +
.../Deployment_Guide/Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../Deployment_Guide/Common_Content/images/40.svg | 31 +
.../Deployment_Guide/Common_Content/images/5.png | Bin 0 -> 900 bytes
.../Deployment_Guide/Common_Content/images/5.svg | 27 +
.../Deployment_Guide/Common_Content/images/6.png | Bin 0 -> 929 bytes
.../Deployment_Guide/Common_Content/images/6.svg | 27 +
.../Deployment_Guide/Common_Content/images/7.png | Bin 0 -> 807 bytes
.../Deployment_Guide/Common_Content/images/7.svg | 27 +
.../Deployment_Guide/Common_Content/images/8.png | Bin 0 -> 962 bytes
.../Deployment_Guide/Common_Content/images/8.svg | 27 +
.../Deployment_Guide/Common_Content/images/9.png | Bin 0 -> 936 bytes
.../Deployment_Guide/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
.../Deployment_Guide/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 -> 2260 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 +
.../Deployment_Guide/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
.../Network_Configuration-NM-All_applet_states.png | Bin 0 -> 11632 bytes
...ork_Configuration-NM-Available_to_all_users.png | Bin 0 -> 5259 bytes
...etwork_Configuration-NM-Network_Connections.png | Bin 0 -> 22093 bytes
.../Network_Configuration-NM-left-click_menu.png | Bin 0 -> 31181 bytes
.../Network_Configuration-NM-right-click_menu.png | Bin 0 -> 9678 bytes
.../Deployment_Guide/images/abrt-alert.png | Bin 0 -> 4424 bytes
.../images/abrt-event-configuration.png | Bin 0 -> 24847 bytes
.../html-single/Deployment_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-panel.png | Bin 0 -> 48154 bytes
.../images/date-and-time-settings.png | Bin 0 -> 144513 bytes
.../Deployment_Guide/images/devicemngr.png | Bin 0 -> 55542 bytes
.../Deployment_Guide/images/gnome-print-queue.png | Bin 0 -> 84139 bytes
.../Deployment_Guide/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
.../Deployment_Guide/images/oprof-start-config.png | Bin 0 -> 25828 bytes
.../Deployment_Guide/images/oprof-start-setup.png | Bin 0 -> 49050 bytes
.../Deployment_Guide/images/print_conf_window.png | Bin 0 -> 25792 bytes
.../images/printconf-add-printer.png | Bin 0 -> 25284 bytes
.../Deployment_Guide/images/printconf-config1.png | Bin 0 -> 38236 bytes
.../Deployment_Guide/images/printconf-config2.png | Bin 0 -> 36077 bytes
.../Deployment_Guide/images/printconf-config3.png | Bin 0 -> 24632 bytes
.../Deployment_Guide/images/printconf-config4.png | Bin 0 -> 158664 bytes
.../Deployment_Guide/images/printconf-config5.png | Bin 0 -> 58801 bytes
.../Deployment_Guide/images/printconf-config6.png | Bin 0 -> 29441 bytes
.../Deployment_Guide/images/printconf-ipp.png | Bin 0 -> 37555 bytes
.../images/printconf-jetdirect.png | Bin 0 -> 32516 bytes
.../Deployment_Guide/images/printconf-lpd.png | Bin 0 -> 36256 bytes
.../Deployment_Guide/images/printconf-main.png | Bin 0 -> 21965 bytes
.../images/printconf-select-driver.png | Bin 0 -> 35786 bytes
.../images/printconf-select-model.png | Bin 0 -> 38501 bytes
.../Deployment_Guide/images/printconf-smb.png | Bin 0 -> 48756 bytes
.../images/region-and-language-language.png | Bin 0 -> 106182 bytes
.../images/region-and-language-layouts-add.png | Bin 0 -> 35313 bytes
.../region-and-language-layouts-indicator.png | Bin 0 -> 20653 bytes
.../images/region-and-language-layouts.png | Bin 0 -> 93535 bytes
.../Deployment_Guide/images/s-c-samba-basic.png | Bin 0 -> 8169 bytes
.../images/s-c-samba-create-share.png | Bin 0 -> 12146 bytes
.../Deployment_Guide/images/s-c-samba-security.png | Bin 0 -> 16224 bytes
.../Deployment_Guide/images/s-c-samba-users.png | Bin 0 -> 5728 bytes
.../Deployment_Guide/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
.../Deployment_Guide/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
.../Deployment_Guide/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
.../Deployment_Guide/images/system-log-viewer.png | Bin 0 -> 88745 bytes
.../images/system-monitor-file-systems.png | Bin 0 -> 114637 bytes
.../images/system-monitor-processes.png | Bin 0 -> 162146 bytes
.../images/system-monitor-resources.png | Bin 0 -> 146129 bytes
.../images/user-accounts-create.png | Bin 0 -> 18774 bytes
.../images/user-accounts-password-change.png | Bin 0 -> 42623 bytes
.../images/user-accounts-remove.png | Bin 0 -> 25349 bytes
.../Deployment_Guide/images/user-accounts.png | Bin 0 -> 94029 bytes
.../images/user-manager-add-group.png | Bin 0 -> 8717 bytes
.../images/user-manager-add-user.png | Bin 0 -> 28869 bytes
.../images/user-manager-edit-group.png | Bin 0 -> 14060 bytes
.../images/user-manager-edit-user.png | Bin 0 -> 22514 bytes
.../Deployment_Guide/images/user-manager.png | Bin 0 -> 108608 bytes
.../15/html-single/Deployment_Guide/index.html |14653 ++++++++++++++++++++
.../Deployment_Guide/Common_Content/css/common.css | 1495 ++
.../Common_Content/css/default.css | 3 +
.../Deployment_Guide/Common_Content/css/lang.css | 2 +
.../Common_Content/css/overrides.css | 51 +
.../Deployment_Guide/Common_Content/css/print.css | 16 +
.../Deployment_Guide/Common_Content/images/1.png | Bin 0 -> 710 bytes
.../Deployment_Guide/Common_Content/images/1.svg | 27 +
.../Deployment_Guide/Common_Content/images/10.png | Bin 0 -> 985 bytes
.../Deployment_Guide/Common_Content/images/10.svg | 31 +
.../Deployment_Guide/Common_Content/images/11.png | Bin 0 -> 810 bytes
.../Deployment_Guide/Common_Content/images/11.svg | 31 +
.../Deployment_Guide/Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../Deployment_Guide/Common_Content/images/12.svg | 31 +
.../Deployment_Guide/Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../Deployment_Guide/Common_Content/images/13.svg | 31 +
.../Deployment_Guide/Common_Content/images/14.png | Bin 0 -> 914 bytes
.../Deployment_Guide/Common_Content/images/14.svg | 31 +
.../Deployment_Guide/Common_Content/images/15.png | Bin 0 -> 989 bytes
.../Deployment_Guide/Common_Content/images/15.svg | 31 +
.../Deployment_Guide/Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../Deployment_Guide/Common_Content/images/16.svg | 31 +
.../Deployment_Guide/Common_Content/images/17.png | Bin 0 -> 888 bytes
.../Deployment_Guide/Common_Content/images/17.svg | 31 +
.../Deployment_Guide/Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../Deployment_Guide/Common_Content/images/18.svg | 31 +
.../Deployment_Guide/Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../Deployment_Guide/Common_Content/images/19.svg | 31 +
.../Deployment_Guide/Common_Content/images/2.png | Bin 0 -> 896 bytes
.../Deployment_Guide/Common_Content/images/2.svg | 27 +
.../Deployment_Guide/Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../Deployment_Guide/Common_Content/images/20.svg | 31 +
.../Deployment_Guide/Common_Content/images/21.png | Bin 0 -> 994 bytes
.../Deployment_Guide/Common_Content/images/21.svg | 31 +
.../Deployment_Guide/Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../Deployment_Guide/Common_Content/images/22.svg | 31 +
.../Deployment_Guide/Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../Deployment_Guide/Common_Content/images/23.svg | 31 +
.../Deployment_Guide/Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../Deployment_Guide/Common_Content/images/24.svg | 31 +
.../Deployment_Guide/Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../Deployment_Guide/Common_Content/images/25.svg | 31 +
.../Deployment_Guide/Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../Deployment_Guide/Common_Content/images/26.svg | 31 +
.../Deployment_Guide/Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../Deployment_Guide/Common_Content/images/27.svg | 31 +
.../Deployment_Guide/Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../Deployment_Guide/Common_Content/images/28.svg | 31 +
.../Deployment_Guide/Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../Deployment_Guide/Common_Content/images/29.svg | 31 +
.../Deployment_Guide/Common_Content/images/3.png | Bin 0 -> 958 bytes
.../Deployment_Guide/Common_Content/images/3.svg | 27 +
.../Deployment_Guide/Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../Deployment_Guide/Common_Content/images/30.svg | 31 +
.../Deployment_Guide/Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../Deployment_Guide/Common_Content/images/31.svg | 31 +
.../Deployment_Guide/Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../Deployment_Guide/Common_Content/images/32.svg | 31 +
.../Deployment_Guide/Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../Deployment_Guide/Common_Content/images/33.svg | 31 +
.../Deployment_Guide/Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../Deployment_Guide/Common_Content/images/34.svg | 31 +
.../Deployment_Guide/Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../Deployment_Guide/Common_Content/images/35.svg | 31 +
.../Deployment_Guide/Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../Deployment_Guide/Common_Content/images/36.svg | 31 +
.../Deployment_Guide/Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../Deployment_Guide/Common_Content/images/37.svg | 31 +
.../Deployment_Guide/Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../Deployment_Guide/Common_Content/images/38.svg | 31 +
.../Deployment_Guide/Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../Deployment_Guide/Common_Content/images/39.svg | 31 +
.../Deployment_Guide/Common_Content/images/4.png | Bin 0 -> 849 bytes
.../Deployment_Guide/Common_Content/images/4.svg | 27 +
.../Deployment_Guide/Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../Deployment_Guide/Common_Content/images/40.svg | 31 +
.../Deployment_Guide/Common_Content/images/5.png | Bin 0 -> 900 bytes
.../Deployment_Guide/Common_Content/images/5.svg | 27 +
.../Deployment_Guide/Common_Content/images/6.png | Bin 0 -> 929 bytes
.../Deployment_Guide/Common_Content/images/6.svg | 27 +
.../Deployment_Guide/Common_Content/images/7.png | Bin 0 -> 807 bytes
.../Deployment_Guide/Common_Content/images/7.svg | 27 +
.../Deployment_Guide/Common_Content/images/8.png | Bin 0 -> 962 bytes
.../Deployment_Guide/Common_Content/images/8.svg | 27 +
.../Deployment_Guide/Common_Content/images/9.png | Bin 0 -> 936 bytes
.../Deployment_Guide/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
.../Deployment_Guide/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 -> 2260 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 +
.../Deployment_Guide/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
.../15/html/Deployment_Guide/abrt-plugins.html | 22 +
.../Deployment_Guide/app-Revision_History.html | 16 +
.../ch-Automating_System_Tasks.html | 147 +
.../ch-Configuring_Authentication.html | 429 +
.../15/html/Deployment_Guide/ch-DHCP_Servers.html | 16 +
.../15/html/Deployment_Guide/ch-DNS_Servers.html | 38 +
.../ch-Date_and_Time_Configuration.html | 32 +
.../Deployment_Guide/ch-Directory_Servers.html | 485 +
.../ch-File_and_Print_Servers.html | 661 +
...ackage_Management-sec-Additional_Resources.html | 16 +
.../ch-Language_and_Keyboard_Configuration.html | 18 +
.../15/html/Deployment_Guide/ch-Mail_Servers.html | 98 +
.../ch-Managing_Users_and_Groups.html | 66 +
.../ch-Manually_Upgrading_the_Kernel.html | 40 +
.../Deployment_Guide/ch-Network_Interfaces.html | 38 +
.../15/html/Deployment_Guide/ch-OpenSSH.html | 96 +
.../15/html/Deployment_Guide/ch-PackageKit.html | 46 +
.../Fedora/15/html/Deployment_Guide/ch-RPM.html | 54 +
.../Deployment_Guide/ch-Services_and_Daemons.html | 34 +
.../ch-System_Monitoring_Tools.html | 117 +
.../ch-The_sysconfig_Directory.html | 336 +
.../ch-Viewing_and_Managing_Log_Files.html | 311 +
.../15/html/Deployment_Guide/ch-Web_Servers.html | 1280 ++
.../ch-Working_with_Kernel_Modules.html | 80 +
.../Fedora/15/html/Deployment_Guide/ch-abrt.html | 28 +
.../Fedora/15/html/Deployment_Guide/ch-kdump.html | 230 +
.../Fedora/15/html/Deployment_Guide/ch-proc.html | 65 +
.../Fedora/15/html/Deployment_Guide/ch-yum.html | 97 +
.../15/html/Deployment_Guide/ch10s02s03.html | 41 +
.../Fedora/15/html/Deployment_Guide/ch19s02.html | 30 +
.../Fedora/15/html/Deployment_Guide/ch19s05.html | 30 +
.../15/html/Deployment_Guide/ch19s05s02.html | 20 +
.../15/html/Deployment_Guide/ch19s05s03.html | 14 +
.../chap-SSSD_User_Guide-Configuring_Domains.html | 290 +
.../chap-SSSD_User_Guide-Configuring_Services.html | 74 +
.../chap-SSSD_User_Guide-Introduction.html | 18 +
.../chap-SSSD_User_Guide-Setting_Up_SSSD.html | 186 +
.../chap-SSSD_User_Guide-Troubleshooting.html | 122 +
.../configuring-automatic-reporting.html | 21 +
.../configuring-centralized-crash-collection.html | 58 +
.../configuring-plugins-in-the-gui.html | 60 +
.../15/html/Deployment_Guide/configuring.html | 51 +
.../15/html/Deployment_Guide/dhcp-relay-agent.html | 18 +
.../Deployment_Guide/generating-backtrace.html | 76 +
.../Network_Configuration-NM-All_applet_states.png | Bin 0 -> 11632 bytes
...ork_Configuration-NM-Available_to_all_users.png | Bin 0 -> 5259 bytes
...etwork_Configuration-NM-Network_Connections.png | Bin 0 -> 22093 bytes
.../Network_Configuration-NM-left-click_menu.png | Bin 0 -> 31181 bytes
.../Network_Configuration-NM-right-click_menu.png | Bin 0 -> 9678 bytes
.../15/html/Deployment_Guide/images/abrt-alert.png | Bin 0 -> 4424 bytes
.../images/abrt-event-configuration.png | Bin 0 -> 24847 bytes
.../15/html/Deployment_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-panel.png | Bin 0 -> 48154 bytes
.../images/date-and-time-settings.png | Bin 0 -> 144513 bytes
.../15/html/Deployment_Guide/images/devicemngr.png | Bin 0 -> 55542 bytes
.../Deployment_Guide/images/gnome-print-queue.png | Bin 0 -> 84139 bytes
.../15/html/Deployment_Guide/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
.../Deployment_Guide/images/oprof-start-config.png | Bin 0 -> 25828 bytes
.../Deployment_Guide/images/oprof-start-setup.png | Bin 0 -> 49050 bytes
.../Deployment_Guide/images/print_conf_window.png | Bin 0 -> 25792 bytes
.../images/printconf-add-printer.png | Bin 0 -> 25284 bytes
.../Deployment_Guide/images/printconf-config1.png | Bin 0 -> 38236 bytes
.../Deployment_Guide/images/printconf-config2.png | Bin 0 -> 36077 bytes
.../Deployment_Guide/images/printconf-config3.png | Bin 0 -> 24632 bytes
.../Deployment_Guide/images/printconf-config4.png | Bin 0 -> 158664 bytes
.../Deployment_Guide/images/printconf-config5.png | Bin 0 -> 58801 bytes
.../Deployment_Guide/images/printconf-config6.png | Bin 0 -> 29441 bytes
.../html/Deployment_Guide/images/printconf-ipp.png | Bin 0 -> 37555 bytes
.../images/printconf-jetdirect.png | Bin 0 -> 32516 bytes
.../html/Deployment_Guide/images/printconf-lpd.png | Bin 0 -> 36256 bytes
.../Deployment_Guide/images/printconf-main.png | Bin 0 -> 21965 bytes
.../images/printconf-select-driver.png | Bin 0 -> 35786 bytes
.../images/printconf-select-model.png | Bin 0 -> 38501 bytes
.../html/Deployment_Guide/images/printconf-smb.png | Bin 0 -> 48756 bytes
.../images/region-and-language-language.png | Bin 0 -> 106182 bytes
.../images/region-and-language-layouts-add.png | Bin 0 -> 35313 bytes
.../region-and-language-layouts-indicator.png | Bin 0 -> 20653 bytes
.../images/region-and-language-layouts.png | Bin 0 -> 93535 bytes
.../Deployment_Guide/images/s-c-samba-basic.png | Bin 0 -> 8169 bytes
.../images/s-c-samba-create-share.png | Bin 0 -> 12146 bytes
.../Deployment_Guide/images/s-c-samba-security.png | Bin 0 -> 16224 bytes
.../Deployment_Guide/images/s-c-samba-users.png | Bin 0 -> 5728 bytes
.../15/html/Deployment_Guide/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
.../Deployment_Guide/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
.../Deployment_Guide/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
.../Deployment_Guide/images/system-log-viewer.png | Bin 0 -> 88745 bytes
.../images/system-monitor-file-systems.png | Bin 0 -> 114637 bytes
.../images/system-monitor-processes.png | Bin 0 -> 162146 bytes
.../images/system-monitor-resources.png | Bin 0 -> 146129 bytes
.../images/user-accounts-create.png | Bin 0 -> 18774 bytes
.../images/user-accounts-password-change.png | Bin 0 -> 42623 bytes
.../images/user-accounts-remove.png | Bin 0 -> 25349 bytes
.../html/Deployment_Guide/images/user-accounts.png | Bin 0 -> 94029 bytes
.../images/user-manager-add-group.png | Bin 0 -> 8717 bytes
.../images/user-manager-add-user.png | Bin 0 -> 28869 bytes
.../images/user-manager-edit-group.png | Bin 0 -> 14060 bytes
.../images/user-manager-edit-user.png | Bin 0 -> 22514 bytes
.../html/Deployment_Guide/images/user-manager.png | Bin 0 -> 108608 bytes
.../Fedora/15/html/Deployment_Guide/index.html | 35 +
.../Fedora/15/html/Deployment_Guide/ix01.html | 10 +
.../15/html/Deployment_Guide/lease-database.html | 18 +
.../part-Basic_System_Configuration.html | 12 +
.../part-Infrastructure_Services.html | 12 +
...art-Kernel_Module_and_Driver_Configuration.html | 12 +
.../part-Monitoring_and_Automation.html | 12 +
.../15/html/Deployment_Guide/part-Networking.html | 12 +
.../Deployment_Guide/part-Package_Management.html | 12 +
.../15/html/Deployment_Guide/part-Servers.html | 12 +
.../Fedora/15/html/Deployment_Guide/pr01.html | 26 +
.../Fedora/15/html/Deployment_Guide/pr01s03.html | 62 +
.../15/html/Deployment_Guide/pr01s03s02.html | 35 +
.../15/html/Deployment_Guide/pr01s03s03.html | 18 +
.../Deployment_Guide/pref-Acknowledgments.html | 14 +
.../15/html/Deployment_Guide/reporter-plugins.html | 20 +
.../Fedora/15/html/Deployment_Guide/s1-BIND.html | 338 +
.../Fedora/15/html/Deployment_Guide/s1-FTP.html | 26 +
.../s1-autotasks-additional-resources.html | 24 +
.../Deployment_Guide/s1-autotasks-at-batch.html | 42 +
.../15/html/Deployment_Guide/s1-check-rpm-sig.html | 38 +
.../s1-dhcp-additional-resources.html | 24 +
.../s1-dhcp-configuring-client.html | 30 +
.../s1-dhcp-configuring-server.html | 111 +
.../Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html | 24 +
.../s1-email-additional-resources.html | 36 +
.../15/html/Deployment_Guide/s1-email-mda.html | 64 +
.../15/html/Deployment_Guide/s1-email-mta.html | 79 +
.../15/html/Deployment_Guide/s1-email-mua.html | 62 +
.../15/html/Deployment_Guide/s1-email-types.html | 22 +
.../15/html/Deployment_Guide/s1-kdump-crash.html | 65 +
.../html/Deployment_Guide/s1-kdump-resources.html | 20 +
.../Deployment_Guide/s1-kernel-boot-loader.html | 87 +
.../html/Deployment_Guide/s1-kernel-download.html | 18 +
.../s1-kernel-modules-additional-resources.html | 30 +
.../s1-kernel-perform-upgrade.html | 19 +
.../html/Deployment_Guide/s1-kernel-preparing.html | 56 +
.../s1-log-files-additional-resources.html | 20 +
.../html/Deployment_Guide/s1-logfiles-adding.html | 18 +
.../Deployment_Guide/s1-logfiles-examining.html | 14 +
.../Deployment_Guide/s1-logfiles-locating.html | 79 +
.../html/Deployment_Guide/s1-logfiles-viewing.html | 50 +
.../s1-networkscripts-control.html | 50 +
.../s1-networkscripts-functions.html | 16 +
.../s1-networkscripts-interfaces.html | 105 +
.../s1-networkscripts-resources.html | 16 +
.../s1-networkscripts-static-routes.html | 55 +
.../s1-openssh-additional-resources.html | 26 +
.../s1-proc-additional-resources.html | 24 +
.../html/Deployment_Guide/s1-proc-directories.html | 119 +
.../15/html/Deployment_Guide/s1-proc-sysctl.html | 31 +
.../15/html/Deployment_Guide/s1-proc-topfiles.html | 24 +
.../s1-rpm-additional-resources.html | 16 +
.../html/Deployment_Guide/s1-rpm-impressing.html | 88 +
.../15/html/Deployment_Guide/s1-rpm-using.html | 32 +
.../s1-services-additional-resources.html | 12 +
.../html/Deployment_Guide/s1-services-running.html | 61 +
.../html/Deployment_Guide/s1-ssh-beyondshell.html | 23 +
.../15/html/Deployment_Guide/s1-ssh-clients.html | 35 +
.../Deployment_Guide/s1-ssh-configuration.html | 96 +
.../s1-sysconfig-additional-resources.html | 14 +
.../s1-sysconfig-etcsysconf-dir.html | 31 +
.../s1-sysinfo-additional-resources.html | 27 +
.../Deployment_Guide/s1-sysinfo-filesystems.html | 42 +
.../html/Deployment_Guide/s1-sysinfo-hardware.html | 20 +
.../Deployment_Guide/s1-sysinfo-memory-usage.html | 24 +
.../html/Deployment_Guide/s1-users-configui.html | 56 +
.../s1-users-groups-additional-resources.html | 44 +
.../s1-users-groups-private-groups.html | 32 +
.../s1-users-groups-shadow-utilities.html | 32 +
.../s1-users-groups-standard-groups.html | 390 +
.../s1-users-groups-standard-users.html | 1502 ++
.../15/html/Deployment_Guide/s1-users-tools.html | 181 +
.../s2-autotasks-at-batch-controlling-access.html | 18 +
.../s2-autotasks-at-batch-service.html | 18 +
.../s2-autotasks-at-batch-viewing.html | 12 +
.../s2-autotasks-batch-configuring.html | 20 +
.../s2-autotasks-commandline-options.html | 28 +
.../s2-bind-additional-resources.html | 42 +
.../15/html/Deployment_Guide/s2-bind-dig.html | 97 +
.../15/html/Deployment_Guide/s2-bind-features.html | 36 +
.../15/html/Deployment_Guide/s2-bind-mistakes.html | 22 +
.../15/html/Deployment_Guide/s2-bind-rndc.html | 89 +
.../15/html/Deployment_Guide/s2-bind-zone.html | 256 +
.../Deployment_Guide/s2-email-mta-fetchmail.html | 116 +
.../Deployment_Guide/s2-email-mta-sendmail.html | 118 +
.../s2-email-procmail-recipes.html | 141 +
.../Deployment_Guide/s2-email-related-books.html | 20 +
.../html/Deployment_Guide/s2-email-switchmail.html | 16 +
.../html/Deployment_Guide/s2-email-types-mda.html | 14 +
.../html/Deployment_Guide/s2-email-types-mua.html | 14 +
.../Deployment_Guide/s2-email-useful-websites.html | 26 +
.../15/html/Deployment_Guide/s2-ftp-resources.html | 28 +
.../15/html/Deployment_Guide/s2-ftp-servers.html | 36 +
.../html/Deployment_Guide/s2-ftp-vsftpd-conf.html | 338 +
.../html/Deployment_Guide/s2-ftp-vsftpd-start.html | 34 +
.../Deployment_Guide/s2-kdump-crash-backtrace.html | 35 +
.../html/Deployment_Guide/s2-kdump-crash-exit.html | 13 +
.../Deployment_Guide/s2-kdump-crash-files.html | 22 +
.../html/Deployment_Guide/s2-kdump-crash-log.html | 37 +
.../Deployment_Guide/s2-kdump-crash-memory.html | 40 +
.../Deployment_Guide/s2-kdump-crash-processes.html | 25 +
.../s2-kdump-resources-online.html | 12 +
.../s2-kernel-boot-loader-iseries.html | 20 +
.../s2-kernel-boot-loader-pseries.html | 27 +
...rnel-modules-additional-resources-websites.html | 12 +
.../15/html/Deployment_Guide/s2-keys-checking.html | 18 +
.../s2-log-files-useful-websites.html | 14 +
.../s2-networkscripts-interfaces-alias.html | 28 +
.../s2-networkscripts-interfaces-chan.html | 41 +
.../s2-networkscripts-interfaces-other.html | 20 +
.../s2-networkscripts-interfaces-ppp0.html | 74 +
.../s2-openssh-useful-websites.html | 16 +
.../15/html/Deployment_Guide/s2-proc-cmdline.html | 22 +
.../15/html/Deployment_Guide/s2-proc-cpuinfo.html | 48 +
.../15/html/Deployment_Guide/s2-proc-crypto.html | 23 +
.../15/html/Deployment_Guide/s2-proc-devices.html | 47 +
.../15/html/Deployment_Guide/s2-proc-dir-bus.html | 34 +
.../html/Deployment_Guide/s2-proc-dir-driver.html | 32 +
.../15/html/Deployment_Guide/s2-proc-dir-fs.html | 12 +
.../15/html/Deployment_Guide/s2-proc-dir-irq.html | 18 +
.../15/html/Deployment_Guide/s2-proc-dir-net.html | 54 +
.../15/html/Deployment_Guide/s2-proc-dir-scsi.html | 97 +
.../15/html/Deployment_Guide/s2-proc-dir-sys.html | 333 +
.../html/Deployment_Guide/s2-proc-dir-sysvipc.html | 12 +
.../15/html/Deployment_Guide/s2-proc-dma.html | 14 +
.../html/Deployment_Guide/s2-proc-execdomains.html | 16 +
.../15/html/Deployment_Guide/s2-proc-fb.html | 14 +
.../html/Deployment_Guide/s2-proc-filesystems.html | 38 +
.../html/Deployment_Guide/s2-proc-interrupts.html | 50 +
.../15/html/Deployment_Guide/s2-proc-iomem.html | 30 +
.../15/html/Deployment_Guide/s2-proc-ioports.html | 38 +
.../15/html/Deployment_Guide/s2-proc-kcore.html | 16 +
.../15/html/Deployment_Guide/s2-proc-kmsg.html | 12 +
.../15/html/Deployment_Guide/s2-proc-loadavg.html | 18 +
.../15/html/Deployment_Guide/s2-proc-locks.html | 24 +
.../15/html/Deployment_Guide/s2-proc-mdstat.html | 22 +
.../15/html/Deployment_Guide/s2-proc-meminfo.html | 88 +
.../15/html/Deployment_Guide/s2-proc-misc.html | 16 +
.../15/html/Deployment_Guide/s2-proc-modules.html | 41 +
.../15/html/Deployment_Guide/s2-proc-mounts.html | 30 +
.../15/html/Deployment_Guide/s2-proc-mtrr.html | 19 +
.../html/Deployment_Guide/s2-proc-partitions.html | 29 +
.../15/html/Deployment_Guide/s2-proc-pci.html | 45 +
.../15/html/Deployment_Guide/s2-proc-pid.html | 58 +
.../15/html/Deployment_Guide/s2-proc-slabinfo.html | 67 +
.../15/html/Deployment_Guide/s2-proc-stat.html | 49 +
.../15/html/Deployment_Guide/s2-proc-swaps.html | 17 +
.../Deployment_Guide/s2-proc-sysrq-trigger.html | 14 +
.../15/html/Deployment_Guide/s2-proc-tty.html | 30 +
.../15/html/Deployment_Guide/s2-proc-uptime.html | 16 +
.../15/html/Deployment_Guide/s2-proc-version.html | 16 +
.../s2-redhat-config-users-group-new.html | 16 +
.../s2-redhat-config-users-group-properties.html | 16 +
.../s2-redhat-config-users-process.html | 82 +
.../html/Deployment_Guide/s2-rpm-freshening.html | 24 +
.../15/html/Deployment_Guide/s2-rpm-querying.html | 36 +
.../Deployment_Guide/s2-rpm-related-books.html | 12 +
.../html/Deployment_Guide/s2-rpm-uninstalling.html | 27 +
.../Deployment_Guide/s2-rpm-useful-websites.html | 14 +
.../15/html/Deployment_Guide/s2-rpm-verifying.html | 52 +
.../s2-services-additional-resources-books.html | 12 +
.../Deployment_Guide/s2-ssh-beyondshell-tcpip.html | 32 +
.../html/Deployment_Guide/s2-ssh-clients-scp.html | 30 +
.../html/Deployment_Guide/s2-ssh-clients-sftp.html | 51 +
.../s2-ssh-configuration-keypairs.html | 128 +
.../s2-ssh-configuration-requiring.html | 24 +
.../s2-ssh-configuration-sshd.html | 29 +
.../html/Deployment_Guide/s3-ftp-vsftpd-conf.html | 24 +
.../s3-services-running-restarting.html | 14 +
.../s3-services-running-running.html | 14 +
.../s3-services-running-stopping.html | 14 +
.../Deployment_Guide/sec-Additional_Resources.html | 12 +
.../sec-Configuration_File_Changes.html | 24 +
.../sec-Configuring_Yum_and_Yum_Repositories.html | 110 +
.../sec-Creating_a_Yum_Repository.html | 20 +
.../sec-Displaying_Information_About_a_Module.html | 72 +
.../sec-Displaying_Package_Information.html | 45 +
.../sec-Finding_Packages_with_Filters.html | 58 +
.../15/html/Deployment_Guide/sec-Installing.html | 55 +
.../sec-Installing_More_Yum_Plugins.html | 12 +
...sec-Installing_and_Removing_Package_Groups.html | 16 +
...ing_and_Removing_Packages_and_Dependencies.html | 28 +
.../sec-Installing_and_Upgrading.html | 90 +
.../Deployment_Guide/sec-Listing_Packages.html | 100 +
.../Deployment_Guide/sec-Loading_a_Module.html | 30 +
.../sec-PackageKit_Architecture.html | 94 +
.../sec-Packages_and_Package_Groups.html | 23 +
.../sec-Persistent_Module_Loading.html | 25 +
.../Deployment_Guide/sec-Plugin_Descriptions.html | 55 +
.../15/html/Deployment_Guide/sec-Removing.html | 30 +
.../sec-Setting_Module_Parameters.html | 45 +
.../sec-Setting_repository_Options.html | 46 +
.../sec-Specific_Kernel_Module_Capabilities.html | 16 +
.../Deployment_Guide/sec-Unloading_a_Module.html | 41 +
.../sec-Using_Add_Remove_Software.html | 18 +
.../sec-Using_Channel_Bonding.html | 192 +
.../Deployment_Guide/sec-Using_Yum_Variables.html | 28 +
.../sec-Verifying_the_Initial_RAM_Disk_Image.html | 66 +
.../sec-Viewing_the_Transaction_Log.html | 21 +
.../15/html/Deployment_Guide/sec-Yum_Plugins.html | 35 +
.../sect-Configuring_a_Multihomed_DHCP_Server.html | 115 +
...nd_Time_Configuration-Additional_Resources.html | 18 +
...d_Line_Configuration-Network_Time_Protocol.html | 52 +
...e_Configuration-Command_Line_Configuration.html | 27 +
...anguage_and_Keyboard_Configuration-Layouts.html | 28 +
.../sect-Preface-Book_Organization.html | 76 +
.../Deployment_Guide/sect-Preface-Feedback.html | 20 +
...Domains-Setting_up_Kerberos_Authentication.html | 83 +
...uration_Options-Configuring_a_Proxy_Domain.html | 87 +
...SSSD_User_Guide-Introduction-SSSD_Features.html | 58 +
...ation_Files-SSSD_Configuration_File_Format.html | 71 +
.../Deployment_Guide/testing-upload-method.html | 21 +
.../Fedora-15-Deployment_Guide-en-US.pdf | Bin 0 -> 6073076 bytes
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.xml | 10 +-
public_html/en-US/toc.html | 20 +-
public_html/es-ES/opds-Fedora.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.xml | 10 +-
public_html/es-ES/toc.html | 22 +-
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.xml | 10 +-
public_html/fa-IR/toc.html | 20 +-
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.xml | 10 +-
public_html/fi-FI/toc.html | 20 +-
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.xml | 10 +-
public_html/fr-FR/toc.html | 16 +-
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.xml | 10 +-
public_html/gu-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/he-IL/toc.html | 20 +-
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.xml | 10 +-
public_html/hi-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/hu-HU/toc.html | 20 +-
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.xml | 10 +-
public_html/id-ID/toc.html | 20 +-
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.xml | 10 +-
public_html/it-IT/toc.html | 18 +-
public_html/ja-JP/opds-Fedora.xml | 2 +-
.../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.xml | 10 +-
public_html/ja-JP/toc.html | 16 +-
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.xml | 10 +-
public_html/kn-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/ko-KR/toc.html | 20 +-
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.xml | 10 +-
public_html/ml-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/mr-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/nb-NO/toc.html | 20 +-
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.xml | 10 +-
public_html/nl-NL/toc.html | 18 +-
public_html/opds.xml | 86 +-
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.xml | 10 +-
public_html/or-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/pa-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/pl-PL/toc.html | 16 +-
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.xml | 10 +-
public_html/pt-BR/toc.html | 20 +-
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.xml | 10 +-
public_html/pt-PT/toc.html | 18 +-
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.xml | 10 +-
public_html/ru-RU/toc.html | 16 +-
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.xml | 10 +-
public_html/sk-SK/toc.html | 20 +-
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 +-
public_html/sr-Latn-RS/opds.xml | 10 +-
public_html/sr-Latn-RS/toc.html | 20 +-
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.xml | 10 +-
public_html/sr-RS/toc.html | 20 +-
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.xml | 10 +-
public_html/sv-SE/toc.html | 16 +-
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.xml | 10 +-
public_html/ta-IN/toc.html | 20 +-
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.xml | 10 +-
public_html/te-IN/toc.html | 20 +-
public_html/toc.html | 40 +-
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.xml | 10 +-
public_html/uk-UA/toc.html | 18 +-
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.xml | 10 +-
public_html/zh-CN/toc.html | 18 +-
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.xml | 10 +-
public_html/zh-TW/toc.html | 20 +-
913 files changed, 39006 insertions(+), 864 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index 30036d5..004b62a 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index f010116..2005750 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -1441,32 +1441,32 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/html/Fedora_Live_Ima...
- <lastmod>2011-05-21</lastmod>
+ <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/html/Deployment_Guid...
+ <lastmod>2011-05-24</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/html-single/Fedora_L...
- <lastmod>2011-05-21</lastmod>
+ <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/html-single/Deployme...
+ <lastmod>2011-05-24</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/html/Installation_Gu...
+ <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/pdf/Deployment_Guide...
<lastmod>2011-05-24</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/html-single/Installa...
- <lastmod>2011-05-24</lastmod>
+ <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/html/Fedora_Live_Ima...
+ <lastmod>2011-05-21</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/pdf/Installation_Gui...
- <lastmod>2011-05-24</lastmod>
+ <
loc>http://docs.fedoraproject.org/en-US/Fedora/15/html-single/Fedora_L...
+ <lastmod>2011-05-21</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
@@ -3151,7 +3151,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentati...
+ <
loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentati...
<lastmod>2010-07-07</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -3529,7 +3529,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.2...
+ <
loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.2...
<lastmod>2011-04-03</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -3757,7 +3757,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/es-ES/Fedora/14/pdf/Software_Managem...
+ <
loc>http://docs.fedoraproject.org/es-ES/Fedora/14/pdf/Software_Managem...
<lastmod>2010-10-08</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -3805,7 +3805,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/es-ES/Fedora/13/pdf/Accessibility_Gu...
+ <
loc>http://docs.fedoraproject.org/es-ES/Fedora/13/pdf/Accessibility_Gu...
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -4477,7 +4477,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/es-ES/Fedora/11/pdf/Security_Guide/F...
+ <
loc>http://docs.fedoraproject.org/es-ES/Fedora/11/pdf/Security_Guide/f...
<lastmod>2010-06-13</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -5173,7 +5173,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/fi-FI/Fedora/11/pdf/Fedora_Live_imag...
+ <
loc>http://docs.fedoraproject.org/fi-FI/Fedora/11/pdf/Fedora_Live_imag...
<lastmod>2010-06-14</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -5197,7 +5197,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/fi-FI/Fedora/10/pdf/Fedora_Live_Imag...
+ <
loc>http://docs.fedoraproject.org/fi-FI/Fedora/10/pdf/Fedora_Live_Imag...
<lastmod>2010-06-14</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -6397,7 +6397,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/it-IT/Fedora/13/pdf/Accessibility_Gu...
+ <
loc>http://docs.fedoraproject.org/it-IT/Fedora/13/pdf/Accessibility_Gu...
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -9013,7 +9013,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/nl-NL/Fedora/11/pdf/Security_Guide/F...
+ <
loc>http://docs.fedoraproject.org/nl-NL/Fedora/11/pdf/Security_Guide/f...
<lastmod>2010-06-13</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -10909,7 +10909,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/pt-PT/Fedora/13/pdf/Accessibility_Gu...
+ <
loc>http://docs.fedoraproject.org/pt-PT/Fedora/13/pdf/Accessibility_Gu...
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -14005,7 +14005,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/uk-UA/Fedora/13/pdf/Accessibility_Gu...
+ <
loc>http://docs.fedoraproject.org/uk-UA/Fedora/13/pdf/Accessibility_Gu...
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -14545,7 +14545,7 @@
<priority>0.8</priority>
</url>
<url>
- <
loc>http://docs.fedoraproject.org/zh-CN/Fedora/13/pdf/Accessibility_Gu...
+ <
loc>http://docs.fedoraproject.org/zh-CN/Fedora/13/pdf/Accessibility_Gu...
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
diff --git a/public_html/as-IN/opds-Fedora.xml b/public_html/as-IN/opds-Fedora.xml
index e9c51d4..72424eb 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>2011-05-24T13:34:05</updated>
+ <updated>2011-05-24T14:52:40</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 bb04d7f..30e1f65 100644
--- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:06</updated>
+ <updated>2011-05-24T14:52:40</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 3423d0e..5b15e12 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>2011-05-24T13:34:06</updated>
+ <updated>2011-05-24T14:52:40</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 efba5d3..e58f829 100644
--- a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index 5c2835f..5b275d7 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:05</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:06</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:06</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/as-IN/toc.html b/public_html/as-IN/toc.html
index 8550d21..1a3808f 100644
--- a/public_html/as-IN/toc.html
+++ b/public_html/as-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bg-BG/opds-Fedora.xml b/public_html/bg-BG/opds-Fedora.xml
index 7a36fda..cdb66c8 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index 93c8369..48ddb14 100644
--- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Core.xml
b/public_html/bg-BG/opds-Fedora_Core.xml
index 027b881..8f6a412 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
index cab2761..741a020 100644
--- a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 9db70df..44e018a 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bg-BG/toc.html b/public_html/bg-BG/toc.html
index 6cc9b75..1f94300 100644
--- a/public_html/bg-BG/toc.html
+++ b/public_html/bg-BG/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bn-IN/opds-Fedora.xml b/public_html/bn-IN/opds-Fedora.xml
index a6796ec..32dc19a 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</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 12b23e5..fc14a8d 100644
--- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</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 e815e2f..d367a05 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</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 5eaff11..5c3c01e 100644
--- a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index 5d2c280..d3a6962 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bn-IN/toc.html b/public_html/bn-IN/toc.html
index a2858fe..dff3a8e 100644
--- a/public_html/bn-IN/toc.html
+++ b/public_html/bn-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bs-BA/opds-Fedora.xml b/public_html/bs-BA/opds-Fedora.xml
index d6a4025..b72acc8 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</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 17fb161..b25164d 100644
--- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</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 95e9927..7d53354 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</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 1038f7f..bf6c9b8 100644
--- a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index 18a8471..8e5dcd5 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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bs-BA/toc.html b/public_html/bs-BA/toc.html
index d534b38..4f5f54e 100644
--- a/public_html/bs-BA/toc.html
+++ b/public_html/bs-BA/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ca-ES/opds-Fedora.xml b/public_html/ca-ES/opds-Fedora.xml
index 96a76e0..5776351 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>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</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 5b27ea0..34d6ee9 100644
--- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</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 ff31024..2f866a9 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>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</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 b0540d0..a618d9f 100644
--- a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index 4a010a4..850dde0 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>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ca-ES/toc.html b/public_html/ca-ES/toc.html
index 3a26433..be49285 100644
--- a/public_html/ca-ES/toc.html
+++ b/public_html/ca-ES/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/cs-CZ/opds-Fedora.xml b/public_html/cs-CZ/opds-Fedora.xml
index ecbd771..20119c0 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>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</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 f2334ef..e56d785 100644
--- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</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 26157ce..3e3b354 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>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</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 c4d3ff8..cfce5da 100644
--- a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index a6ba6bd..aad2cf7 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>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/cs-CZ/toc.html b/public_html/cs-CZ/toc.html
index cd4b30e..f44eff7 100644
--- a/public_html/cs-CZ/toc.html
+++ b/public_html/cs-CZ/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/da-DK/opds-Fedora.xml b/public_html/da-DK/opds-Fedora.xml
index 8020b8f..4f94009 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>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</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 d2bb09d..96066e9 100644
--- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</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 5efefa9..0ceb678 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>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</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 bef8a4f..3d0cd0e 100644
--- a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index 5abac44..ac5afff 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>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/da-DK/toc.html b/public_html/da-DK/toc.html
index 2afaeeb..9e2ef67 100644
--- a/public_html/da-DK/toc.html
+++ b/public_html/da-DK/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/de-DE/opds-Fedora.xml b/public_html/de-DE/opds-Fedora.xml
index 94bafdb..00804d8 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>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</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 7bff2b4..8b85159 100644
--- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</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 0e77d1a..8ba0401 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>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</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 df199ca..a7fa3e3 100644
--- a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index 6e7acb2..fb51baa 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>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/de-DE/toc.html b/public_html/de-DE/toc.html
index 7e52fed..2d12c03 100644
--- a/public_html/de-DE/toc.html
+++ b/public_html/de-DE/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Nicht übersetzt</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -887,7 +887,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1133,7 +1133,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/el-GR/opds-Fedora.xml b/public_html/el-GR/opds-Fedora.xml
index 3ea42a4..c49dc33 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>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</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 d1eb105..3c76fe4 100644
--- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</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 5920e0e..21fa3e0 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>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</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 9f10210..eae6acc 100644
--- a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index 671ba9c..fa7ebee 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>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/el-GR/toc.html b/public_html/el-GR/toc.html
index 7fc5bdb..6ff1ac5 100644
--- a/public_html/el-GR/toc.html
+++ b/public_html/el-GR/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/common.css
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..f9603b7
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/common.css
@@ -0,0 +1,1495 @@
+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;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+}
+
+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;
+}
+
+.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;
+ 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;
+}
+
+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*/
+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;
+}
+
+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;
+}
+
+div.section {
+ margin-top:1em;
+}
+
+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;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+}
+
+.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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/default.css
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+@import url("common.css");
+@import url("overrides.css");
+@import url("lang.css");
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/lang.css
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/overrides.css
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/print.css
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+@import url("common.css");
+@import url("overrides.css");
+@import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/1.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/1.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/1.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/10.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/10.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/10.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/11.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/11.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/11.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/12.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/12.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/12.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/13.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/13.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/13.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/14.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/14.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/14.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/15.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/15.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/15.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/16.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/16.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/16.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/17.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/17.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/17.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/18.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/18.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/18.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/19.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/19.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/19.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/2.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/2.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/2.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/20.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/20.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/20.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/21.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/21.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/21.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/22.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/22.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/22.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/23.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/23.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/23.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/24.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/24.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/24.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/25.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/25.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/25.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/26.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/26.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/26.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/27.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/27.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/27.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/28.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/28.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/28.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/29.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/29.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/29.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/3.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/3.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/3.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/30.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/30.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/30.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/31.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/31.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/31.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/32.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/32.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/32.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/33.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/33.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/33.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/34.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/34.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/34.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/35.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/35.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/35.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/36.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/36.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/36.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/37.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/37.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/37.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/38.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/38.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/38.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/39.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/39.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/39.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/4.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/4.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/4.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/40.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/40.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/40.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/5.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/5.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/5.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/6.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/6.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/6.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/7.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/7.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/7.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/8.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/8.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/8.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/9.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/9.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/9.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/bullet_arrowblue.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/bullet_arrowblue.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/documentation.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/documentation.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/dot.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/dot.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/dot2.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/dot2.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/green.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/green.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/h1-bg.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/h1-bg.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/image_left.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/image_left.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/image_right.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..5b67443
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/image_right.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/important.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/important.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/important.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L
78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L
41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882
z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L
55.536215,56.538729 z"
+ id="path6824"
+
style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L
55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L
55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L
55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L
55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L
55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L
55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L
55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L
55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new"
/>
+ </g>
+</svg>
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/logo.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/logo.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/note.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/note.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/note.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L
-2512.4524,4607.3813 L -2512.4524,56.33197 z"
+
transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+
style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1"
/>
+ </g>
+ <g
+
transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928
370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C
154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353
494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+
style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+
style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729
326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C
209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L
509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C
495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+
style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C
253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861
313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345
440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+
style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+
style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+
style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ </g>
+ </g>
+ </g>
+</svg>
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/red.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/red.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/shade.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/shade.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/shine.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/shine.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-back.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-back.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-forward.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-forward.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-up.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-go-up.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-home.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/stock-home.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/title_logo.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/title_logo.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/title_logo.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/warning.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/warning.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/warning.svg
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L
-1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L
-1602.5477,1091.5306 L -1603,1054.4387 z"
+
transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+
style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1"
/>
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L
-1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L
-1602.5477,1091.5306 L -1603,1054.4387 z"
+
transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+
style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1"
/>
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987
-2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C
-2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961
-2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L
-2686.7886,1597.753"
+ id="path8038"
+
style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream
Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346
-2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C
-2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346
-2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+
style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream
Charter" />
+ </g>
+ </g>
+</svg>
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/watermark-draft.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/watermark-draft.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/yellow.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/Common_Content/images/yellow.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png
new file mode 100644
index 0000000..9c331b6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png
new file mode 100644
index 0000000..6acf293
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png
new file mode 100644
index 0000000..8df5a42
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png
new file mode 100644
index 0000000..f4cb430
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt-alert.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt-alert.png
new file mode 100644
index 0000000..c95a6be
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt-alert.png differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt-event-configuration.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt-event-configuration.png
new file mode 100644
index 0000000..f213180
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt-event-configuration.png
differ
diff --git a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt.png
new file mode 100644
index 0000000..8a7f53d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/abrt.png differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-filters-available.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-filters-available.png
new file mode 100644
index 0000000..78050b5
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-filters-available.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-filters-end-user.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-filters-end-user.png
new file mode 100644
index 0000000..b909b93
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-filters-end-user.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-install.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-install.png
new file mode 100644
index 0000000..064d224
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-install.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-log.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-log.png
new file mode 100644
index 0000000..dcfaae7
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-log.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-package-group.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-package-group.png
new file mode 100644
index 0000000..2626ea1
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-package-group.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-remove.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-remove.png
new file mode 100644
index 0000000..3b8429c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software-remove.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software.png
new file mode 100644
index 0000000..219c461
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/add-remove-software.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-01.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-01.png
new file mode 100644
index 0000000..214673d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-01.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-02.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-02.png
new file mode 100644
index 0000000..2c6b837
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-02.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-03.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-03.png
new file mode 100644
index 0000000..bcebeee
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-03.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-04.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-04.png
new file mode 100644
index 0000000..67cfbda
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-04.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-05.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-05.png
new file mode 100644
index 0000000..fff1bfa
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-05.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-06.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-06.png
new file mode 100644
index 0000000..13d27ee
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-06.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-07.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-07.png
new file mode 100644
index 0000000..4b454ba
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-07.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/authconfig_LDAP_kerb.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/authconfig_LDAP_kerb.png
new file mode 100644
index 0000000..7268d86
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/authconfig_LDAP_kerb.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/authconfig_advanced.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/authconfig_advanced.png
new file mode 100644
index 0000000..53ddd7c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/authconfig_advanced.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/date-and-time-panel.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/date-and-time-panel.png
new file mode 100644
index 0000000..d3873b9
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/date-and-time-panel.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/date-and-time-settings.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/date-and-time-settings.png
new file mode 100644
index 0000000..260a043
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/date-and-time-settings.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/devicemngr.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/devicemngr.png
new file mode 100644
index 0000000..ebbd20b
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/devicemngr.png differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/gnome-print-queue.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/gnome-print-queue.png
new file mode 100644
index 0000000..a19d10c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/gnome-print-queue.png
differ
diff --git a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/hwbrowser.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/hwbrowser.png
new file mode 100644
index 0000000..a15d0bf
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/hwbrowser.png differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
new file mode 100644
index 0000000..bec8d23
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
new file mode 100644
index 0000000..9242e4a
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
b/public_html/en-US/Fedora/15/html-single/Deployment_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/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png
new file mode 100644
index 0000000..e9f5b66
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration.png
new file mode 100644
index 0000000..2b250b7
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/oprof-start-config.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/oprof-start-config.png
new file mode 100644
index 0000000..03b8701
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/oprof-start-config.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/oprof-start-setup.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/oprof-start-setup.png
new file mode 100644
index 0000000..5f0c64b
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/oprof-start-setup.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/print_conf_window.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/print_conf_window.png
new file mode 100644
index 0000000..ba58c70
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/print_conf_window.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-add-printer.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-add-printer.png
new file mode 100644
index 0000000..9a25612
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-add-printer.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config1.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config1.png
new file mode 100644
index 0000000..5f67b4d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config1.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config2.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config2.png
new file mode 100644
index 0000000..9e05c23
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config2.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config3.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config3.png
new file mode 100644
index 0000000..47e483c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config3.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config4.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config4.png
new file mode 100644
index 0000000..a2387a8
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config4.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config5.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config5.png
new file mode 100644
index 0000000..9074579
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config5.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config6.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config6.png
new file mode 100644
index 0000000..152a760
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-config6.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-ipp.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-ipp.png
new file mode 100644
index 0000000..55e8e89
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-ipp.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-jetdirect.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-jetdirect.png
new file mode 100644
index 0000000..5884d66
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-jetdirect.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-lpd.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-lpd.png
new file mode 100644
index 0000000..5ea620c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-lpd.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-main.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-main.png
new file mode 100644
index 0000000..57fb07d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-main.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-select-driver.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-select-driver.png
new file mode 100644
index 0000000..6b27ff1
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-select-driver.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-select-model.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-select-model.png
new file mode 100644
index 0000000..a8e49f8
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-select-model.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-smb.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-smb.png
new file mode 100644
index 0000000..26b7939
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/printconf-smb.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-language.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-language.png
new file mode 100644
index 0000000..e846eaf
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-language.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts-add.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts-add.png
new file mode 100644
index 0000000..607a1aa
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts-add.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts-indicator.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts-indicator.png
new file mode 100644
index 0000000..c61e692
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts-indicator.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts.png
new file mode 100644
index 0000000..448c00c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/region-and-language-layouts.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-basic.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-basic.png
new file mode 100644
index 0000000..c0dffc3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-basic.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-create-share.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-create-share.png
new file mode 100644
index 0000000..14bc8d5
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-create-share.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-security.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-security.png
new file mode 100644
index 0000000..fb71f96
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-security.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-users.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-users.png
new file mode 100644
index 0000000..8de4375
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba-users.png
differ
diff --git a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba.png
new file mode 100644
index 0000000..27abf11
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/s-c-samba.png differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/samba-nautilus-domain.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/samba-nautilus-domain.png
new file mode 100644
index 0000000..3b8e5a9
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/samba-nautilus-domain.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update-preferences.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update-preferences.png
new file mode 100644
index 0000000..64f5b91
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update-preferences.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update-software-sources.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update-software-sources.png
new file mode 100644
index 0000000..3ab48d5
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update-software-sources.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update.png
new file mode 100644
index 0000000..f1b066b
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/software-update.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-passphrase-prompt.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-passphrase-prompt.png
new file mode 100644
index 0000000..b8b7b11
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-passphrase-prompt.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications-add.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications-add.png
new file mode 100644
index 0000000..517567e
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications-add.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications-check.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications-check.png
new file mode 100644
index 0000000..a3d8599
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications-check.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications.png
new file mode 100644
index 0000000..bfa9578
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/ssh-startup-applications.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/switchmail-gui.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/switchmail-gui.png
new file mode 100644
index 0000000..380d884
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/switchmail-gui.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-add.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-add.png
new file mode 100644
index 0000000..3690469
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-add.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-alerts.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-alerts.png
new file mode 100644
index 0000000..db4301a
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-alerts.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-define.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-define.png
new file mode 100644
index 0000000..3b37e73
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-define.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-enable.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-enable.png
new file mode 100644
index 0000000..06eb44c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-enable.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-manage.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-manage.png
new file mode 100644
index 0000000..285f83f
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer-filters-manage.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer.png
new file mode 100644
index 0000000..7c3bdd6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-log-viewer.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-file-systems.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-file-systems.png
new file mode 100644
index 0000000..4f6050c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-file-systems.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-processes.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-processes.png
new file mode 100644
index 0000000..f218181
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-processes.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-resources.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-resources.png
new file mode 100644
index 0000000..e56a166
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/system-monitor-resources.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-create.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-create.png
new file mode 100644
index 0000000..652df07
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-create.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-password-change.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-password-change.png
new file mode 100644
index 0000000..da264e4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-password-change.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-remove.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-remove.png
new file mode 100644
index 0000000..727df90
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts-remove.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts.png
new file mode 100644
index 0000000..633b363
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-accounts.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-add-group.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-add-group.png
new file mode 100644
index 0000000..d59e89c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-add-group.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-add-user.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-add-user.png
new file mode 100644
index 0000000..af1eb92
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-add-user.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-edit-group.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-edit-group.png
new file mode 100644
index 0000000..594ab85
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-edit-group.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-edit-user.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-edit-user.png
new file mode 100644
index 0000000..a49ff97
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager-edit-user.png
differ
diff --git
a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager.png
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager.png
new file mode 100644
index 0000000..a50cad2
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/images/user-manager.png differ
diff --git a/public_html/en-US/Fedora/15/html-single/Deployment_Guide/index.html
b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/index.html
new file mode 100644
index 0000000..607712f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html-single/Deployment_Guide/index.html
@@ -0,0 +1,14653 @@
+<?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>Deployment Guide</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><meta name="description" content="The Deployment Guide documents
relevant information regarding the deployment, configuration, and administration of Fedora
15. It is oriented towards system administrators with a basic understanding of the
system." /><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_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="en-US" class="book"
id="id1453041" lang="en-US"><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">15</span></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h1
id="id1453041" class="title">Deployment
Guide</h1></div><div fo
nt-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h2
class="subtitle">Deployment, Configuration and Administration of Fedora
15</h2></div><p class="edition">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="en-US"
class="authorgroup" lang="en-US"><div
class="author"><h3 class="author"><span
class="firstname">Jaromír</span> <span
class="surname">Hradílek</span></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:jhradile@redhat.com">jhradile@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="firstname">Douglas</span> <span
class="surname">Silas</span></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:dhensley@redhat.com">dhensley@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="firstname">Martin</span> <span
class="surname">Prpi
č</span></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@redhat.com">mprpic@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="firstname">Eva</span> <span
class="surname">Kopalová</span></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:ekopalov@redhat.com">ekopalov@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="firstname">John</span> <span
class="surname">Ha</span></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="firstname">David</span>
<span class="surname">O'Brien</span></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="firstname">Michael</span>
<span class="surname">Hideo</span></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="firstname">Don</span>
<span class="surname">Domingo</span></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="id543217" class="legalnotice"><h1
class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2011 Red Hat,
Inc. and others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An
explanation of CC-BY-SA is available at <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http:/...;.
The original authors of this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if
you distribute this document or an adaptation of it, you must provide the URL for the
original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not
to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the
Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States
and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a
href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines"...;.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark
of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of
Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon
Graphics International Corp. or its subsidiaries in the United States and/or other
countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark
of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
class="abstract"><h6>Abstract</h6><div
class="para">
+ The <em class="citetitle">Deployment Guide</em> documents
relevant information regarding the deployment, configuration, and administration of Fedora
15. It is oriented towards system administrators with a basic understanding of the
system.
+ </div></div></div></div><hr /></div><div
class="toc"><dl><dt><span class="preface"><a
href="#id663216">Preface</a></span></dt><dd><dl><dt><span
class="section"><a href="#sect-Preface-Target_Audience">1.
Target Audience</a></span></dt><dt><span
class="section"><a href="#sect-Preface-Book_Organization">2.
How to Read this Book</a></span></dt><dt><span
class="section"><a href="#id676498">3. Document
Conventions</a></span></dt><dd><dl><dt><span
class="section"><a href="#id390360">3.1. Typographic
Conventions</a></span></dt><dt><span
class="section"><a href="#id1305126">3.2. Pull-quote
Conventions</a></span></dt><dt><span
class="section"><a href="#id543787">3.3. Notes and
Warnings</a></span></dt></dl></dd><dt><span
class="section"><a href="#sect-Preface-Feedback">4.
Feedback</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_System_Configuration">I.
Basic System Configu
ration</a></span></dt><dd><dl><dt><span
class="chapter"><a
href="#ch-Language_and_Keyboard_Configuration">1. Language and Keyboard
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Language_and_Keyboard_Configuration-Language">1.1. Changing the
Language</a></span></dt><dt><span
class="section"><a
href="#sect-Language_and_Keyboard_Configuration-Layouts">1.2. Changing the
Keyboard Layout</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-Date_and_Time_Configuration">2.
Date and Time
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Date_and_Time">2.1. Date and Time
Configuration Tool</a></span></dt><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">2.2.
Command Line
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">2.2.1.
Configuring the Da
te and Time</a></span></dt><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">2.2.2.
Configuring the Network Time
Protocol</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Additional_Resources">2.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation">2.3.1.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Managing_Users_and_Groups">3.
Managing Users and
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts">3.1. User Accounts
Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.1.1.
Configuring an Account</a></span></dt><dt><span
class="section"><a href="#sect-Managing_Users_an
d_Groups-User_Accounts-Adding_a_New_User">3.1.2. Adding a New
User</a></span></dt><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.1.3.
Removing a User</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-configui">3.2. User
Manager Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-redhat-config-users-user-new">3.2.1. Adding a New
User</a></span></dt><dt><span
class="section"><a
href="#s2-redhat-config-users-group-new">3.2.2. Adding a New
Group</a></span></dt><dt><span
class="section"><a
href="#s2-redhat-config-users-group-properties">3.2.3. Modifying Group
Properties</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-tools">3.3. User and Group
Management Tools</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-users-cmd-line">3.3.1. Command
Line Configuration</a></span></dt><dt><span
class="section"><a
href="#s2-redhat-config-users-process">3.3.2. Explaining th
e Process</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-users-groups-standard-users">3.4. Standard
Users</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-standard-groups">3.5. Standard
Groups</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-private-groups">3.6. User Private
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-users-groups-rationale">3.6.1.
Group
Directories</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-users-groups-shadow-utilities">3.7. Shadow
Passwords</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-additional-resources">3.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-users-groups-documentation">3.8.1. Installed
Documentation</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Package_Management">II. Package
Management</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-y
um">4.
Yum</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Checking_For_and_Updating_Packages">4.1. Checking For and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Checking_For_Updates">4.1.1.
Checking For Updates</a></span></dt><dt><span
class="section"><a href="#sec-Updating_Packages">4.1.2.
Updating Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Preserving_Configuration_File_Changes">4.1.3. Preserving
Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Packages_and_Package_Groups">4.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Searching_Packages">4.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="#sec-Listing_Packages">4.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Package_Information">4.2.3. Displaying Package
Information</a></span></dt><dt><span class
="section"><a href="#sec-Installing">4.2.4. Installing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-Removing">4.2.5. Removing
Packages</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Configuring_Yum_and_Yum_Repositories">4.3. Configuring Yum and Yum
Repositories</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Setting_main_Options">4.3.1.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_repository_Options">4.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="#sec-Using_Yum_Variables">4.3.3.
Using Yum Variables</a></span></dt><dt><span
class="section"><a
href="#sec-Creating_a_Yum_Repository">4.3.4. Creating a Yum
Repository</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Yum_Plugins">4.4. Yum
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Enabling,
Configuring and
Disabling Yum Plugins</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_More_Yum_Plugins">4.4.2. Installing Additional Yum
Plugins</a></span></dt><dt><span
class="section"><a href="#sec-Plugin_Descriptions">4.4.3.
Plugin
Descriptions</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Additional_Resources">4.5.
Additional
Resources</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. Updating Packages
with Software
Update</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Setting_preferences_for_checking_for_updates">5.1.1. Setting the
Update-Checking Interval</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_preferences_for_software_sources">5.1.2. Setting the
Software Sources</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Using_Add_Remove_Software">5.2.
Using
Add/Remove
Software</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. Refreshing
Software Sources (Yum Repositories)</a></span></dt><dt><span
class="section"><a
href="#sec-Finding_Packages_with_Filters">5.2.2. Finding Packages with
Filters</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_and_Removing_Packages_and_Dependencies">5.2.3.
Installing and Removing Packages (and
Dependencies)</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_and_Removing_Package_Groups">5.2.4. Installing and
Removing Package Groups</a></span></dt><dt><span
class="section"><a
href="#sec-Viewing_the_Transaction_Log">5.2.5. Viewing the Transaction
Log</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-PackageKit_Architecture">5.3.
PackageKit Architecture</a></span></dt><dt><span
class="section"><a
href="#ch-Graphical_Package_Management-sec-Additional_Resources">5.4.
Additional Resources</a>
</span></dt></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Networking">III.
Networking</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-Network_Interfaces">6. Network
Interfaces</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-networkscripts-files">6.1.
Network Configuration Files</a></span></dt><dt><span
class="section"><a href="#s1-networkscripts-interfaces">6.2.
Interface Configuration
Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-eth0">6.2.1. Ethernet
Interfaces</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-chan">6.2.2. Channel Bonding
Interfaces</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-alias">6.2.3. Alias and Clone
Files</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-ppp0">6.2.4. Dialup
Interfaces</a></span></dt><dt><span
class="section"><a href="#s2-networkscripts-interfaces-other"
6.2.5. Other
Interfaces</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-networkscripts-control">6.3.
Interface Control Scripts</a></span></dt><dt><span
class="section"><a
href="#s1-networkscripts-static-routes">6.4. Configuring Static
Routes</a></span></dt><dt><span
class="section"><a href="#s1-networkscripts-functions">6.5.
Network Function Files</a></span></dt><dt><span
class="section"><a href="#s1-networkscripts-resources">6.6.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-networkscripts-docs-inst">6.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Infrastructure_Services">IV.
Infrastructure
Services</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-Services_and_Daemons">7.
Services and
Daemons</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-services-configuring">7.1.
Configuring
Services</a></span></dt><dd><dl><dt><span
class="sec
tion"><a
href="#s3-services-configuration-enabling">7.1.1. Enabling the
Service</a></span></dt><dt><span
class="section"><a
href="#s3-services-configuration-disabling">7.1.2. Disabling the
Service</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-services-running">7.2. Running
Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-running-checking">7.2.1. Checking the Service
Status</a></span></dt><dt><span
class="section"><a href="#s3-services-running-running">7.2.2.
Running the Service</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-stopping">7.2.3. Stopping the
Service</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-restarting">7.2.4. Restarting the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-services-additional-resources">7.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-services-additional-resources-installed">7.3.1. Inst
alled Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-services-additional-resources-books">7.3.2. Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Configuring_Authentication">8.
Configuring
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool">8.1. The Authentication
Configuration Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1.
Identity & Authentication</a></span></dt><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">8.1.2.
Advanced Options</a></span></dt><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3.
Command Line
Version</a></span></dt></dl></dd><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Introduction">8.2. The System Security Services
D
aemon (SSSD)</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-Introduction-What_is_SSSD">8.2.1. What is
SSSD?</a></span></dt><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">8.2.2. SSSD
Features</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Setting_Up_SSSD">8.2.3. Setting Up
SSSD</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Configuring_Services">8.2.4. Configuring
Services</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Configuring_Domains">8.2.5. Configuring
Domains</a></span></dt><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">8.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">8.2.7.
Configuring a Proxy Domain</a></span></dt><dt><span
class="section"
<a href="#chap-SSSD_User_Guide-Troubleshooting">8.2.8.
Troubleshooting</a></span></dt><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">8.2.9.
SSSD Configuration File
Format</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-OpenSSH">9.
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-ssh-protocol">9.1. The SSH
Protocol</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-why">9.1.1. Why Use
SSH?</a></span></dt><dt><span
class="section"><a href="#s2-ssh-features">9.1.2. Main
Features</a></span></dt><dt><span
class="section"><a href="#s2-ssh-versions">9.1.3. Protocol
Versions</a></span></dt><dt><span
class="section"><a href="#s2-ssh-conn">9.1.4. Event Sequence
of an SSH
Connection</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-configuration">9.2. An
OpenSSH
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a href=
"#s2-ssh-configuration-configs">9.2.1. Configuration
Files</a></span></dt><dt><span
class="section"><a href="#s2-ssh-configuration-sshd">9.2.2.
Starting an OpenSSH Server</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-requiring">9.2.3. Requiring SSH for Remote
Connections</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-keypairs">9.2.4. Using a Key-Based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-clients">9.3. OpenSSH
Clients</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-clients-ssh">9.3.1. Using
the ssh Utility</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-scp">9.3.2. Using
the <code class="command">scp</code>
Utility</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-sftp">9.3.3. Using
the <code class="command">sftp</code>
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-beyondshell">9.4. More Than
a Secur
e Shell</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-beyondshell-x11">9.4.1. X11
Forwarding</a></span></dt><dt><span
class="section"><a href="#s2-ssh-beyondshell-tcpip">9.4.2.
Port Forwarding</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-openssh-additional-resources">9.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-openssh-installed-docs">9.5.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-openssh-useful-websites">9.5.2.
Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Servers">V.
Servers</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-DHCP_Servers">10. DHCP
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-dhcp-why">10.1. Why Use
DHCP?</a></span></dt><dt><span
class="section"><a href="#s1-dhcp-configuring-server">10.2.
Configuring a DHCP
Server</a></span></dt><dd><dl><dt><span class
="section"><a href="#config-file">10.2.1. Configuration
File</a></span></dt><dt><span
class="section"><a href="#lease-database">10.2.2. Lease
Database</a></span></dt><dt><span
class="section"><a href="#id619308">10.2.3. Starting and
Stopping the Server</a></span></dt><dt><span
class="section"><a href="#dhcp-relay-agent">10.2.4. DHCP
Relay Agent</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-dhcp-configuring-client">10.3.
Configuring a DHCP Client</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_a_Multihomed_DHCP_Server">10.4. Configuring a
Multihomed DHCP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-dns_Host_Configuration">10.4.1. Host
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">10.5. DHCP
for IPv6 (DHCPv6)</a></span></dt><dt><span
class="section"><a href="#s1-dhcp-additional-resources">10.6.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="sectio
n"><a href="#s2-dhcp-installed-docs">10.6.1. Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-DNS_Servers">11. DNS
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Introduction_to_DNS">11.1.
Introduction to
DNS</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-dns-introduction-zones">11.1.1.
Nameserver Zones</a></span></dt><dt><span
class="section"><a
href="#s2-dns-introduction-nameservers">11.1.2. Nameserver
Types</a></span></dt><dt><span
class="section"><a href="#s2-dns-introduction-bind">11.1.3.
BIND as a
Nameserver</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-BIND">11.2.
BIND</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-bind-namedconf">11.2.1.
Configuring the named Service</a></span></dt><dt><span
class="section"><a href="#s2-bind-zone">11.2.2. Editing Zone
Files</a></span></dt><dt><span
class="section"><a href="#s2-bind-rndc">11.2.3. Using the
rndc Utili
ty</a></span></dt><dt><span class="section"><a
href="#s2-bind-dig">11.2.4. Using the dig
Utility</a></span></dt><dt><span
class="section"><a href="#s2-bind-features">11.2.5. Advanced
Features of BIND</a></span></dt><dt><span
class="section"><a href="#s2-bind-mistakes">11.2.6. Common
Mistakes to Avoid</a></span></dt><dt><span
class="section"><a
href="#s2-bind-additional-resources">11.2.7. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Web_Servers">12. Web
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-The_Apache_HTTP_Server">12.1.
The Apache HTTP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-apache-version2-features">12.1.1. New
Features</a></span></dt><dt><span
class="section"><a href="#s2-apache-version2-changes">12.1.2.
Notable Changes</a></span></dt><dt><span
class="section"><a
href="#s2-apache-version2-migrating">12.1.3. Updating the
Configuration</a></span></dt><dt><span class=
"section"><a href="#s2-apache-running">12.1.4. Running the
httpd Service</a></span></dt><dt><span
class="section"><a href="#s2-apache-editing">12.1.5. Editing
the Configuration Files</a></span></dt><dt><span
class="section"><a href="#s2-apache-dso">12.1.6. Working with
Modules</a></span></dt><dt><span
class="section"><a href="#s2-apache-virtualhosts">12.1.7.
Setting Up Virtual Hosts</a></span></dt><dt><span
class="section"><a href="#s2-apache-mod_ssl">12.1.8. Setting
Up an SSL Server</a></span></dt><dt><span
class="section"><a href="#s2-apache-resources">12.1.9.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Mail_Servers">13. Mail
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-email-protocols">13.1. Email
Protocols</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-protocols-send">13.1.1.
Mail Transport Protocols</a></span></dt><dt><span
class="section"><a href="#s2-email-protocols-client
">13.1.2. Mail Access
Protocols</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-types">13.2. Email Program
Classifications</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-types-mta">13.2.1. Mail
Transport Agent</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mda">13.2.2. Mail
Delivery Agent</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mua">13.2.3. Mail
User Agent</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mta">13.3. Mail Transport
Agents</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-mta-postfix">13.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-sendmail">13.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-fetchmail">13.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="#s2-email-switchmail">13.3.4. Mail
Transport Agent (MTA)
Configuration</a></span></dt></dl></dd><dt><span
cl
ass="section"><a href="#s1-email-mda">13.4. Mail Delivery
Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-email-procmail-configuration">13.4.1. Procmail
Configuration</a></span></dt><dt><span
class="section"><a href="#s2-email-procmail-recipes">13.4.2.
Procmail Recipes</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mua">13.5. Mail User
Agents</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-security">13.5.1. Securing
Communication</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-email-additional-resources">13.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-installed-docs">13.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-email-useful-websites">13.6.2.
Useful Websites</a></span></dt><dt><span
class="section"><a href="#s2-email-related-books">13.6.3.
Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="chapte
r"><a href="#ch-Directory_Servers">14. Directory
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-OpenLDAP">14.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ldap-introduction">14.1.1.
Introduction to LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-installation">14.1.2.
Installing the OpenLDAP Suite</a></span></dt><dt><span
class="section"><a href="#s2-ldap-configuration">14.1.3.
Configuring an OpenLDAP Server</a></span></dt><dt><span
class="section"><a href="#s2-ldap-running">14.1.4. Running an
OpenLDAP Server</a></span></dt><dt><span
class="section"><a href="#s2-ldap-pam">14.1.5. Configuring a
System to Authenticate Using OpenLDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-resources">14.1.6.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-File_and_Print_Servers">15. File
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Samba">1
5.1. Samba</a></span></dt><dd><dl><dt><span
class="section"><a href="#samba-rgs-overview">15.1.1.
Introduction to Samba</a></span></dt><dt><span
class="section"><a href="#s2-samba-daemons">15.1.2. Samba
Daemons and Related Services</a></span></dt><dt><span
class="section"><a href="#s2-samba-connect-share">15.1.3.
Connecting to a Samba Share</a></span></dt><dt><span
class="section"><a href="#s2-samba-configuring">15.1.4.
Configuring a Samba Server</a></span></dt><dt><span
class="section"><a href="#s2-samba-startstop">15.1.5.
Starting and Stopping Samba</a></span></dt><dt><span
class="section"><a href="#s2-samba-servers">15.1.6. Samba
Server Types and the <code class="filename">smb.conf</code>
File</a></span></dt><dt><span
class="section"><a href="#s2-samba-security-modes">15.1.7.
Samba Security Modes</a></span></dt><dt><span
class="section"><a href="#s2-samba-account-info-dbs">15.1.8.
Samba Account Information Databases</a></span></dt><dt><span
class="section"><a href="#s2-sa
mba-network-browsing">15.1.9. Samba Network
Browsing</a></span></dt><dt><span
class="section"><a href="#s2-samba-cups">15.1.10. Samba with
CUPS Printing Support</a></span></dt><dt><span
class="section"><a href="#s2-samba-programs">15.1.11. Samba
Distribution Programs</a></span></dt><dt><span
class="section"><a href="#s2-samba-resources">15.1.12.
Additional
Resources</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-FTP">15.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ftp-protocol">15.2.1. The File
Transfer Protocol</a></span></dt><dt><span
class="section"><a href="#s2-ftp-servers">15.2.2. FTP
Servers</a></span></dt><dt><span
class="section"><a href="#s3-ftp-vsftpd-conf">15.2.3. Files
Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-start">15.2.4. Starting and Stopping <code
class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-co
nf">15.2.5. <code class="command">vsftpd</code>
Configuration Options</a></span></dt><dt><span
class="section"><a href="#s2-ftp-resources">15.2.6.
Additional
Resources</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="#part-Monitoring_and_Automation">VI.
Monitoring and
Automation</a></span></dt><dd><dl><dt><span
class="chapter"><a href="#ch-System_Monitoring_Tools">16.
System Monitoring
Tools</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-sysinfo-system-processes">16.1.
System Processes</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-memory-usage">16.2.
Memory Usage</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-filesystems">16.3. File
Systems</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-hardware">16.4.
Hardware</a></span></dt><dt><span
class="section"><a
href="#s1-sysinfo-additional-resources">16.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysin
fo-installed-docs">16.5.1. Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="#ch-Viewing_and_Managing_Log_Files">17. Viewing and Managing Log
Files</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-configuring-rsyslog">17.1.
Configuring
rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-global-directives">17.1.1.
Global Directives</a></span></dt><dt><span
class="section"><a href="#s2-modules">17.1.2.
Modules</a></span></dt><dt><span
class="section"><a href="#s2-rules">17.1.3.
Rules</a></span></dt><dt><span
class="section"><a href="#s2-rsyslog-cmd-options">17.1.4.
<span
class="application"><strong>rsyslog</strong></span> Command
Line
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-logfiles-locating">17.2.
Locating Log Files</a></span></dt><dd><dl><dt><span
class="section"><a href="#configuring-logrotate">17.2.1.
Configuring
logrotate</a></span></dt></dl></dd><dt><span clas
s="section"><a href="#s1-logfiles-viewing">17.3. Viewing Log
Files</a></span></dt><dt><span
class="section"><a href="#s1-logfiles-adding">17.4. Adding a
Log File</a></span></dt><dt><span
class="section"><a href="#s1-logfiles-examining">17.5.
Monitoring Log Files</a></span></dt><dt><span
class="section"><a
href="#s1-log-files-additional-resources">17.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-log-files-installed-docs">17.6.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-log-files-useful-websites">17.6.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Automating_System_Tasks">18.
Automating System
Tasks</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-autotasks-cron-anacron">18.1.
Cron and Anacron</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-autotasks-cron-service">18.1.1.
Starting and Stopping the Service</a></span></dt><dt><span
class="section"><a
href="#s2-configuring-anacron-jobs">18.1.2. Configuring Anacron
Jobs</a></span></dt><dt><span
class="section"><a href="#s2-configuring-cron-jobs">18.1.3.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a href="#s2-autotasks-cron-access">18.1.4.
Controlling Access to Cron</a></span></dt><dt><span
class="section"><a
href="#s2-black-white-listing-of-cron-jobs">18.1.5. Black/White Listing of
Cron Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-autotasks-at-batch">18.2. At and
Batch</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-autotasks-at-configuring">18.2.1. Configuring At
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-batch-configuring">18.2.2. Configuring Batch
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-viewing">18.2.3. Viewing Pending
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-commandline-options">18.2.4. Additional Comm
and Line Options</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-controlling-access">18.2.5. Controlling Access
to At and Batch</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-service">18.2.6. Starting and Stopping the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-autotasks-additional-resources">18.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-autotasks-installed-docs">18.3.1. Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-abrt">19. Automatic
Bug-Reporting Tool
(ABRT)</a></span></dt><dd><dl><dt><span
class="section"><a href="#id1226654">19.1.
Overview</a></span></dt><dt><span
class="section"><a href="#id976999">19.2. Installing and
Running ABRT</a></span></dt><dt><span
class="section"><a href="#abrt-plugins">19.3. ABRT
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a href="#analyzer-plugins">19.3.1.
Analyzer Plugins</a></span></dt><dt><span
class="section"><a href="#reporter-plugins">19.3.2. Reporter
Plugins</a></span></dt><dt><span
class="section"><a
href="#configuring-plugins-in-the-gui">19.3.3. Plugin Configuration in the
GUI</a></span></dt></dl></dd><dt><span
class="section"><a href="#generating-backtrace">19.4.
Generating
Backtraces</a></span></dt><dd><dl><dt><span
class="section"><a href="#troubleshooting">19.4.1.
Troubleshooting Backtrace
Generation</a></span></dt></dl></dd><dt><span
class="section"><a href="#id424708">19.5. Using the Command
Line Interface</a></span></dt><dd><dl><dt><span
class="section"><a href="#id424722">19.5.1. Viewing
Crashes</a></span></dt><dt><span
class="section"><a href="#id679552">19.5.2. Reporting
Crashes</a></span></dt><dt><span
class="section"><a href="#id568017">19.5.3. Deleting
Crashes</a></span></dt></dl></dd><dt><span
class="section"><a href="#configuring">19.6. Configuring
ABRT</a></span></dt><dt><span
class="section"><a href=
"#configuring-centralized-crash-collection">19.7. Configuring Centralized
Crash Collection</a></span></dt><dd><dl><dt><span
class="section"><a href="#id583691">19.7.1. Testing
ABRT's Crash Detection</a></span></dt><dt><span
class="section"><a href="#testing-upload-method">19.7.2.
Testing the Upload
Method</a></span></dt></dl></dd><dt><span
class="section"><a
href="#configuring-automatic-reporting">19.8. Configuring Automatic
Reporting</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a
href="#part-Kernel_Module_and_Driver_Configuration">VII. Kernel, Module and
Driver
Configuration</a></span></dt><dd><dl><dt><span
class="chapter"><a
href="#ch-Manually_Upgrading_the_Kernel">20. Manually Upgrading the
Kernel</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-kernel-packages">20.1. Overview
of Kernel Packages</a></span></dt><dt><span
class="section"><a href="#s1-kernel-preparing">20.2.
Preparing to Upgrade</a></span></dt><dt><span
class="section"><a href="#s1
-kernel-download">20.3. Downloading the Upgraded
Kernel</a></span></dt><dt><span
class="section"><a href="#s1-kernel-perform-upgrade">20.4.
Performing the Upgrade</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_the_Initial_RAM_Disk_Image">20.5. Verifying the Initial
RAM Disk Image</a></span></dt><dt><span
class="section"><a href="#s1-kernel-boot-loader">20.6.
Verifying the Boot
Loader</a></span></dt><dd><dl><dt><span
class="section"><a href="#s3-kernel-boot-loader-grub">20.6.1.
Configuring the GRUB Boot Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-iseries">20.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-pseries">20.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">21.
Working with Kernel
Modules</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Listing_
Currently-Loaded_Modules">21.1. Listing Currently-Loaded
Modules</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Information_About_a_Module">21.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="#sec-Loading_a_Module">21.3. Loading
a Module</a></span></dt><dt><span
class="section"><a href="#sec-Unloading_a_Module">21.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_Module_Parameters">21.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="#sec-Persistent_Module_Loading">21.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="#sec-Specific_Kernel_Module_Capabilities">21.7. Specific Kernel Module
Capabilities</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Using_Multiple_Ethernet_Cards">21.7.1. Using Multiple Ethernet
Cards</a></span></dt><dt><span
class="section"><a href="#sec-Using_Channel_Bonding">21.7.2.
Using Chan
nel Bonding</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-kernel-modules-additional-resources">21.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-kernel-modules-additional-resources-installed">21.8.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-modules-additional-resources-websites">21.8.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-kdump">22. The kdump Crash
Recovery Service</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-kdump-configuration">22.1.
Configuring the kdump
Service</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-kdump-configuration-gui">22.1.1.
Using the Kernel Dump Configuration
Utility</a></span></dt><dt><span
class="section"><a href="#s2-kdump-configuration-cli">22.1.2.
Configuring kdump on the Command Line</a></span></dt><dt><span
class="section"><a href="#s2-kdump-configuration-testing">
22.1.3. Testing the
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-kdump-crash">22.2. Analyzing the
Core Dump</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-kdump-crash-running">22.2.1.
Running the crash Utility</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-log">22.2.2.
Displaying the Message Buffer</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-backtrace">22.2.3.
Displaying a Backtrace</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-processes">22.2.4.
Displaying a Process Status</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-memory">22.2.5.
Displaying Virtual Memory Information</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-files">22.2.6.
Displaying Open Files</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-exit">22.2.7.
Exiting the
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-kdump-resource
s">22.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-kdump-resources-installed">22.3.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a href="#s2-kdump-resources-online">22.3.2.
Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="appendix"><a href="#ch-RPM">A.
RPM</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-rpm-design">A.1. RPM Design
Goals</a></span></dt><dt><span
class="section"><a href="#s1-rpm-using">A.2. Using
RPM</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-rpm-finding">A.2.1. Finding RPM
Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_and_Upgrading">A.2.2. Installing and
Upgrading</a></span></dt><dt><span
class="section"><a
href="#sec-Configuration_File_Changes">A.2.3. Configuration File
Changes</a></span></dt><dt><span
class="section"><a href="#s2-rpm-uninstalling">A.2.4.
Uninstalling</a></span></dt><dt><span class="sectio
n"><a href="#s2-rpm-freshening">A.2.5.
Freshening</a></span></dt><dt><span
class="section"><a href="#s2-rpm-querying">A.2.6.
Querying</a></span></dt><dt><span
class="section"><a href="#s2-rpm-verifying">A.2.7.
Verifying</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-check-rpm-sig">A.3. Checking a
Package's
Signature</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-keys-importing">A.3.1. Importing
Keys</a></span></dt><dt><span
class="section"><a href="#s2-keys-checking">A.3.2. Verifying
Signature of
Packages</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-rpm-impressing">A.4. Practical
and Common Examples of RPM Usage</a></span></dt><dt><span
class="section"><a href="#s1-rpm-additional-resources">A.5.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-rpm-installed-docs">A.5.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-rpm-useful-websites">A.5.2.
Useful Websites</
a></span></dt><dt><span class="section"><a
href="#s2-rpm-related-books">A.5.3. Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="appendix"><a href="#ch-The_sysconfig_Directory">B. The
sysconfig
Directory</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-sysconfig-files">B.1. Files in
the /etc/sysconfig/
Directory</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysconfig-arpwatch">B.1.1.
/etc/sysconfig/arpwatch </a></span></dt><dt><span
class="section"><a href="#s2-sysconfig-authconfig">B.1.2.
/etc/sysconfig/authconfig </a></span></dt><dt><span
class="section"><a href="#s2-sysconfig-autofs">B.1.3.
/etc/sysconfig/autofs </a></span></dt><dt><span
class="section"><a href="#s2-sysconfig-clock">B.1.4.
/etc/sysconfig/clock </a></span></dt><dt><span
class="section"><a href="#s2-sysconfig-dhcpd">B.1.5.
/etc/sysconfig/dhcpd </a></span></dt><dt><span
class="section"><a href="#s2-sysconfig-firewall">B.1.6.
/etc/sysconfig/firstboot </a></sp
an></dt><dt><span class="section"><a
href="#s2-sysconfig-i18n">B.1.7. /etc/sysconfig/i18n
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-init">B.1.8. /etc/sysconfig/init
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-ip6tables">B.1.9. /etc/sysconfig/ip6tables-config
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-kybd">B.1.10. /etc/sysconfig/keyboard
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-ldap">B.1.11. /etc/sysconfig/ldap
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-named">B.1.12. /etc/sysconfig/named
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-network">B.1.13. /etc/sysconfig/network
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-ntpd">B.1.14. /etc/sysconfig/ntpd
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-quagga">B.1.15. /etc/sysconfig/quagga
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-ra
dvd">B.1.16. /etc/sysconfig/radvd
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-samba">B.1.17. /etc/sysconfig/samba
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-selinux">B.1.18. /etc/sysconfig/selinux
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-sendmail">B.1.19. /etc/sysconfig/sendmail
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-spamd">B.1.20. /etc/sysconfig/spamassassin
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-squid">B.1.21. /etc/sysconfig/squid
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-rcu">B.1.22. /etc/sysconfig/system-config-users
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-vncservers">B.1.23. /etc/sysconfig/vncservers
</a></span></dt><dt><span class="section"><a
href="#s2-sysconfig-xinetd">B.1.24. /etc/sysconfig/xinetd
</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-sysconfig-etcsysconf-dir">B.2.
D
irectories in the /etc/sysconfig/
Directory</a></span></dt><dt><span
class="section"><a
href="#s1-sysconfig-additional-resources">B.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-sysconfig-installed-documentation">B.3.1. Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="appendix"><a href="#ch-proc">C. The proc File
System</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-proc-virtual">C.1. A Virtual
File System</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-proc-viewing">C.1.1. Viewing
Virtual Files</a></span></dt><dt><span
class="section"><a href="#s2-proc-change">C.1.2. Changing
Virtual Files</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-proc-topfiles">C.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">C.2.1.
/proc/buddyinfo </a></span></dt><dt><span class="se
ction"><a href="#s2-proc-cmdline">C.2.2. /proc/cmdline
</a></span></dt><dt><span class="section"><a
href="#s2-proc-cpuinfo">C.2.3. /proc/cpuinfo
</a></span></dt><dt><span class="section"><a
href="#s2-proc-crypto">C.2.4. /proc/crypto
</a></span></dt><dt><span class="section"><a
href="#s2-proc-devices">C.2.5. /proc/devices
</a></span></dt><dt><span class="section"><a
href="#s2-proc-dma">C.2.6. /proc/dma
</a></span></dt><dt><span class="section"><a
href="#s2-proc-execdomains">C.2.7. /proc/execdomains
</a></span></dt><dt><span class="section"><a
href="#s2-proc-fb">C.2.8. /proc/fb
</a></span></dt><dt><span class="section"><a
href="#s2-proc-filesystems">C.2.9. /proc/filesystems
</a></span></dt><dt><span class="section"><a
href="#s2-proc-interrupts">C.2.10. /proc/interrupts
</a></span></dt><dt><span class="section"><a
href="#s2-proc-iomem">C.2.11. /proc/iomem
</a></span></dt><dt><span class="section"><a
href="#s2-proc-ioports">C.2.12. /proc/ioports
</a></span></dt><dt><s
pan class="section"><a href="#s2-proc-kcore">C.2.13.
/proc/kcore </a></span></dt><dt><span
class="section"><a href="#s2-proc-kmsg">C.2.14. /proc/kmsg
</a></span></dt><dt><span class="section"><a
href="#s2-proc-loadavg">C.2.15. /proc/loadavg
</a></span></dt><dt><span class="section"><a
href="#s2-proc-locks">C.2.16. /proc/locks
</a></span></dt><dt><span class="section"><a
href="#s2-proc-mdstat">C.2.17. /proc/mdstat
</a></span></dt><dt><span class="section"><a
href="#s2-proc-meminfo">C.2.18. /proc/meminfo
</a></span></dt><dt><span class="section"><a
href="#s2-proc-misc">C.2.19. /proc/misc
</a></span></dt><dt><span class="section"><a
href="#s2-proc-modules">C.2.20. /proc/modules
</a></span></dt><dt><span class="section"><a
href="#s2-proc-mounts">C.2.21. /proc/mounts
</a></span></dt><dt><span class="section"><a
href="#s2-proc-mtrr">C.2.22. /proc/mtrr
</a></span></dt><dt><span class="section"><a
href="#s2-proc-partitions">C.2.23. /proc/partitions
</a></span></dt><dt><sp
an class="section"><a href="#s2-proc-slabinfo">C.2.24.
/proc/slabinfo </a></span></dt><dt><span
class="section"><a href="#s2-proc-stat">C.2.25. /proc/stat
</a></span></dt><dt><span class="section"><a
href="#s2-proc-swaps">C.2.26. /proc/swaps
</a></span></dt><dt><span class="section"><a
href="#s2-proc-sysrq-trigger">C.2.27. /proc/sysrq-trigger
</a></span></dt><dt><span class="section"><a
href="#s2-proc-uptime">C.2.28. /proc/uptime
</a></span></dt><dt><span class="section"><a
href="#s2-proc-version">C.2.29. /proc/version
</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-proc-directories">C.3.
Directories within
/proc/</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-proc-processdirs">C.3.1. Process
Directories</a></span></dt><dt><span
class="section"><a href="#s2-proc-dir-bus">C.3.2. /proc/bus/
</a></span></dt><dt><span class="section"><a
href="#s2-proc-pci">C.3.3. /proc/bus/pci
</a></span></dt><dt><span class="section"><a
href="#s2-proc-dir
-driver">C.3.4. /proc/driver/
</a></span></dt><dt><span class="section"><a
href="#s2-proc-dir-fs">C.3.5. /proc/fs
</a></span></dt><dt><span class="section"><a
href="#s2-proc-dir-irq">C.3.6. /proc/irq/
</a></span></dt><dt><span class="section"><a
href="#s2-proc-dir-net">C.3.7. /proc/net/
</a></span></dt><dt><span class="section"><a
href="#s2-proc-dir-scsi">C.3.8. /proc/scsi/
</a></span></dt><dt><span class="section"><a
href="#s2-proc-dir-sys">C.3.9. /proc/sys/
</a></span></dt><dt><span class="section"><a
href="#s2-proc-dir-sysvipc">C.3.10. /proc/sysvipc/
</a></span></dt><dt><span class="section"><a
href="#s2-proc-tty">C.3.11. /proc/tty/
</a></span></dt><dt><span class="section"><a
href="#s2-proc-pid">C.3.12. /proc/<em
class="replaceable"><code>PID</code></em>/
</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-proc-sysctl">C.4. Using the
sysctl Command</a></span></dt><dt><span
class="section"><a href="#s1-proc-additional-resources">C.5.
References</a></
span></dt></dl></dd><dt><span
class="appendix"><a href="#app-Revision_History">D. Revision
History</a></span></dt><dt><span
class="index"><a
href="#id895660">Index</a></span></dt></dl></div><div
xml:lang="en-US" class="preface" id="id663216"
lang="en-US"><div
class="titlepage"><div><div><h1 id="id663216"
class="title">Preface</h1></div></div></div><div
class="para">
+ The <em class="citetitle">Deployment Guide</em> contains
information on how to customize the Fedora 15 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">
+ This manual discusses many intermediate topics such as the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Installing and managing packages using the graphical <span
class="application"><strong>PackageKit</strong></span> and
command line <span
class="application"><strong>Yum</strong></span> package
managers
+ </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 user-space crash data
with the <span class="application"><strong>Automatic Bug Reporting
Tool</strong></span>, and 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"
id="sect-Preface-Target_Audience">1. Target
Audience</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 <em class="citetitle">Fedora 15
Installation Guide</em>.
+ </div></div><div class="section"
id="sect-Preface-Book_Organization"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Preface-Book_Organization">2. How to Read this
Book</h2></div></div></div><div class="para">
+ This manual is divided into the following main categories:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
class="xref" href="#part-Basic_System_Configuration">Part I, “Basic
System Configuration”</a></span></dt><dd><div
class="para">
+ This part covers basic system administration tasks such as keyboard configuration,
date and time configuration, and managing users and groups.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Language_and_Keyboard_Configuration">Chapter 1, <em>Language
and Keyboard Configuration</em></a> covers basic language and keyboard setup.
Read this chapter if you need to configure the language of your desktop, change the
keyboard layout, or add the keyboard layout indicator to the panel.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Date_and_Time_Configuration">Chapter 2, <em>Date and Time
Configuration</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">Chapter 3, <em>Managing Users and
Groups</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">Part II, “Package
Management”</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">Chapter 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">Chapter 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">Part III,
“Networking”</a></span></dt><dd><div
class="para">
+ This part describes how to configure the network on Fedora.
+ </div><div class="para">
+ <a class="xref" href="#ch-Network_Interfaces">Chapter 6,
<em>Network Interfaces</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">Part IV, “Infrastructure
Services”</a></span></dt><dd><div class="para">
+ This part provides information how to configure services and daemons, configure
authentication, and enable remote logins.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> explains the concept of runlevels, and describes how to set
the default one. It also covers the configuration of the services to be run in each of
these runlevels, and provides information on how to start, stop, and restart a service.
Read this chapter to learn how to manage services on your system.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Configuring_Authentication">Chapter 8, <em>Configuring
Authentication</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">Chapter 9,
<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">Part V,
“Servers”</a></span></dt><dd><div class="para">
+ This part discusses various topics related to servers such as how to set up a Web
server or share files and directories over the network.
+ </div><div class="para">
+ <a class="xref" href="#ch-DHCP_Servers">Chapter 10,
<em>DHCP Servers</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">Chapter 11,
<em>DNS Servers</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">Chapter 12,
<em>Web Servers</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">Chapter 13,
<em>Mail Servers</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">Chapter 14,
<em>Directory Servers</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">Chapter 15, <em>File
Servers</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. Read this chapter if you need to configure a file
server on your system.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="#part-Monitoring_and_Automation">Part VI, “Monitoring and
Automation”</a></span></dt><dd><div class="para">
+ This part describes various tools that allow system administrators to monitor
system performance, automate system tasks, and report bugs.
+ </div><div class="para">
+ <a class="xref"
href="#ch-System_Monitoring_Tools">Chapter 16, <em>System Monitoring
Tools</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">Chapter 17, <em>Viewing and
Managing Log Files</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">Chapter 18, <em>Automating System
Tasks</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-abrt">Chapter 19,
<em>Automatic Bug-Reporting Tool (ABRT)</em></a> concentrates on
<span class="application"><strong>ABRT</strong></span>,
a system service and a set of tools to collect crash data and send a report to the
relevant issue tracker. Read this chapter to learn how to use <span
class="application"><strong>ABRT</strong></span> on your
system.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="#part-Kernel_Module_and_Driver_Configuration">Part VII, “Kernel, Module
and Driver Configuration”</a></span></dt><dd><div
class="para">
+ This part covers various tools that assist administrators with kernel
customization.
+ </div><div class="para">
+ <a class="xref"
href="#ch-Manually_Upgrading_the_Kernel">Chapter 20, <em>Manually
Upgrading the Kernel</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">Chapter 21, <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">Chapter 22,
<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="#ch-RPM">Appendix A,
<em>RPM</em></a></span></dt><dd><div
class="para">
+ This appendix concentrates on the RPM Package Manager (RPM), an open packaging
system used by Fedora, and the use of the <code
class="command">rpm</code> utility. Read this appendix if you need to
use <code class="command">rpm</code> instead of <code
class="command">yum</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="#ch-The_sysconfig_Directory">Appendix B, <em>The sysconfig
Directory</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">Appendix C, <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="en-US" class="section" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="id676498">3. Document
Conventions</h2></div></div></div><div
class="para">
+ This manual uses several conventions to highlight certain words and phrases and draw
attention to specific pieces of information.
+ </div><div class="para">
+ In PDF and paper editions, this manual uses typefaces drawn from the <a
href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>
set. The Liberation Fonts set is also used in HTML editions if the set is installed on
your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat
Enterprise Linux 5 and later includes the Liberation Fonts set by default.
+ </div><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id390360">3.1. Typographic
Conventions</h3></div></div></div><div
class="para">
+ Four typographic conventions are used to call attention to specific words and phrases.
These conventions, and the circumstances they apply to, are as follows.
+ </div><div class="para">
+ <code class="literal">Mono-spaced Bold</code>
+ </div><div class="para">
+ Used to highlight system input, including shell commands, file names and paths. Also
used to highlight keycaps and key combinations. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ To see the contents of the file <code
class="filename">my_next_bestselling_novel</code> in your current
working directory, enter the <code class="command">cat
my_next_bestselling_novel</code> command at the shell prompt and press <span
class="keycap"><strong>Enter</strong></span> to execute the
command.
+ </div></blockquote></div><div class="para">
+ The above includes a file name, a shell command and a keycap, all presented in
mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps by the hyphen connecting each part
of a key combination. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ Press <span
class="keycap"><strong>Enter</strong></span> to execute the
command.
+ </div><div class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> to switch to the
first virtual terminal. Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F1</strong></span> to return to your
X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights
two key combinations (each a set of three keycaps with each set pressed simultaneously).
+ </div><div class="para">
+ If source code is discussed, class names, methods, functions, variable names and
returned values mentioned within a paragraph will be presented as above, in <code
class="literal">mono-spaced bold</code>. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ File-related classes include <code
class="classname">filesystem</code> for file systems, <code
class="classname">file</code> for files, and <code
class="classname">dir</code> for directories. Each class has its own
associated set of permissions.
+ </div></blockquote></div><div class="para">
+ <span class="application"><strong>Proportional
Bold</strong></span>
+ </div><div class="para">
+ This denotes words or phrases encountered on a system, including application names;
dialog box text; labeled buttons; check-box and radio button labels; menu titles and
sub-menu titles. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ Choose <span
class="guimenu"><strong>System</strong></span> → <span
class="guisubmenu"><strong>Preferences</strong></span> →
<span class="guimenuitem"><strong>Mouse</strong></span>
from the main menu bar to launch <span
class="application"><strong>Mouse
Preferences</strong></span>. In the <span
class="guilabel"><strong>Buttons</strong></span> tab, click
the <span class="guilabel"><strong>Left-handed
mouse</strong></span> check box and click <span
class="guibutton"><strong>Close</strong></span> to switch
the primary mouse button from the left to the right (making the mouse suitable for use in
the left hand).
+ </div><div class="para">
+ To insert a special character into a <span
class="application"><strong>gedit</strong></span> file,
choose <span
class="guimenu"><strong>Applications</strong></span> →
<span
class="guisubmenu"><strong>Accessories</strong></span> →
<span class="guimenuitem"><strong>Character
Map</strong></span> from the main menu bar. Next, choose <span
class="guimenu"><strong>Search</strong></span> → <span
class="guimenuitem"><strong>Find…</strong></span> from the
<span class="application"><strong>Character
Map</strong></span> menu bar, type the name of the character in the <span
class="guilabel"><strong>Search</strong></span> field and
click <span
class="guibutton"><strong>Next</strong></span>. The
character you sought will be highlighted in the <span
class="guilabel"><strong>Character Table</strong></span>.
Double-click this highlighted character to place it in the <span
class="guilabel"><strong>Text to copy</strong></span> field
and then click the <span class="guibutton"><stron
g>Copy</strong></span> button. Now switch back to your document and choose
<span class="guimenu"><strong>Edit</strong></span> →
<span class="guimenuitem"><strong>Paste</strong></span>
from the <span
class="application"><strong>gedit</strong></span> menu
bar.
+ </div></blockquote></div><div class="para">
+ The above text includes application names; system-wide menu names and items;
application-specific menu names; and buttons and text found within a GUI interface, all
presented in proportional bold and all distinguishable by context.
+ </div><div class="para">
+ <code class="command"><em
class="replaceable"><code>Mono-spaced Bold
Italic</code></em></code> or <span
class="application"><strong><em
class="replaceable"><code>Proportional Bold
Italic</code></em></strong></span>
+ </div><div class="para">
+ Whether mono-spaced bold or proportional bold, the addition of italics indicates
replaceable or variable text. Italics denotes text you do not input literally or displayed
text that changes depending on circumstance. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ To connect to a remote machine using ssh, type <code
class="command">ssh <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>domain.name</code></em></code>
at a shell prompt. If the remote machine is <code
class="filename">example.com</code> and your username on that machine
is john, type <code class="command">ssh john(a)example.com</code>.
+ </div><div class="para">
+ The <code class="command">mount -o remount <em
class="replaceable"><code>file-system</code></em></code>
command remounts the named file system. For example, to remount the <code
class="filename">/home</code> file system, the command is <code
class="command">mount -o remount /home</code>.
+ </div><div class="para">
+ To see the version of a currently installed package, use the <code
class="command">rpm -q <em
class="replaceable"><code>package</code></em></code>
command. It will return a result as follows: <code class="command"><em
class="replaceable"><code>package-version-release</code></em></code>.
+ </div></blockquote></div><div class="para">
+ Note the words in bold italics above — username, domain.name, file-system, package,
version and release. Each word is a placeholder, either for text you enter when issuing a
command or for text displayed by the system.
+ </div><div class="para">
+ Aside from standard usage for presenting the title of a work, italics denotes the
first use of a new and important term. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ Publican is a <em class="firstterm">DocBook</em> publishing
system.
+ </div></blockquote></div></div><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id1305126">3.2. Pull-quote
Conventions</h3></div></div></div><div
class="para">
+ Terminal output and source code listings are set off visually from the surrounding
text.
+ </div><div class="para">
+ Output sent to a terminal is set in <code
class="computeroutput">mono-spaced roman</code> and presented thus:
+ </div><pre class="screen">books Desktop documentation
drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</pre><div
class="para">
+ Source-code listings are also set in <code
class="computeroutput">mono-spaced roman</code> but add syntax
highlighting as follows:
+ </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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id543787">3.3. Notes and
Warnings</h3></div></div></div><div class="para">
+ Finally, we use three visual styles to draw attention to information that might
otherwise be overlooked.
+ </div><div class="note"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a
note should have no negative consequences, but you might miss out on a trick that makes
your life easier.
+ </div></div></div><div class="important"><div
class="admonition_header"><h2>Important</h2></div><div
class="admonition"><div class="para">
+ Important boxes detail things that are easily missed: configuration changes that only
apply to the current session, or services that need restarting before an update will
apply. Ignoring a box labeled 'Important' will not cause data loss but may cause
irritation and frustration.
+ </div></div></div><div class="warning"><div
class="admonition_header"><h2>Warning</h2></div><div
class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div></div><div
xml:lang="en-US" class="section" id="sect-Preface-Feedback"
lang="en-US"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Preface-Feedback">4. Feedback</h2></div></div></div><a
id="id634714" 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">
+ When submitting a bug report, be sure to provide the following information:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Manual's identifier: <code
class="literal">deployment-guide</code>
+ </div></li><li class="listitem"><div
class="para">
+ Version number: <code class="literal">15</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"
id="pref-Acknowledgments">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/h...;.
+ </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, KarstenWade, Lucy Ringland,
Marcela Mašláňová, Mark Johnson, Michael Behm, Michael Behm, Miroslav Lichvár, Radek
Vokál, Rahul Kavalapara, Rahul Sundaram, Sandra Moore, Zbyšek Mráz and Jan Včelák, 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">Part I. Basic System
Configuration</h1></div></div></div><div
class="partintro" id="id1456022"><div></div><div
class="para">
+ This part covers basic system administration tasks such as keyboard configuration,
date and time configuration, and managing users and groups.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a
href="#ch-Language_and_Keyboard_Configuration">1. Language and Keyboard
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Language_and_Keyboard_Configuration-Language">1.1. Changing the
Language</a></span></dt><dt><span
class="section"><a
href="#sect-Language_and_Keyboard_Configuration-Layouts">1.2. Changing the
Keyboard Layout</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#ch-Date_and_Time_Configuration">2.
Date and Time
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Date_and_Time">2.1. Date and Time
Configuration Tool</a></span></dt><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">2.2.
Command Line
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration
-Date_and_Time">2.2.1. Configuring the Date and
Time</a></span></dt><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">2.2.2.
Configuring the Network Time
Protocol</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Additional_Resources">2.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation">2.3.1.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Managing_Users_and_Groups">3.
Managing Users and
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts">3.1. User Accounts
Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.1.1.
Configuring an Account</a></span></dt><dt><span class="
section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">3.1.2.
Adding a New User</a></span></dt><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.1.3.
Removing a User</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-configui">3.2. User
Manager Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-redhat-config-users-user-new">3.2.1. Adding a New
User</a></span></dt><dt><span
class="section"><a
href="#s2-redhat-config-users-group-new">3.2.2. Adding a New
Group</a></span></dt><dt><span
class="section"><a
href="#s2-redhat-config-users-group-properties">3.2.3. Modifying Group
Properties</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-tools">3.3. User and Group
Management Tools</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-users-cmd-line">3.3.1. Command
Line Configuration</a></span></dt><dt><span
class="section"><a href="#s2-redhat-c
onfig-users-process">3.3.2. Explaining the
Process</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-users-groups-standard-users">3.4. Standard
Users</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-standard-groups">3.5. Standard
Groups</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-private-groups">3.6. User Private
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-users-groups-rationale">3.6.1.
Group
Directories</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-users-groups-shadow-utilities">3.7. Shadow
Passwords</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-additional-resources">3.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-users-groups-documentation">3.8.1. Installed
Documentation</a></span></dt></dl></dd></dl></dd></dl></div></div><div
xml:lang="en-US" class="chapter"
id="ch-Language_and_Keyboard_Configuration" lang="en-US"><
div class="titlepage"><div><div><h2
class="title">Chapter 1. Language and Keyboard
Configuration</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#sect-Language_and_Keyboard_Configuration-Language">1.1. Changing the
Language</a></span></dt><dt><span
class="section"><a
href="#sect-Language_and_Keyboard_Configuration-Layouts">1.2. Changing the
Keyboard Layout</a></span></dt></dl></div><div
class="para">
+ This chapter describes how to change the language of your desktop, configure the
keyboard layout, and allow a user to switch between different keyboard layouts using the
<span class="application"><strong>Region and
Language</strong></span> configuration tool.
+ </div><div class="section"
id="sect-Language_and_Keyboard_Configuration-Language"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Language_and_Keyboard_Configuration-Language">1.1. Changing the
Language</h2></div></div></div><a id="id629072"
class="indexterm"></a><a id="id829196"
class="indexterm"></a><div class="para">
+ To configure the language of your desktop, open the <span
class="application"><strong>System Settings</strong></span>
dialog window by selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Settings</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu,
click <span class="guimenuitem"><strong>Region and
Language</strong></span>, and select the <span
class="guilabel"><strong>Language</strong></span> tab. You
will be presented with a list of available languages.
+ </div><div class="figure"
id="fig-Language_and_Keyboard_Configuration-Language"><div
class="figure-contents"><div class="mediaobject"><img
src="images/region-and-language-language.png" alt="Changing the
language" /><div class="longdesc"><div
class="para">
+ Changing the language
+ </div></div></div></div><h6>Figure 1.1. Changing the
language</h6></div><br class="figure-break" /><div
class="para">
+ To choose a particular language, select it from the list and either close the window,
or click the <span class="guibutton"><strong>All
Settings</strong></span> button in the upper-left corner of the window to
return to the <span class="application"><strong>System
Settings</strong></span> window. The changes will take effect the next time
you log in to your system.
+ </div></div><div class="section"
id="sect-Language_and_Keyboard_Configuration-Layouts"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Language_and_Keyboard_Configuration-Layouts">1.2. Changing the
Keyboard Layout</h2></div></div></div><a
id="id465371" class="indexterm"></a><a
id="id565959" class="indexterm"></a><div
class="para">
+ Although the installation program allows a system administrator to configure a
keyboard layout during the system installation, the default settings may not always suit
your current needs. To add a new keyboard layout, open the <span
class="application"><strong>System Settings</strong></span>
window by selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Settings</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu,
click the <span class="guimenuitem"><strong>Region and
Language</strong></span> icon, and select the <span
class="guilabel"><strong>Layouts</strong></span> tab.
+ </div><div class="figure"
id="fig-Language_and_Keyboard_Configuration-Layouts"><div
class="figure-contents"><div class="mediaobject"><img
src="images/region-and-language-layouts.png" alt="Changing the keyboard
layout" /><div class="longdesc"><div
class="para">
+ Changing the keyboard layout
+ </div></div></div></div><h6>Figure 1.2. Changing the
keyboard layout</h6></div><br class="figure-break" /><div
class="para">
+ The left part of the window provides a list of currently enabled layouts, while the
right part allows you to choose whether to use the same keyboard layout for all windows,
or if you prefer to use a different layout for each window.
+ </div><div class="para">
+ To add a keyboard layout, click the <span
class="guibutton"><strong>+</strong></span> (that is, the
plus sign) button below the list. A dialog box will appear, allowing you to select the
desired layout. The input field in the bottom part of the dialog box allows you to reduce
the number of displayed items by typing part of the layout name (such as <span
class="quote">“<span
class="quote">slov</span>”</span> for Slovak layouts) in it. Once
you are done, click the <span
class="guibutton"><strong>Add</strong></span> button to
confirm your choice.
+ </div><div class="figure"
id="fig-Language_and_Keyboard_Configuration-Layouts-Add"><div
class="figure-contents"><div class="mediaobject"><img
src="images/region-and-language-layouts-add.png" alt="Adding a keyboard
layout" /><div class="longdesc"><div
class="para">
+ Adding a keyboard layout
+ </div></div></div></div><h6>Figure 1.3. Adding a
keyboard layout</h6></div><br class="figure-break" /><div
class="para">
+ To remove a keyboard layout, click the <span
class="guibutton"><strong>−</strong></span> (that is, the
minus sign) button below the list.
+ </div><div class="para">
+ When more than one layout is enabled, a keyboard indicator appears on the panel in
order to allow you to switch between the layouts, and the first layout in the list is
considered the default. To move a particular layout up or down in the list, select it from
the list and click the <span
class="guibutton"><strong>↑</strong></span> (the upwards
arrow) or <span
class="guibutton"><strong>↓</strong></span> (the downwards
arrow) buttons respectively.
+ </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="The keyboard
layout indicator" /><div class="longdesc"><div
class="para">
+ The keyboard layout indicator
+ </div></div></div></div><h6>Figure 1.4. The keyboard
layout indicator</h6></div><br class="figure-break" /><div
class="para">
+ The changes take effect immediately.
+ </div></div></div><div xml:lang="en-US"
class="chapter" id="ch-Date_and_Time_Configuration"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 2. Date and Time
Configuration</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#sect-Date_and_Time_Configuration-Date_and_Time">2.1. Date and Time
Configuration Tool</a></span></dt><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">2.2.
Command Line
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">2.2.1.
Configuring the Date and Time</a></span></dt><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">2.2.2.
Configuring the Network Time
Protocol</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Additional_Resources">2.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation">2.3.1.
Additional
Resources</a></span></dt></dl></dd></dl></div><div
class="para">
+ This chapter covers setting the system date and time in Fedora, both manually and using
the Network Time Protocol (<abbr class="abbrev">NTP</abbr>), as well
as setting the adequate time zone. Two methods are covered: setting the date and time
using the <span class="application"><strong>Date and
Time</strong></span> configuration tool, and doing so on the command line.
+ </div><div class="section"
id="sect-Date_and_Time_Configuration-Date_and_Time"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Date_and_Time_Configuration-Date_and_Time">2.1. Date and Time
Configuration Tool</h2></div></div></div><div
class="para">
+ The <span class="application"><strong>Date and
Time</strong></span> configuration tool allows a user to change the system
date and time, to configure the time zone used by the system, and to set up the Network
Time Protocol daemon to synchronize the system clock with a time server.
+ </div><div class="para">
+ To start the tool, select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Settings</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu and
click the <span class="guimenuitem"><strong>Date and
Time</strong></span> icon, or click the time in the panel and select <span
class="guibutton"><strong>Date and Time
Settings</strong></span> from the drop-down menu.
+ </div><div class="figure"
id="fig-Date_and_Time_Configuration-Time"><div
class="figure-contents"><div class="mediaobject"><img
src="images/date-and-time-panel.png" alt="Running the Date and Time
configuration tool" /><div class="longdesc"><div
class="para">
+ Running the Date and Time configuration tool
+ </div></div></div></div><h6>Figure 2.1. Running the
Date and Time configuration tool</h6></div><br
class="figure-break" /><div class="para">
+ By default, the tool only allows you to review the current settings. This is because
only <code class="systemitem">root</code> is allowed to set the
system date and time. To unlock the configuration tool for changes, click the <span
class="guibutton"><strong>Unlock</strong></span> button in
the bottom-left corner of the window, and provide the root password when prompted.
+ </div><div class="figure"
id="fig-Date_and_Time_Configuration-Date_and_Time"><div
class="figure-contents"><div class="mediaobject"><img
src="images/date-and-time-settings.png" alt="The Date and Time
configuration tool" /><div class="longdesc"><div
class="para">
+ The Date and Time configuration tool
+ </div></div></div></div><h6>Figure 2.2. The Date and
Time configuration tool</h6></div><br class="figure-break"
/><div class="para">
+ As you can see in <a class="xref"
href="#fig-Date_and_Time_Configuration-Date_and_Time">Figure 2.2, “The Date
and Time configuration tool”</a>, the main window of the <span
class="application"><strong>Date and Time</strong></span>
configuration tool is divided into two parts: while the left side of the window is
dedicated to the time zone settings, the right part allows you to configure the date and
time itself.
+ </div><a id="id954081"
class="indexterm"></a><a id="id954094"
class="indexterm"></a><div class="para">
+ To change the time zone, click on the map, or select the region and city from the
<span class="guilabel"><strong>Region</strong></span>
and <span class="guilabel"><strong>City</strong></span>
drop-down lists.
+ </div><a id="id834054"
class="indexterm"></a><a id="id834068"
class="indexterm"></a><div class="para">
+ To change the current time of your system, either configure the system to synchronize
it over the network by clicking the <span
class="guilabel"><strong>Network Time</strong></span>
switch, or set it manually by clicking the up and down arrows above and below the numbers.
Use the <span class="guilabel"><strong>24-Hour
Time</strong></span> switch to enable or disable the 24-hour time format.
+ </div><a id="id506514"
class="indexterm"></a><a id="id506528"
class="indexterm"></a><div class="para">
+ To change the current date of your system, select a month from the drop-down list
below the time, and use the up and down arrows to choose the day and year.
+ </div><div class="para">
+ The changes take effect immediately.
+ </div></div><div class="section"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration">2.2. Command
Line Configuration</h2></div></div></div><div
class="para">
+ In case your system does not have the <span
class="application"><strong>Date/Time
Properties</strong></span> tool installed, or the <span
class="emphasis"><em>X Window Server</em></span> is not
running, you can change the system date and time on the command line. Note that in order
to perform actions described in this section, you have to be logged in as <code
class="systemitem">root</code>. To do so, type the following at a shell
prompt:
+ </div><pre class="screen"><code
class="command">su -</code></pre><div
class="section"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">2.2.1. Configuring
the Date and Time</h3></div></div></div><a
id="id422708" class="indexterm"></a><a
id="id422716" class="indexterm"></a><div
class="para">
+ The <code class="command">date</code> command allows the
superuser to set the system date and time manually:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ To change the current date, type the command in the following form at a shell
prompt, replacing the <em
class="replaceable"><code>YYYY</code></em> with a
four-digit year, <em
class="replaceable"><code>MM</code></em> with a two-digit
month, and <em class="replaceable"><code>DD</code></em>
with a two-digit day of the month:
+ </div><pre class="screen"><code
class="command">date +%D -s <em
class="replaceable"><code>YYYY-MM-DD</code></em></code></pre><div
class="para">
+ For example, to set the date to 2 June 2010, type:
+ </div><pre class="screen">~]# <code
class="command">date +%D -s
2010-06-02</code></pre></li><li class="step"><div
class="para">
+ To change the current date, use the following command, where <em
class="replaceable"><code>HH</code></em> stands for an
hour, <em class="replaceable"><code>MM</code></em> is a
minute, and <em class="replaceable"><code>SS</code></em>
is a second, all typed in a two-digit form:
+ </div><pre class="screen"><code
class="command">date +%T -s <em
class="replaceable"><code>HH:MM:SS</code></em></code></pre><div
class="para">
+ If your system clock is set to use <acronym
class="acronym">UTC</acronym> (Coordinated Universal Time), add the
following option:
+ </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">
+ For instance, to set the system clock to 11:26 PM using the <acronym
class="acronym">UTC</acronym>, type:
+ </div><pre class="screen">~]# <code
class="command">date +%T -s 23:26:00
-u</code></pre></li></ol></div><div
class="para">
+ You can check your current settings by typing <code
class="command">date</code> without any additional argument, for
example:
+ </div><pre class="screen">~]$ <code
class="command">date</code>
+Wed Jun 2 11:58:48 CEST 2010</pre></div><div class="section"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">2.2.2. Configuring
the Network Time Protocol</h3></div></div></div><a
id="id641931" class="indexterm"></a><a
id="id641943" class="indexterm"></a><a
id="id641951" class="indexterm"></a><a
id="id430214" class="indexterm"></a><div
class="para">
+ As opposed to the manual setup described above, you can also synchronize the system
clock with a remote server over the Network Time Protocol (<acronym
class="acronym">NTP</acronym>). For the one-time synchronization only,
use the <span
class="application"><strong>ntpdate</strong></span>
command:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Check whether the selected NTP server is accessible by using the <code
class="command">ntpdate</code> command in the following form:
+ </div><pre class="screen"><code
class="command">ntpdate -q <em
class="replaceable"><code>server_address</code></em></code></pre><div
class="para">
+ For example, to connect to <code
class="systemitem">0.fedora.pool.ntp.org</code>, type:
+ </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
+23 May 01:05:54 ntpdate[10619]: step time server 204.15.208.61 offset -39.275438
sec</pre></li><li class="step"><div
class="para">
+ When you find a satisfactory server, run the <span
class="application"><strong>ntpdate</strong></span> command
followed with one or more server addresses:
+ </div><pre class="screen"><code
class="command">ntpdate <em
class="replaceable"><code>server_address...</code></em></code></pre><div
class="para">
+ For instance:
+ </div><pre class="screen">~]# <code
class="command">ntpdate
0.fedora.pool.ntp.org
1.fedora.pool.ntp.org</code>
+23 May 01:07:13 ntpdate[10669]: step time server 204.15.208.61 offset -39.275436
sec</pre><div class="para">
+ Unless an error message is displayed, the system time should now be set. You can
check the current by setting typing <code
class="command">date</code> without any additional arguments as shown
in <a class="xref"
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">Section 2.2.1,
“Configuring the Date and Time”</a>.
+ </div></li><li class="step"><div
class="para">
+ In most cases, these steps are sufficient. Only if you really need one or more
system services to always use the correct time, enable running the <span
class="application"><strong>ntpdate</strong></span> at boot
time:
+ </div><pre class="screen"><code
class="command">systemctl enable
ntpdate.service</code></pre><div class="para">
+ For more information about system services and their setup, refer to <a
class="xref" href="#ch-Services_and_Daemons">Chapter 7,
<em>Services and Daemons</em></a>.
+ </div><div class="note"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ If the synchronization with the time server at boot time keeps failing, that is,
you find a relevant error message in the <code
class="filename">/var/log/boot.log</code> system log, try to add the
following line to <code
class="filename">/etc/sysconfig/network</code>:
+ </div><pre
class="screen">NETWORKWAIT=1</pre></div></div></li></ol></div><a
id="id671189" class="indexterm"></a><a
id="id671201" class="indexterm"></a><a
id="id671209" class="indexterm"></a><a
id="id834130" class="indexterm"></a><div
class="para">
+ However, the more convenient way is to set the <code
class="systemitem">ntpd</code> daemon to synchronize the time at boot
time automatically:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Open the NTP configuration file <code
class="filename">/etc/ntp.conf</code> in a text editor, creating a new
one if it does not already exist.
+ </div></li><li class="step"><div
class="para">
+ Add or edit the list of public NTP servers. If you are using Fedora 15, the file
should already contain the following lines, but feel free to change or expand these
according to your needs:
+ </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>Speeding up initial
synchronization</h2></div><div class="admonition"><div
class="para">
+ To speed the initial synchronization up, it is recommended that the <code
class="command">iburst</code> directive is added at the end of each
server line.
+ </div></div></div></li><li
class="step"><div class="para">
+ In the same file, set the proper permissions, giving the unrestricted access to
localhost only:
+ </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">
+ Save the changes, exit the editor, and restart the NTP daemon:
+ </div><pre class="screen"><code
class="command">systemctl restart
ntpd.service</code></pre></li><li class="step"><div
class="para">
+ Additionally, make sure that <code
class="command">ntpd</code> daemon is started at boot time:
+ </div><pre class="screen"><code
class="command">systemctl enable
ntpd.service</code></pre></li></ol></div></div></div><div
class="section"
id="sect-Date_and_Time_Configuration-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Date_and_Time_Configuration-Additional_Resources">2.3. Additional
Resources</h2></div></div></div><div
class="para">
+ For more information about the date and time configuration, refer to the following
resources.
+ </div><div class="section"
id="sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation">2.3.1. Additional
Resources</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="literal">date</code>(1) — The manual page for
the <span
class="application"><strong>date</strong></span> utility.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">ntpdate</code>(8) — The manual page for
the <span
class="application"><strong>ntpdate</strong></span>
utility.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">ntpd</code>(8) — The manual page for
the <code class="systemitem">ntpd</code> service.
+ </div></li></ul></div></div></div></div><div
xml:lang="en-US" class="chapter"
id="ch-Managing_Users_and_Groups" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 3. Managing Users and
Groups</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts">3.1. User Accounts
Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.1.1.
Configuring an Account</a></span></dt><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">3.1.2.
Adding a New User</a></span></dt><dt><span
class="section"><a
href="#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.1.3.
Removing a User</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-configui">3.2. User
Manager Tool</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-redhat-config-users-u
ser-new">3.2.1. Adding a New
User</a></span></dt><dt><span
class="section"><a
href="#s2-redhat-config-users-group-new">3.2.2. Adding a New
Group</a></span></dt><dt><span
class="section"><a
href="#s2-redhat-config-users-group-properties">3.2.3. Modifying Group
Properties</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-users-tools">3.3. User and Group
Management Tools</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-users-cmd-line">3.3.1. Command
Line Configuration</a></span></dt><dt><span
class="section"><a
href="#s2-redhat-config-users-process">3.3.2. Explaining the
Process</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-users-groups-standard-users">3.4. Standard
Users</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-standard-groups">3.5. Standard
Groups</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-private-groups">3.6. User Private
Groups</a></span></dt><dd><dl><dt><span
class="section"><a h
ref="#s2-users-groups-rationale">3.6.1. Group
Directories</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-users-groups-shadow-utilities">3.7. Shadow
Passwords</a></span></dt><dt><span
class="section"><a
href="#s1-users-groups-additional-resources">3.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-users-groups-documentation">3.8.1. Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id620971" class="indexterm"></a><a
id="id1458535" class="indexterm"></a><a
id="id388635" class="indexterm"></a><a
id="id1443239" class="indexterm"></a><div
class="para">
+ The control of <em class="firstterm">users</em> and <em
class="firstterm">groups</em> is a core element of Fedora system
administration. Users can be either people (meaning accounts tied to physical users) or
accounts which exist for specific applications to use. Groups are logical expressions of
organization, tying users together for a common purpose. Users within a group can read,
write, or execute files owned by that group.
+ </div><div class="para">
+ Each user is associated with a unique numerical identification number called a <em
class="firstterm">userid</em> (<em
class="firstterm">UID</em>); likewise, each group is associated with a
<em class="firstterm">groupid</em> (<em
class="firstterm">GID</em>).
+ </div><div class="para">
+ A user who creates a file is also the owner and group owner of that file. The file is
assigned separate read, write, and execute permissions for the owner, the group, and
everyone else. The file owner can be changed only by the <code
class="systemitem">root</code> user, and access permissions can be
changed by both the <code class="systemitem">root</code> user and
file owner.
+ </div><div class="para">
+ Fedora also supports <em class="firstterm">access control
lists</em> (<em class="firstterm">ACLs</em>) for files and
directories which allow permissions for specific users outside of the owner to be set. For
more information about ACLs, refer to the <em class="citetitle">Access
Control Lists</em> chapter of the Fedora <em
class="citetitle">Storage Administration Guide</em>.
+ </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"
id="sect-Managing_Users_and_Groups-User_Accounts">3.1. User Accounts
Tool</h2></div></div></div><a id="id414917"
class="indexterm"></a><a id="id405941"
class="indexterm"></a><a id="id405084"
class="indexterm"></a><div class="para">
+ The <span class="application"><strong>User
Accounts</strong></span> configuration tool allows you to view, modify, add,
and delete local users. To run the utility, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Settings</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu and
click the <span class="guimenu"><strong>User
Accounts</strong></span> icon, or click your name on the panel and choose
<span class="guimenuitem"><strong>My
Account</strong></span> from the drop-down menu.
+ </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="The User Accounts configuration
tool" /><div class="longdesc"><div class="para">
+ The User Accounts configuration tool
+ </div></div></div></div><h6>Figure 3.1. The User
Accounts configuration tool</h6></div><br class="figure-break"
/><div class="para">
+ The main window of the <span class="application"><strong>User
Accounts</strong></span> configuration tool is divided into two parts: The
left side of the window contains a list of available user accounts. The right side
provides details on a particular account.
+ </div><div class="para">
+ By default, the tool only allows you to change certain settings regarding your
account. This is because only <code class="systemitem">root</code>
is allowed to configure users and groups. To unlock the configuration tool for all kinds
of changes, click the <span
class="guibutton"><strong>Unlock</strong></span> button in
the bottom-left corner of the window, and provide the root password when prompted.
+ </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"
id="sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.1.1. Configuring
an Account</h3></div></div></div><div
class="para">
+ To change the image associated with an account, click the icon next to the account
name and either select a picture from the drop-down list, or click <span
class="guimenuitem"><strong>Browse for more
pictures...</strong></span> to use an image from your local drive.
+ </div><div class="para">
+ To change the name associated with an account, click the name next to the icon to
edit it.
+ </div><div class="para">
+ To change the account type, use the <span
class="guimenu"><strong>Account type</strong></span>
drop-down list. However, this change requires the configuration tool to be unlocked even
if it is your account.
+ </div><div class="para">
+ To change the default language for an account, click the button next to the <span
class="guilabel"><strong>Language</strong></span> label,
and select the desired language from the list.
+ </div><div class="para">
+ To change the password, click the button next to the <span
class="guilabel"><strong>Password</strong></span> label. A
dialog box will appear, allowing you to set the new password. Note that the current
password must be provided in order to confirm the change. Once done, click the <span
class="guibutton"><strong>Change</strong></span> button to
save the change.
+ </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="Changing the
password" /><div class="longdesc"><div
class="para">
+ Changing the password
+ </div></div></div></div><h6>Figure 3.2. Changing the
password</h6></div><br class="figure-break" /><div
class="note"><div
class="admonition_header"><h2>Password security
advice</h2></div><div class="admonition"><div
class="para">
+ It is advisable to use a much longer password, as this makes it more difficult for
an intruder to guess it and access the account without permission. It is also recommended
that the password not be based on a dictionary term: use a combination of letters, numbers
and special characters.
+ </div></div></div><div class="para">
+ Finally, to set up automatic login for a particular account, enable the <span
class="guilabel"><strong>Automatic Login</strong></span>
switch. The configuration tool must be unlocked to make this change.
+ </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"
id="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">3.1.2. Adding
a New User</h3></div></div></div><a id="id558633"
class="indexterm"></a><div class="para">
+ To add a new user, make sure the configuration tool is unlocked, and click the
<span class="guibutton"><strong>+</strong></span> button
(that is, the plus sign) below the account list. A dialog box as shown in <a
class="xref"
href="#fig-Managing_Users_and_Groups-User_Accounts-Adding_an_Account">Figure 3.3,
“Creating a new account”</a> will appear.
+ </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="Creating a new account"
/><div class="longdesc"><div class="para">
+ Creating a new account
+ </div></div></div></div><h6>Figure 3.3. Creating a
new account</h6></div><br class="figure-break" /><div
class="para">
+ Take the followign steps to create an account:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Select an account type from the <span
class="guimenu"><strong>Account type</strong></span>
drop-down list. Available account types are <code
class="option">Administrator</code> and <code
class="option">Standard</code> (the default option).
+ </div></li><li class="step"><div
class="para">
+ Fill in the <span class="guilabel"><strong>Full
name</strong></span> input field to set the name associated with the account.
This name will be used by the login manager, and will be displayed on the panel.
+ </div></li><li class="step"><div
class="para">
+ Either select a suggested username from the <span
class="guilabel"><strong>Username</strong></span> drop-down
list, or fill in the corresponding input field.
+ </div></li><li class="step"><div
class="para">
+ Click the <span
class="guibutton"><strong>Create</strong></span> button to
confirm the settings.
+ </div></li></ol></div><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em>
(UPG) scheme. The UPG scheme does not add or change anything in the standard UNIX way of
handling groups; it offers a new convention. Whenever you create a new user, a unique
group with the same name as the user is created.
+ </div><div class="para">
+ When a new account is created, default configuration files are copied from the
<code class="filename">/etc/skel/</code> directory into the new home
directory.
+ </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"
id="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.1.3. Removing
a User</h3></div></div></div><a id="id836770"
class="indexterm"></a><div class="para">
+ To remove a user, make sure the configuration tool is unlocked, select the desired
account from the account list, and click the <span
class="guibutton"><strong>−</strong></span> button (that
is, the minus sign) below the account list. A dialog box as shown in <a
class="xref"
href="#fig-Managing_Users_and_Groups-User_Accounts-Removing_an_Account">Figure 3.4,
“Removing an account”</a> will appear.
+ </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="Removing an account"
/><div class="longdesc"><div class="para">
+ Removing an account
+ </div></div></div></div><h6>Figure 3.4. Removing an
account</h6></div><br class="figure-break" /><div
class="para">
+ To delete files and directories that belong to the user (that is, the home directory,
mail spool, and temporary files), click the <span
class="guibutton"><strong>Delete Files</strong></span>
button. To keep these files intact and only delete the user account, click <span
class="guibutton"><strong>Keep Files</strong></span>. To
abort the deletion, click <span
class="guibutton"><strong>Cancel</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"
id="s1-users-configui">3.2. User Manager
Tool</h2></div></div></div><a id="id410550"
class="indexterm"></a><a id="id410562"
class="indexterm"></a><a id="id410574"
class="indexterm"></a><a id="id410587"
class="indexterm"></a><a id="id461769"
class="indexterm"></a><a id="id461781"
class="indexterm"></a><div class="para">
+ The <span class="application"><strong>User
Manager</strong></span> allows you to view, modify, add, and delete local
users and groups.
+ </div><div class="figure"
id="fig-Users_Groups-User_Manager"><div
class="figure-contents"><div class="mediaobject"><img
src="images/user-manager.png" alt="The GNOME User Manager"
/><div class="longdesc"><div class="para">
+ The GNOME User Manager allows you to manage users
+ </div></div></div></div><h6>Figure 3.5. The GNOME User
Manager</h6></div><br class="figure-break" /><div
class="para">
+ You can start the <span class="application"><strong>User
Manager</strong></span> by clicking <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guimenuitem"><strong>Other</strong></span>
→ <span class="guimenuitem"><strong>Users and
Groups</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu.
Alternatively, you can enter <code
class="command">system-config-users</code> at the shell prompt to open
the <span class="application"><strong>User
Manager</strong></span>. Viewing and modifying user and group information
requires superuser privileges. If you are not the superuser when you open the <span
class="application"><strong>User Manager</strong></span>,
it will prompt you for the superuser password.
+ </div><a id="id1001045"
class="indexterm"></a><a id="id448566"
class="indexterm"></a><div class="para">
+ To view a list of local users on the system, click the <span
class="guilabel"><strong>Users</strong></span> tab. To view
a list of local groups on the system, click the <span
class="guilabel"><strong>Groups</strong></span> tab.
+ </div><div class="para">
+ To find a specific user or group, type the first few letters of the name in the
<span class="guilabel"><strong>Search
filter</strong></span> field. Press <span
class="keycap"><strong>Enter</strong></span> or click the
<span class="guibutton"><strong>Apply
filter</strong></span> button. The filtered list is displayed.
+ </div><div class="para">
+ To sort the users, click on the column User Name and for groups click on Group Name.
The users or groups are sorted according to the value of that column.
+ </div><div class="para">
+ Fedora reserves user IDs below 500 for system users. By default, the <span
class="application"><strong>User Manager</strong></span>
does not display system users. To view all users, including the system users, go to
<span class="guimenu"><strong>Edit</strong></span> →
<span
class="guimenuitem"><strong>Preferences</strong></span> and
uncheck <span class="guilabel"><strong>Hide system users and
groups</strong></span> from the dialog box.
+ </div><div class="section"
id="s2-redhat-config-users-user-new"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-redhat-config-users-user-new">3.2.1. Adding a New
User</h3></div></div></div><a id="id609737"
class="indexterm"></a><div class="para">
+ To add a new user, click the <span
class="guibutton"><strong>Add User</strong></span> button.
A window as shown in <a class="xref"
href="#user-new-fig">Figure 3.6, “Creating a new user”</a> appears.
Type the username and full name for the new user in the appropriate fields. Type the
user's password in the <span
class="guilabel"><strong>Password</strong></span> and
<span class="guilabel"><strong>Confirm
Password</strong></span> fields. The password must be at least six
characters.
+ </div><div class="note"><div
class="admonition_header"><h2>Password security
advice</h2></div><div class="admonition"><div
class="para">
+ It is advisable to use a much longer password, as this makes it more difficult for
an intruder to guess it and access the account without permission. It is also recommended
that the password not be based on a dictionary term: use a combination of letters, numbers
and special characters.
+ </div></div></div><div class="para">
+ Select a login shell from the pulldown list. If you are not sure which shell to
select, accept the default value of <code
class="command">/bin/bash</code>. The default home directory is
<code class="filename">/home/<em
class="replaceable"><code>username</code></em>/</code>.
You can change the home directory that is created for the user, or you can choose not to
create the home directory by unselecting <span
class="guilabel"><strong>Create home
directory</strong></span>.
+ </div><div class="para">
+ If you select to create the home directory, default configuration files are copied
from the <code class="filename">/etc/skel/</code> directory into the
new home directory.
+ </div><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em>
(UPG) scheme. The UPG scheme does not add or change anything in the standard UNIX way of
handling groups; it offers a new convention. Whenever you create a new user, by default, a
unique group with the same name as the user is created. If you do not want to create this
group, unselect <span class="guilabel"><strong>Create a private
group for the user</strong></span>.
+ </div><div class="para">
+ To specify a user ID for the user, select <span
class="guilabel"><strong>Specify user ID
manually</strong></span>. If the option is not selected, the next available
user ID above 500 is assigned to the new user. Because Fedora reserves user IDs below 500
for system users, it is not advisable to manually assign user IDs 1-499.
+ </div><div class="para">
+ Click <span
class="guibutton"><strong>OK</strong></span> to create the
user.
+ </div><div class="figure" id="user-new-fig"><div
class="figure-contents"><div class="mediaobject"><img
src="images/user-manager-add-user.png" alt="Creating a new user"
/><div class="longdesc"><div class="para">
+ Creating a new user with the Create New User dialog
+ </div></div></div></div><h6>Figure 3.6. Creating a
new user</h6></div><br class="figure-break" /><div
class="para">
+ To configure more advanced user properties, such as password expiration, modify the
user's properties after adding the user.
+ </div><h4 id="id842923">Modifying User
Properties</h4><a id="id842927"
class="indexterm"></a><a id="id842939"
class="indexterm"></a><div class="para">
+ To view the properties of an existing user, click on the <span
class="guilabel"><strong>Users</strong></span> tab, select
the user from the user list, and click <span
class="guimenuitem"><strong>Properties</strong></span> from
the menu (or choose <span
class="guimenu"><strong>File</strong></span> → <span
class="guimenuitem"><strong>Properties</strong></span> from
the pulldown menu). A window similar to <a class="xref"
href="#user-properties-fig">Figure 3.7, “User Properties”</a> appears.
+ </div><div class="figure"
id="user-properties-fig"><div class="figure-contents"><div
class="mediaobject"><img src="images/user-manager-edit-user.png"
alt="User Properties" /><div class="longdesc"><div
class="para">
+ Modifying user properties
+ </div></div></div></div><h6>Figure 3.7. User
Properties</h6></div><br class="figure-break" /><div
class="para">
+ The <span class="guilabel"><strong>User
Properties</strong></span> window is divided into multiple tabbed pages:
+ </div><a id="id555995"
class="indexterm"></a><a id="id556007"
class="indexterm"></a><a id="id556019"
class="indexterm"></a><a id="id556031"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>User
Data</strong></span> — Shows the basic user information configured when you
added the user. Use this tab to change the user's full name, password, home directory,
or login shell.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Account
Info</strong></span> — Select <span
class="guilabel"><strong>Enable account
expiration</strong></span> if you want the account to expire on a certain
date. Enter the date in the provided fields. Select <span
class="guilabel"><strong>Local password is
locked</strong></span> to lock the user account and prevent the user from
logging into the system.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Password
Info</strong></span> — Displays the date that the user's password last
changed. To force the user to change passwords after a certain number of days, select
<span class="guilabel"><strong>Enable password
expiration</strong></span> and enter a desired value in the <span
class="guilabel"><strong>Days before change
required:</strong></span> field. The number of days before the user's
password expires, the number of days before the user is warned to change passwords, and
days before the account becomes inactive can also be changed.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Groups</strong></span> — Allows
you to view and configure the Primary Group of the user, as well as other groups that you
want the user to be a member of.
+ </div></li></ul></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"
id="s2-redhat-config-users-group-new">3.2.2. Adding a New
Group</h3></div></div></div><a id="id913116"
class="indexterm"></a><div class="para">
+ To add a new user group, select <span
class="guibutton"><strong>Add Group</strong></span> from
the toolbar. A window similar to <a class="xref"
href="#group-new-fig">Figure 3.8, “New Group”</a> appears. Type the
name of the new group. To specify a group ID for the new group, select <span
class="guilabel"><strong>Specify group ID
manually</strong></span> and select the GID. Note that Fedora also reserves
group IDs lower than 500 for system groups.
+ </div><div class="figure" id="group-new-fig"><div
class="figure-contents"><div class="mediaobject"><img
src="images/user-manager-add-group.png" alt="New Group" /><div
class="longdesc"><div class="para">
+ Creating a new group
+ </div></div></div></div><h6>Figure 3.8. New
Group</h6></div><br class="figure-break" /><div
class="para">
+ Click <span
class="guibutton"><strong>OK</strong></span> to create the
group. The new group appears in the group list.
+ </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"
id="s2-redhat-config-users-group-properties">3.2.3. Modifying Group
Properties</h3></div></div></div><a id="id600702"
class="indexterm"></a><div class="para">
+ To view the properties of an existing group, select the group from the group list and
click <span
class="guimenuitem"><strong>Properties</strong></span> from
the menu (or choose <span
class="guimenu"><strong>File</strong></span> → <span
class="guimenuitem"><strong>Properties</strong></span> from
the pulldown menu). A window similar to <a class="xref"
href="#group-properties-fig">Figure 3.9, “Group Properties”</a>
appears.
+ </div><div class="figure"
id="group-properties-fig"><div
class="figure-contents"><div class="mediaobject"><img
src="images/user-manager-edit-group.png" alt="Group Properties"
/><div class="longdesc"><div class="para">
+ Modifying group properties
+ </div></div></div></div><h6>Figure 3.9. Group
Properties</h6></div><br class="figure-break" /><a
id="id877549" class="indexterm"></a><div
class="para">
+ The <span class="guilabel"><strong>Group
Users</strong></span> tab displays which users are members of the group. Use
this tab to add or remove users from the group. Click <span
class="guibutton"><strong>OK</strong></span> to save your
changes.
+ </div></div></div><div class="section"
id="s1-users-tools"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-tools">3.3. User and Group Management
Tools</h2></div></div></div><a id="id1229842"
class="indexterm"></a><a id="id1229859"
class="indexterm"></a><a id="id1229877"
class="indexterm"></a><a id="id470020"
class="indexterm"></a><div class="para">
+ Managing users and groups can be tiresome; this is why Fedora provides tools and
conventions to make this task easier to manage.
+ </div><div class="para">
+ The easiest way to manage users and groups is through the graphical application,
<span class="application"><strong>User
Manager</strong></span> (<code
class="command">system-config-users</code>). For more information on
<span class="application"><strong>User
Manager</strong></span>, refer to <a class="xref"
href="#s1-users-configui">Section 3.2, “User Manager Tool”</a>.
+ </div><div class="para">
+ The following command line tools can also be used to manage users and groups:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">useradd</code>, <code
class="command">usermod</code>, and <code
class="command">userdel</code> — Industry-standard methods of adding,
deleting and modifying user accounts
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">groupadd</code>, <code
class="command">groupmod</code>, and <code
class="command">groupdel</code> — Industry-standard methods of adding,
deleting, and modifying user groups
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">gpasswd</code> — Industry-standard
method of administering the <code class="filename">/etc/group</code>
file
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pwck</code>, <code
class="command">grpck</code> — Tools used for the verification of the
password, group, and associated shadow files
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pwconv</code>, <code
class="command">pwunconv</code> — Tools used for the conversion of
passwords to shadow passwords and back to standard passwords
+ </div></li></ul></div><div class="section"
id="s2-users-cmd-line"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-users-cmd-line">3.3.1. Command Line
Configuration</h3></div></div></div><a id="id405254"
class="indexterm"></a><a id="id591840"
class="indexterm"></a><a id="id591855"
class="indexterm"></a><div class="para">
+ If you prefer command line tools or do not have the X Window System installed, use
following to configure users and groups.
+ </div><h4 id="id591872">Adding a User</h4><div
class="para">
+ To add a user to the system:
+ </div><a id="id591880"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Issue the <code class="command">useradd</code> command to
create a locked user account:
+ </div><pre class="screen"><code
class="command">useradd</code> <em
class="replaceable"><code>username</code></em></pre></li><li
class="step"><div class="para">
+ <a id="id401272" class="indexterm"></a>
+ Unlock the account by issuing the <code
class="command">passwd</code> command to assign a password and set
password aging guidelines:
+ </div><pre class="screen"><code
class="command">passwd</code> <em
class="replaceable"><code>username</code></em></pre></li></ol></div><div
class="para">
+ Command line options for <code class="command">useradd</code>
are detailed in <a class="xref"
href="#table-useradd-options">Table 3.1, “<code
class="command">useradd</code> Command Line Options”</a>.
+ </div><div class="table"
id="table-useradd-options"><h6>Table 3.1. <code
class="command">useradd</code> Command Line Options</h6><div
class="table-contents"><table summary="useradd Command Line
Options" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-c</code> '<em
class="replaceable"><code>comment</code></em>'
+ </td><td>
+ <em
class="replaceable"><code>comment</code></em> can be
replaced with any string. This option is generally used to specify the full name of a
user.
+ </td></tr><tr><td>
+ <code class="option">-d</code> <em
class="replaceable"><code>home_directory</code></em>
+ </td><td>
+ Home directory to be used instead of default <code
class="filename">/home/<em
class="replaceable"><code>username</code></em>/</code>.
+ </td></tr><tr><td>
+ <code class="option">-e</code> <em
class="replaceable"><code>date</code></em>
+ </td><td>
+ Date for the account to be disabled in the format YYYY-MM-DD.
+ </td></tr><tr><td>
+ <code class="option">-f</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Number of days after the password expires until the account is disabled. If
<code class="literal">0</code> is specified, the account is disabled
immediately after the password expires. If <code
class="literal">-1</code> is specified, the account is not be disabled
after the password expires.
+ </td></tr><tr><td>
+ <code class="option">-g</code> <em
class="replaceable"><code>group_name</code></em>
+ </td><td>
+ Group name or group number for the user's default group. The group must exist
prior to being specified here.
+ </td></tr><tr><td>
+ <code class="option">-G</code> <em
class="replaceable"><code>group_list</code></em>
+ </td><td>
+ List of additional (other than default) group names or group numbers, separated
by commas, of which the user is a member. The groups must exist prior to being specified
here.
+ </td></tr><tr><td>
+ <code class="option">-m</code>
+ </td><td>
+ Create the home directory if it does not exist.
+ </td></tr><tr><td>
+ <code class="option">-M</code>
+ </td><td>
+ Do not create the home directory.
+ </td></tr><tr><td>
+ <code class="option">-N</code>
+ </td><td>
+ Do not create a user private group for the user.
+ </td></tr><tr><td>
+ <code class="option">-p</code> <em
class="replaceable"><code>password</code></em>
+ </td><td>
+ The password encrypted with <code
class="command">crypt</code>.
+ </td></tr><tr><td>
+ <code class="option">-r</code>
+ </td><td>
+ Create a system account with a UID less than 500 and without a home directory.
+ </td></tr><tr><td>
+ <code class="option">-s</code>
+ </td><td>
+ User's login shell, which defaults to <code
class="command">/bin/bash</code>.
+ </td></tr><tr><td>
+ <code class="option">-u</code> <em
class="replaceable"><code>uid</code></em>
+ </td><td>
+ User ID for the user, which must be unique and greater than 499.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><h4 id="id418175">Adding a
Group</h4><a id="id1279057"
class="indexterm"></a><a id="id1279070"
class="indexterm"></a><div class="para">
+ To add a group to the system, use the command <code
class="command">groupadd</code>:
+ </div><pre class="screen"><code
class="command">groupadd</code> <em
class="replaceable"><code>group_name</code></em></pre><div
class="para">
+ Command line options for <code class="command">groupadd</code>
are detailed in <a class="xref"
href="#table-groupadd-options">Table 3.2, “<code
class="command">groupadd</code> Command Line Options”</a>.
+ </div><div class="table"
id="table-groupadd-options"><h6>Table 3.2. <code
class="command">groupadd</code> Command Line Options</h6><div
class="table-contents"><table summary="groupadd Command Line
Options" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-f</code>, <code
class="option">--force</code>
+ </td><td>
+ When used with <code class="option">-g</code> <em
class="replaceable"><code>gid</code></em> and <em
class="replaceable"><code>gid</code></em> already exists,
<code class="command">groupadd</code> will choose another unique
<em class="replaceable"><code>gid</code></em> for the
group.
+ </td></tr><tr><td>
+ <code class="option">-g</code> <em
class="replaceable"><code>gid</code></em>
+ </td><td>
+ Group ID for the group, which must be unique and greater than 499.
+ </td></tr><tr><td>
+ <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>
+ Override <code class="filename">/etc/login.defs</code>
defaults.
+ </td></tr><tr><td>
+ <code class="option">-o</code>, <code
class="option">--non-unique</code>
+ </td><td>
+ Allow to create groups with duplicate.
+ </td></tr><tr><td>
+ <code class="option">-p</code>, <code
class="option">--password</code> <em
class="replaceable"><code>password</code></em>
+ </td><td>
+ Use this encrypted password for the new group.
+ </td></tr><tr><td>
+ <code class="option">-r</code>
+ </td><td>
+ Create a system group with a GID less than 500.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><h4 id="id529374">Password
Aging</h4><a id="id529378"
class="indexterm"></a><a id="id529390"
class="indexterm"></a><a id="id529402"
class="indexterm"></a><a id="id529409"
class="indexterm"></a><a id="id1278370"
class="indexterm"></a><div class="para">
+ For security reasons, it is advisable to require users to change their passwords
periodically. This can be done when adding or editing a user on the <span
class="guilabel"><strong>Password Info</strong></span> tab
of the <span class="application"><strong>User
Manager</strong></span>.
+ </div><div class="para">
+ To configure password expiration for a user from a shell prompt, use the <code
class="command">chage</code> command with an option from <a
class="xref" href="#table-chage-options">Table 3.3, “<code
class="command">chage</code> Command Line Options”</a>, followed
by the username.
+ </div><div class="important"><div
class="admonition_header"><h2>Shadow passwords must be enabled to use
chage</h2></div><div class="admonition"><div
class="para">
+ Shadow passwords must be enabled to use the <code
class="command">chage</code> command. For more information, see <a
class="xref" href="#s1-users-groups-shadow-utilities">Section 3.7,
“Shadow Passwords”</a>.
+ </div></div></div><div class="table"
id="table-chage-options"><h6>Table 3.3. <code
class="command">chage</code> Command Line Options</h6><div
class="table-contents"><table summary="chage Command Line
Options" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-d</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specifies the number of days since January 1, 1970 the password was changed.
+ </td></tr><tr><td>
+ <code class="option">-E</code> <em
class="replaceable"><code>date</code></em>
+ </td><td>
+ Specifies the date on which the account is locked, in the format YYYY-MM-DD.
Instead of the date, the number of days since January 1, 1970 can also be used.
+ </td></tr><tr><td>
+ <code class="option">-I</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specifies the number of inactive days after the password expiration before
locking the account. If the value is <code class="literal">0</code>,
the account is not locked after the password expires.
+ </td></tr><tr><td>
+ <code class="option">-l</code>
+ </td><td>
+ Lists current account aging settings.
+ </td></tr><tr><td>
+ <code class="option">-m</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specify the minimum number of days after which the user must change passwords. If
the value is <code class="literal">0</code>, the password does not
expire.
+ </td></tr><tr><td>
+ <code class="option">-M</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specify the maximum number of days for which the password is valid. When the
number of days specified by this option plus the number of days specified with the
<code class="option">-d</code> option is less than the current day,
the user must change passwords before using the account.
+ </td></tr><tr><td>
+ <code class="option">-W</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specifies the number of days before the password expiration date to warn the
user.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="note"><div
class="admonition_header"><h2>chage
interactivity</h2></div><div class="admonition"><div
class="para">
+ If the <code class="command">chage</code> command is followed
directly by a username (with no options), it displays the current password aging values
and allows them to be changed interactively.
+ </div></div></div><div class="para">
+ You can configure a password to expire the first time a user logs in. This forces
users to change passwords immediately.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ <span class="emphasis"><em>Set up an initial
password</em></span> — There are two common approaches to this step: the
administrator can assign a default password, or he can use a null password.
+ </div><div class="para">
+ To assign a default password, type the following at a shell prompt:
+ </div><pre class="screen"><code
class="command">passwd</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ To assign a null password instead, use the following command:
+ </div><pre class="screen"><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>Avoid using null passwords whenever
possible</h2></div><div class="admonition"><div
class="para">
+ Using a null password, while convenient, is a highly insecure practice, as any
third party can log in first and access the system using the insecure username. Always
make sure that the user is ready to log in before unlocking an account with a null
password.
+ </div></div></div></li><li
class="step"><div class="para">
+ <span class="emphasis"><em>Force immediate password
expiration</em></span> — Type the following command:
+ </div><pre class="screen"><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">
+ This command sets the value for the date the password was last changed to the epoch
(January 1, 1970). This value forces immediate password expiration no matter what password
aging policy, if any, is in place.
+ </div></li></ol></div><div class="para">
+ Upon the initial log in, the user is now prompted for a new password.
+ </div></div><div class="section"
id="s2-redhat-config-users-process"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-redhat-config-users-process">3.3.2. Explaining the
Process</h3></div></div></div><div class="para">
+ The following steps illustrate what happens if the command <code
class="command">useradd juan</code> is issued on a system that has
shadow passwords enabled:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ A new line for <code class="systemitem">juan</code> is
created in <code class="filename">/etc/passwd</code>:
+ </div><pre
class="screen">juan:x:501:501::/home/juan:/bin/bash</pre><div
class="para">
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the username <code
class="literal">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ There is an <code class="literal">x</code> for the password
field indicating that the system is using shadow passwords.
+ </div></li><li class="listitem"><div
class="para">
+ A UID greater than 499 is created. Under Fedora, UIDs and GIDs below 500 are
reserved for system use. These should not be assigned to users.
+ </div></li><li class="listitem"><div
class="para">
+ A GID greater than 499 is created.
+ </div></li><li class="listitem"><div
class="para">
+ The optional GECOS information is left blank.
+ </div></li><li class="listitem"><div
class="para">
+ The home directory for <code class="systemitem">juan</code>
is set to <code class="filename">/home/juan/</code>.
+ </div></li><li class="listitem"><div
class="para">
+ The default shell is set to <code
class="command">/bin/bash</code>.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ A new line for <code class="systemitem">juan</code> is
created in <code class="filename">/etc/shadow</code>:
+ </div><pre
class="screen">juan:!!:14798:0:99999:7:::</pre><div
class="para">
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the username <code
class="systemitem">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ Two exclamation marks (<code class="literal">!!</code>)
appear in the password field of the <code
class="filename">/etc/shadow</code> file, which locks the account.
+ </div><div class="note"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ If an encrypted password is passed using the <code
class="option">-p</code> flag, it is placed in the <code
class="filename">/etc/shadow</code> file on the new line for the user.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ The password is set to never expire.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ A new line for a group named <code
class="systemitem">juan</code> is created in <code
class="filename">/etc/group</code>:
+ </div><pre class="screen">juan:x:501:</pre><div
class="para">
+ A group with the same name as a user is called a <em
class="firstterm">user private group</em>. For more information on user
private groups, refer to <a class="xref"
href="#s2-redhat-config-users-user-new">Section 3.2.1, “Adding a New
User”</a>.
+ </div><div class="para">
+ The line created in <code class="filename">/etc/group</code>
has the following characteristics:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the group name <code
class="systemitem">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ An <code class="literal">x</code> appears in the password
field indicating that the system is using shadow group passwords.
+ </div></li><li class="listitem"><div
class="para">
+ The GID matches the one listed for user <code
class="systemitem">juan</code> in <code
class="filename">/etc/passwd</code>.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ A new line for a group named <code
class="systemitem">juan</code> is created in <code
class="filename">/etc/gshadow</code>:
+ </div><pre class="screen">juan:!::</pre><div
class="para">
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the group name <code
class="systemitem">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ An exclamation mark (<code class="literal">!</code>)
appears in the password field of the <code
class="filename">/etc/gshadow</code> file, which locks the group.
+ </div></li><li class="listitem"><div
class="para">
+ All other fields are blank.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ A directory for user <code class="systemitem">juan</code> is
created in the <code class="filename">/home/</code> directory:
+ </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">
+ This directory is owned by user <code
class="systemitem">juan</code> and group <code
class="systemitem">juan</code>. It has <em
class="firstterm">read</em>, <em
class="firstterm">write</em>, and <em
class="firstterm">execute</em> privileges <span
class="emphasis"><em>only</em></span> for the user <code
class="systemitem">juan</code>. All other permissions are denied.
+ </div></li><li class="step"><div
class="para">
+ The files within the <code class="filename">/etc/skel/</code>
directory (which contain default user settings) are copied into the new <code
class="filename">/home/juan/</code> directory:
+ </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">
+ At this point, a locked account called <code
class="systemitem">juan</code> exists on the system. To activate it,
the administrator must next assign a password to the account using the <code
class="command">passwd</code> command and, optionally, set password
aging guidelines.
+ </div></div></div><div class="section"
id="s1-users-groups-standard-users"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-standard-users">3.4. Standard
Users</h2></div></div></div><a id="id674557"
class="indexterm"></a><a id="id674569"
class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-users-groups-group-use">Table 3.4,
“Standard Users”</a> lists the standard users configured in the <code
class="filename">/etc/passwd</code> file by an <span
class="guilabel"><strong>Everything</strong></span>
installation. The group ID (GID) in this table is the <span
class="emphasis"><em>primary group</em></span> for the
user. See <a class="xref"
href="#s1-users-groups-standard-groups">Section 3.5, “Standard
Groups”</a> for a listing of standard groups.
+ </div><div class="table"
id="tb-users-groups-group-use"><h6>Table 3.4. Standard
Users</h6><div class="table-contents"><table
summary="Standard Users" border="1"><colgroup><col
class="col1" width="17%" /><col class="col2"
width="17%" /><col class="col3" width="17%"
/><col class="col4" width="17%" /><col
class="col5" width="17%" /><col class="col6"
width="17%" /></colgroup><thead><tr><th>
+ User
+ </th><th>
+ UID
+ </th><th>
+ GID
+ </th><th>
+ Home Directory
+ </th><th>
+ Shell
+ </th><th>
+ Packages
+ </th></tr></thead><tbody><tr><td>
+ <code class="systemitem">root</code>
+ </td><td>
+ 0
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/root</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">bin</code>
+ </td><td>
+ 1
+ </td><td>
+ 1
+ </td><td>
+ <code class="filename">/bin</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">daemon</code>
+ </td><td>
+ 2
+ </td><td>
+ 2
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">sys</code>
+ </td><td>
+ —
+ </td><td>
+ 3
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">adm</code>
+ </td><td>
+ 3
+ </td><td>
+ 4
+ </td><td>
+ <code class="filename">/var/adm</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">tty</code>
+ </td><td>
+ —
+ </td><td>
+ 5
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">disk</code>
+ </td><td>
+ —
+ </td><td>
+ 6
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">lp</code>
+ </td><td>
+ 4
+ </td><td>
+ 7
+ </td><td>
+ <code class="filename">/var/spool/lpd</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mem</code>
+ </td><td>
+ —
+ </td><td>
+ 8
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">kmem</code>
+ </td><td>
+ —
+ </td><td>
+ 9
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">wheel</code>
+ </td><td>
+ —
+ </td><td>
+ 10
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">cdrom</code>
+ </td><td>
+ —
+ </td><td>
+ 11
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">udev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">sync</code>
+ </td><td>
+ 5
+ </td><td>
+ (0)
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/bin/sync</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">shutdown</code>
+ </td><td>
+ 6
+ </td><td>
+ (0)
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/shutdown</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">halt</code>
+ </td><td>
+ 7
+ </td><td>
+ (0)
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/halt</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mail</code>
+ </td><td>
+ 8
+ </td><td>
+ 12
+ </td><td>
+ <code class="filename">/var/spool/mail</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">news</code>
+ </td><td>
+ 9
+ </td><td>
+ 13
+ </td><td>
+ <code class="filename">/var/spool/news</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">uucp</code>
+ </td><td>
+ 10
+ </td><td>
+ 14
+ </td><td>
+ <code class="filename">/var/spool/uucp</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">operator</code>
+ </td><td>
+ 11
+ </td><td>
+ (0)
+ </td><td>
+ <code class="filename">/root</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">games</code>
+ </td><td>
+ 12
+ </td><td>
+ (100)
+ </td><td>
+ <code class="filename">/usr/games</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">gopher</code>
+ </td><td>
+ 13
+ </td><td>
+ 30
+ </td><td>
+ <code class="filename">/usr/lib/gopher-data</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ftp</code>
+ </td><td>
+ 14
+ </td><td>
+ 50
+ </td><td>
+ <code class="filename">/var/ftp</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">man</code>
+ </td><td>
+ —
+ </td><td>
+ 15
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">oprofile</code>
+ </td><td>
+ 16
+ </td><td>
+ 16
+ </td><td>
+ <code class="filename">/home/oprofile</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">oprofile</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pkiuser</code>
+ </td><td>
+ 17
+ </td><td>
+ 17
+ </td><td>
+ <code class="filename">/usr/share/pki</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">pki-ca</span>, <span
class="package">rhpki-ca</span>
+ </td></tr><tr><td>
+ <code class="systemitem">dialout</code>
+ </td><td>
+ —
+ </td><td>
+ 18
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">udev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">floppy</code>
+ </td><td>
+ —
+ </td><td>
+ 19
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">dev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">games</code>
+ </td><td>
+ —
+ </td><td>
+ 20
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">slocate</code>
+ </td><td>
+ —
+ </td><td>
+ 21
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">slocate</span>
+ </td></tr><tr><td>
+ <code class="systemitem">utmp</code>
+ </td><td>
+ —
+ </td><td>
+ 22
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">initscripts</span>, <span
class="package">libutempter</span>
+ </td></tr><tr><td>
+ <code class="systemitem">squid</code>
+ </td><td>
+ 23
+ </td><td>
+ 23
+ </td><td>
+ <code class="filename">/var/spool/squid</code>
+ </td><td>
+ <code class="filename">/dev/null</code>
+ </td><td>
+ <span class="package">squid</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pvm</code>
+ </td><td>
+ 24
+ </td><td>
+ 24
+ </td><td>
+ <code class="filename">/usr/share/pvm3</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">pvm</span>
+ </td></tr><tr><td>
+ <code class="systemitem">named</code>
+ </td><td>
+ 25
+ </td><td>
+ 25
+ </td><td>
+ <code class="filename">/var/named</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">bind</span>
+ </td></tr><tr><td>
+ <code class="systemitem">postgres</code>
+ </td><td>
+ 26
+ </td><td>
+ 26
+ </td><td>
+ <code class="filename">/var/lib/pgsql</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">postgresql-server</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mysql</code>
+ </td><td>
+ 27
+ </td><td>
+ 27
+ </td><td>
+ <code class="filename">/var/lib/mysql</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">mysql</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nscd</code>
+ </td><td>
+ 28
+ </td><td>
+ 28
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">nscd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">rpcuser</code>
+ </td><td>
+ 29
+ </td><td>
+ 29
+ </td><td>
+ <code class="filename">/var/lib/nfs</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">nfs-utils</span>
+ </td></tr><tr><td>
+ <code class="systemitem">console</code>
+ </td><td>
+ —
+ </td><td>
+ 31
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">dev</span>
+ </td></tr><tr><td>
+ <code class="systemitem">rpc</code>
+ </td><td>
+ 32
+ </td><td>
+ 32
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">portmap</span>
+ </td></tr><tr><td>
+ <code class="systemitem">amanda</code>
+ </td><td>
+ 33
+ </td><td>
+ (6)
+ </td><td>
+ <code class="filename">/var/lib/amanda</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">amanda</span>
+ </td></tr><tr><td>
+ <code class="systemitem">tape</code>
+ </td><td>
+ —
+ </td><td>
+ 33
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">udev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">netdump</code>
+ </td><td>
+ 34
+ </td><td>
+ 34
+ </td><td>
+ <code class="filename">/var/crash</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">netdump-client</span>, <span
class="package">netdump-server</span>
+ </td></tr><tr><td>
+ <code class="systemitem">utempter</code>
+ </td><td>
+ —
+ </td><td>
+ 35
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">libutempter</span>
+ </td></tr><tr><td>
+ <code class="systemitem">vdsm</code>
+ </td><td>
+ 36
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">kvm</span>, <span
class="package">vdsm</span>
+ </td></tr><tr><td>
+ <code class="systemitem">kvm</code>
+ </td><td>
+ —
+ </td><td>
+ 36
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">kvm</span>, <span
class="package">vdsm</span>, <span
class="package">libvirt</span>
+ </td></tr><tr><td>
+ <code class="systemitem">rpm</code>
+ </td><td>
+ 37
+ </td><td>
+ 37
+ </td><td>
+ <code class="filename">/var/lib/rpm</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">rpm</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ntp</code>
+ </td><td>
+ 38
+ </td><td>
+ 38
+ </td><td>
+ <code class="filename">/etc/ntp</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">ntp</span>
+ </td></tr><tr><td>
+ <code class="systemitem">video</code>
+ </td><td>
+ —
+ </td><td>
+ 39
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">dip</code>
+ </td><td>
+ —
+ </td><td>
+ 40
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mailman</code>
+ </td><td>
+ 41
+ </td><td>
+ 41
+ </td><td>
+ <code class="filename">/var/mailman</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">mailman</span>
+ </td></tr><tr><td>
+ <code class="systemitem">gdm</code>
+ </td><td>
+ 42
+ </td><td>
+ 42
+ </td><td>
+ <code class="filename">/var/gdm</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">gdm</span>
+ </td></tr><tr><td>
+ <code class="systemitem">xfs</code>
+ </td><td>
+ 43
+ </td><td>
+ 43
+ </td><td>
+ <code class="filename">/etc/X11/fs</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">XFree86-xfs</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pppusers</code>
+ </td><td>
+ —
+ </td><td>
+ 44
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">linuxconf</span>
+ </td></tr><tr><td>
+ <code class="systemitem">popusers</code>
+ </td><td>
+ —
+ </td><td>
+ 45
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">linuxconf</span>
+ </td></tr><tr><td>
+ <code class="systemitem">slipusers</code>
+ </td><td>
+ —
+ </td><td>
+ 46
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">linuxconf</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mailnull</code>
+ </td><td>
+ 47
+ </td><td>
+ 47
+ </td><td>
+ <code class="filename">/var/spool/mqueue</code>
+ </td><td>
+ <code class="filename">/dev/null</code>
+ </td><td>
+ <span class="package">sendmail</span>
+ </td></tr><tr><td>
+ <code class="systemitem">apache</code>
+ </td><td>
+ 48
+ </td><td>
+ 48
+ </td><td>
+ <code class="filename">/var/www</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">apache</span>
+ </td></tr><tr><td>
+ <code class="systemitem">wnn</code>
+ </td><td>
+ 49
+ </td><td>
+ 49
+ </td><td>
+ <code class="filename">/home/wnn</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">FreeWnn</span>
+ </td></tr><tr><td>
+ <code class="systemitem">smmsp</code>
+ </td><td>
+ 51
+ </td><td>
+ 51
+ </td><td>
+ <code class="filename">/var/spool/mqueue</code>
+ </td><td>
+ <code class="filename">/dev/null</code>
+ </td><td>
+ <span class="package">sendmail</span>
+ </td></tr><tr><td>
+ <code class="systemitem">puppet</code>
+ </td><td>
+ 52
+ </td><td>
+ 52
+ </td><td>
+ <code class="filename">/var/lib/puppet</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">puppet</span>
+ </td></tr><tr><td>
+ <code class="systemitem">tomcat</code>
+ </td><td>
+ 53
+ </td><td>
+ 53
+ </td><td>
+ <code class="filename">/var/lib/tomcat</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">tomcat</span>
+ </td></tr><tr><td>
+ <code class="systemitem">lock</code>
+ </td><td>
+ —
+ </td><td>
+ 54
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">lockdev</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ldap</code>
+ </td><td>
+ 55
+ </td><td>
+ 55
+ </td><td>
+ <code class="filename">/var/lib/ldap</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">openldap-servers</span>
+ </td></tr><tr><td>
+ <code class="systemitem">frontpage</code>
+ </td><td>
+ 56
+ </td><td>
+ 56
+ </td><td>
+ <code class="filename">/var/www</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">mod_frontpage</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nut</code>
+ </td><td>
+ 57
+ </td><td>
+ 57
+ </td><td>
+ <code class="filename">/var/lib/ups</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">nut</span>
+ </td></tr><tr><td>
+ <code class="systemitem">beagleindex</code>
+ </td><td>
+ 58
+ </td><td>
+ 58
+ </td><td>
+ <code class="filename">/var/cache/beagle</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">beagle</span>
+ </td></tr><tr><td>
+ <code class="systemitem">tss</code>
+ </td><td>
+ 59
+ </td><td>
+ 59
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">trousers</span>
+ </td></tr><tr><td>
+ <code class="systemitem">piranha</code>
+ </td><td>
+ 60
+ </td><td>
+ 60
+ </td><td>
+ <code class="filename">/etc/sysconfig/ha</code>
+ </td><td>
+ <code class="filename">/dev/null</code>
+ </td><td>
+ <span class="package">piranha</span>
+ </td></tr><tr><td>
+ <code class="systemitem">prelude-manager</code>
+ </td><td>
+ 61
+ </td><td>
+ 61
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">prelude-manager</span>
+ </td></tr><tr><td>
+ <code class="systemitem">snortd</code>
+ </td><td>
+ 62
+ </td><td>
+ 62
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">snortd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">audio</code>
+ </td><td>
+ —
+ </td><td>
+ 63
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">condor</code>
+ </td><td>
+ 64
+ </td><td>
+ 64
+ </td><td>
+ <code class="filename">/var/lib/condor</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">condord</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nslcd</code>
+ </td><td>
+ 65
+ </td><td>
+ (55)
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">nslcd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">wine</code>
+ </td><td>
+ —
+ </td><td>
+ 66
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">wine</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pegasus</code>
+ </td><td>
+ 66
+ </td><td>
+ 65
+ </td><td>
+ <code class="filename">/var/lib/Pegasus</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">tog-pegasus</span>
+ </td></tr><tr><td>
+ <code class="systemitem">webalizer</code>
+ </td><td>
+ 67
+ </td><td>
+ 67
+ </td><td>
+ <code class="filename">/var/www/html/usage</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">webalizer</span>
+ </td></tr><tr><td>
+ <code class="systemitem">haldaemon</code>
+ </td><td>
+ 68
+ </td><td>
+ 68
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">hal</span>
+ </td></tr><tr><td>
+ <code class="systemitem">vcsa</code>
+ </td><td>
+ 69
+ </td><td>
+ 69
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">dev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">avahi</code>
+ </td><td>
+ 70
+ </td><td>
+ 70
+ </td><td>
+ <code class="filename">/var/run/avahi-daemon</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">avahi</span>
+ </td></tr><tr><td>
+ <code class="systemitem">realtime</code>
+ </td><td>
+ —
+ </td><td>
+ 71
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">tcpdump</code>
+ </td><td>
+ 72
+ </td><td>
+ 72
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">tcpdump</span>
+ </td></tr><tr><td>
+ <code class="systemitem">privoxy</code>
+ </td><td>
+ 73
+ </td><td>
+ 73
+ </td><td>
+ <code class="filename">/etc/privoxy</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">privoxy</span>
+ </td></tr><tr><td>
+ <code class="systemitem">sshd</code>
+ </td><td>
+ 74
+ </td><td>
+ 74
+ </td><td>
+ <code class="filename">/var/empty/sshd</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">openssh-server</span>
+ </td></tr><tr><td>
+ <code class="systemitem">radvd</code>
+ </td><td>
+ 75
+ </td><td>
+ 75
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">radvd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">cyrus</code>
+ </td><td>
+ 76
+ </td><td>
+ (12)
+ </td><td>
+ <code class="filename">/var/imap</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">cyrus-imapd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">saslauth</code>
+ </td><td>
+ —
+ </td><td>
+ 76
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">cyrus-imapd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">arpwatch</code>
+ </td><td>
+ 77
+ </td><td>
+ 77
+ </td><td>
+ <code class="filename">/var/lib/arpwatch</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">arpwatch</span>
+ </td></tr><tr><td>
+ <code class="systemitem">fax</code>
+ </td><td>
+ 78
+ </td><td>
+ 78
+ </td><td>
+ <code class="filename">/var/spool/fax</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">mgetty</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nocpulse</code>
+ </td><td>
+ 79
+ </td><td>
+ 79
+ </td><td>
+ <code class="filename">/etc/sysconfig/nocpulse</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">nocpulse</span>
+ </td></tr><tr><td>
+ <code class="systemitem">desktop</code>
+ </td><td>
+ 80
+ </td><td>
+ 80
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">desktop-file-utils</span>
+ </td></tr><tr><td>
+ <code class="systemitem">dbus</code>
+ </td><td>
+ 81
+ </td><td>
+ 81
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">dbus</span>
+ </td></tr><tr><td>
+ <code class="systemitem">jonas</code>
+ </td><td>
+ 82
+ </td><td>
+ 82
+ </td><td>
+ <code class="filename">/var/lib/jonas</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">jonas</span>
+ </td></tr><tr><td>
+ <code class="systemitem">clamav</code>
+ </td><td>
+ 83
+ </td><td>
+ 83
+ </td><td>
+ <code class="filename">/tmp</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">clamav</span>
+ </td></tr><tr><td>
+ <code class="systemitem">screen</code>
+ </td><td>
+ —
+ </td><td>
+ 84
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">screen</span>
+ </td></tr><tr><td>
+ <code class="systemitem">quaggavt</code>
+ </td><td>
+ —
+ </td><td>
+ 85
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">quagga</span>
+ </td></tr><tr><td>
+ <code class="systemitem">sabayon</code>
+ </td><td>
+ 86
+ </td><td>
+ 86
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">sabayon</span>
+ </td></tr><tr><td>
+ <code class="systemitem">polkituser</code>
+ </td><td>
+ 87
+ </td><td>
+ 87
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">PolicyKit</span>
+ </td></tr><tr><td>
+ <code class="systemitem">wbpriv</code>
+ </td><td>
+ —
+ </td><td>
+ 88
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">samba-common</span>
+ </td></tr><tr><td>
+ <code class="systemitem">postfix</code>
+ </td><td>
+ 89
+ </td><td>
+ 89
+ </td><td>
+ <code class="filename">/var/spool/postfix</code>
+ </td><td>
+ <code class="filename">/bin/true</code>
+ </td><td>
+ <span class="package">postfix</span>
+ </td></tr><tr><td>
+ <code class="systemitem">postdrop</code>
+ </td><td>
+ —
+ </td><td>
+ 90
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">postfix</span>
+ </td></tr><tr><td>
+ <code class="systemitem">majordomo</code>
+ </td><td>
+ 91
+ </td><td>
+ 91
+ </td><td>
+ <code class="filename">/usr/lib/majordomo</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">majordomo</span>
+ </td></tr><tr><td>
+ <code class="systemitem">quagga</code>
+ </td><td>
+ 92
+ </td><td>
+ 92
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">quagga</span>
+ </td></tr><tr><td>
+ <code class="systemitem">exim</code>
+ </td><td>
+ 93
+ </td><td>
+ 93
+ </td><td>
+ <code class="filename">/var/spool/exim</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">exim</span>
+ </td></tr><tr><td>
+ <code class="systemitem">distcache</code>
+ </td><td>
+ 94
+ </td><td>
+ 94
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">distcache</span>
+ </td></tr><tr><td>
+ <code class="systemitem">radiusd</code>
+ </td><td>
+ 95
+ </td><td>
+ 95
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">freeradius</span>
+ </td></tr><tr><td>
+ <code class="systemitem">hsqldb</code>
+ </td><td>
+ 96
+ </td><td>
+ 96
+ </td><td>
+ <code class="filename">/var/lib/hsqldb</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">hsqldb</span>
+ </td></tr><tr><td>
+ <code class="systemitem">dovecot</code>
+ </td><td>
+ 97
+ </td><td>
+ 97
+ </td><td>
+ <code class="filename">/usr/libexec/dovecot</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">dovecot</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ident</code>
+ </td><td>
+ 98
+ </td><td>
+ 98
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">ident</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nobody</code>
+ </td><td>
+ 99
+ </td><td>
+ 99
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">users</code>
+ </td><td>
+ —
+ </td><td>
+ 100
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">qemu</code>
+ </td><td>
+ 107
+ </td><td>
+ 107
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">libvirt</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ovirt</code>
+ </td><td>
+ 108
+ </td><td>
+ 108
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">libvirt</span>
+ </td></tr><tr><td>
+ <code class="systemitem">saned</code>
+ </td><td>
+ 111
+ </td><td>
+ 111
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">sane-backends</span>
+ </td></tr><tr><td>
+ <code class="systemitem">vhostmd</code>
+ </td><td>
+ 112
+ </td><td>
+ 112
+ </td><td>
+ <code class="filename">/usr/share/vhostmd</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">vhostmd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">usbmuxd</code>
+ </td><td>
+ 113
+ </td><td>
+ 113
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">usbmuxd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">bacula</code>
+ </td><td>
+ 133
+ </td><td>
+ 133
+ </td><td>
+ <code class="filename">/var/spool/bacula</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">bacula</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ricci</code>
+ </td><td>
+ 140
+ </td><td>
+ 140
+ </td><td>
+ <code class="filename">/var/lib/ricci</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">ricci</span>
+ </td></tr><tr><td>
+ <code class="systemitem">luci</code>
+ </td><td>
+ 141
+ </td><td>
+ 141
+ </td><td>
+ <code class="filename">/var/lib/luci</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">luci</span>
+ </td></tr><tr><td>
+ <code class="systemitem">stap-server</code>
+ </td><td>
+ 155
+ </td><td>
+ 155
+ </td><td>
+ <code class="filename">/var/lib/stap-server</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">systemtap</span>
+ </td></tr><tr><td>
+ <code class="systemitem">avahi-autoipd</code>
+ </td><td>
+ 170
+ </td><td>
+ 170
+ </td><td>
+ <code class="filename">/var/lib/avahi-autoipd</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">avahi</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pulse</code>
+ </td><td>
+ 171
+ </td><td>
+ 171
+ </td><td>
+ <code class="filename">/var/run/pulse</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">pulseaudio</span>
+ </td></tr><tr><td>
+ <code class="systemitem">rtkit</code>
+ </td><td>
+ 172
+ </td><td>
+ 172
+ </td><td>
+ <code class="filename">/proc</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">rtkit</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nfsnobody</code>
+ </td><td>
+ 65534<sup>[<a id="id532272" href="#ftn.id532272"
class="footnote">a</a>]</sup>
+ </td><td>
+ 65534
+ </td><td>
+ <code class="filename">/var/lib/nfs</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">nfs-utils</span>
+ </td></tr></tbody><tbody
class="footnotes"><tr><td colspan="6"><div
class="footnote"><div class="para"><sup>[<a
id="ftn.id532272" href="#id532272"
class="para">a</a>] </sup>
+ nfsnobdy is 4294967294 on 64-bit platforms
+ </div></div></td></tr></tbody></table></div></div><br
class="table-break" /></div><div class="section"
id="s1-users-groups-standard-groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-standard-groups">3.5. Standard
Groups</h2></div></div></div><a id="id777163"
class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-users-groups-group-etc">Table 3.5,
“Standard Groups”</a> lists the standard groups configured by an <span
class="guilabel"><strong>Everything</strong></span>
installation. Groups are stored in the <code
class="filename">/etc/group</code> file.
+ </div><div class="table"
id="tb-users-groups-group-etc"><h6>Table 3.5. Standard
Groups</h6><div class="table-contents"><table
summary="Standard Groups" border="1"><colgroup><col
class="group" width="33%" /><col class="gid"
width="33%" /><col class="members" width="33%"
/></colgroup><thead><tr><th>
+ Group
+ </th><th>
+ GID
+ </th><th>
+ Members
+ </th></tr></thead><tbody><tr><td>
+ <code class="systemitem">root</code>
+ </td><td>
+ 0
+ </td><td>
+ <code class="systemitem">root</code>
+ </td></tr><tr><td>
+ <code class="systemitem">bin</code>
+ </td><td>
+ 1
+ </td><td>
+ <code class="systemitem">root</code>, <code
class="systemitem">bin</code>, <code
class="systemitem">daemon</code>
+ </td></tr><tr><td>
+ <code class="systemitem">daemon</code>
+ </td><td>
+ 2
+ </td><td>
+ <code class="systemitem">root</code>, <code
class="systemitem">bin</code>, <code
class="systemitem">daemon</code>
+ </td></tr><tr><td>
+ <code class="systemitem">sys</code>
+ </td><td>
+ 3
+ </td><td>
+ <code class="systemitem">root</code>, <code
class="systemitem">bin</code>, <code
class="systemitem">adm</code>
+ </td></tr><tr><td>
+ <code class="systemitem">adm</code>
+ </td><td>
+ 4
+ </td><td>
+ <code class="systemitem">root</code>, <code
class="systemitem">adm</code>, <code
class="systemitem">daemon</code>
+ </td></tr><tr><td>
+ <code class="systemitem">tty</code>
+ </td><td>
+ 5
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">disk</code>
+ </td><td>
+ 6
+ </td><td>
+ <code class="systemitem">root</code>
+ </td></tr><tr><td>
+ <code class="systemitem">lp</code>
+ </td><td>
+ 7
+ </td><td>
+ <code class="systemitem">daemon</code>, <code
class="systemitem">lp</code>
+ </td></tr><tr><td>
+ <code class="systemitem">mem</code>
+ </td><td>
+ 8
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">kmem</code>
+ </td><td>
+ 9
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">wheel</code>
+ </td><td>
+ 10
+ </td><td>
+ <code class="systemitem">root</code>
+ </td></tr><tr><td>
+ <code class="systemitem">mail</code>
+ </td><td>
+ 12
+ </td><td>
+ <code class="systemitem">mail</code>, <code
class="systemitem">postfix</code>
+ </td></tr><tr><td>
+ <code class="systemitem">uucp</code>
+ </td><td>
+ 14
+ </td><td>
+ <code class="systemitem">uucp</code>
+ </td></tr><tr><td>
+ <code class="systemitem">man</code>
+ </td><td>
+ 15
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">games</code>
+ </td><td>
+ 20
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">gopher</code>
+ </td><td>
+ 30
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">video</code>
+ </td><td>
+ 39
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dip</code>
+ </td><td>
+ 40
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">ftp</code>
+ </td><td>
+ 50
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">lock</code>
+ </td><td>
+ 54
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">audio</code>
+ </td><td>
+ 63
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">nobody</code>
+ </td><td>
+ 99
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">users</code>
+ </td><td>
+ 100
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dbus</code>
+ </td><td>
+ 81
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">usbmuxd</code>
+ </td><td>
+ 113
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">utmp</code>
+ </td><td>
+ 22
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">utempter</code>
+ </td><td>
+ 35
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">avahi-autoipd</code>
+ </td><td>
+ 170
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">floppy</code>
+ </td><td>
+ 19
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">vcsa</code>
+ </td><td>
+ 69
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">rpc</code>
+ </td><td>
+ 32
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">rtkit</code>
+ </td><td>
+ 499
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">abrt</code>
+ </td><td>
+ 498
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">nscd</code>
+ </td><td>
+ 28
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">desktop_admin_r</code>
+ </td><td>
+ 497
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">desktop_user_r</code>
+ </td><td>
+ 496
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">cdrom</code>
+ </td><td>
+ 11
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">tape</code>
+ </td><td>
+ 33
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dialout</code>
+ </td><td>
+ 18
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">haldaemon</code>
+ </td><td>
+ 68
+ </td><td>
+ <code class="systemitem">haldaemon</code>
+ </td></tr><tr><td>
+ <code class="systemitem">apache</code>
+ </td><td>
+ 48
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">ldap</code>
+ </td><td>
+ 55
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">saslauth</code>
+ </td><td>
+ 495
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">postdrop</code>
+ </td><td>
+ 90
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">postfix</code>
+ </td><td>
+ 89
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">avahi</code>
+ </td><td>
+ 70
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">ntp</code>
+ </td><td>
+ 38
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">rpcuser</code>
+ </td><td>
+ 29
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">nfsnobody</code>
+ </td><td>
+ 65534
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">pulse</code>
+ </td><td>
+ 494
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">pulse-access</code>
+ </td><td>
+ 493
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">fuse</code>
+ </td><td>
+ 492
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">gdm</code>
+ </td><td>
+ 42
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">stapdev</code>
+ </td><td>
+ 491
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">stapusr</code>
+ </td><td>
+ 490
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">sshd</code>
+ </td><td>
+ 74
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">tcpdump</code>
+ </td><td>
+ 72
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">slocate</code>
+ </td><td>
+ 21
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dovecot</code>
+ </td><td>
+ 97
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dovenull</code>
+ </td><td>
+ 489
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">mailnull</code>
+ </td><td>
+ 47
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">smmsp</code>
+ </td><td>
+ 51
+ </td><td>
+ —
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div><div class="section"
id="s1-users-groups-private-groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-private-groups">3.6. User Private
Groups</h2></div></div></div><a id="id532641"
class="indexterm"></a><a id="id532653"
class="indexterm"></a><a id="id532665"
class="indexterm"></a><a id="id421522"
class="indexterm"></a><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em>
(<em class="firstterm">UPG</em>) scheme, which makes UNIX groups
easier to manage. A UPG is created whenever a new user is added to the system. It has the
same name as the user for which it was created and that user is the only member of the
UPG.
+ </div><div class="para">
+ UPGs make it safe to set default permissions for a newly created file or directory,
allowing both the user and <span class="emphasis"><em>the group of
that user</em></span> to make modifications to the file or directory.
+ </div><div class="para">
+ The setting which determines what permissions are applied to a newly created file or
directory is called a <em class="firstterm">umask</em> and is
configured in the <code class="filename">/etc/bashrc</code> file.
Traditionally on UNIX systems, the <code
class="command">umask</code> is set to <code
class="command">022</code>, which allows only the user who created the
file or directory to make modifications. Under this scheme, all other users, <span
class="emphasis"><em>including members of the creator's
group</em></span>, are not allowed to make any modifications. However, under
the UPG scheme, this "group protection" is not necessary since every user has
their own private group.
+ </div><div class="section"
id="s2-users-groups-rationale"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-users-groups-rationale">3.6.1. Group
Directories</h3></div></div></div><a id="id757864"
class="indexterm"></a><a id="id757876"
class="indexterm"></a><div class="para">
+ System administrators usually like to create a group for each major project and
assign people to the group when they need to access that project's files. With this
traditional scheme, file managing is difficult; when someone creates a file, it is
associated with the primary group to which they belong. When a single person works on
multiple projects, it becomes difficult to associate the right files with the right group.
However, with the UPG scheme, groups are automatically assigned to files created within a
directory with the <em class="firstterm">setgid</em> bit set. The
setgid bit makes managing group projects that share a common directory very simple because
any files a user creates within the directory are owned by the group which owns the
directory.
+ </div><div class="para">
+ For example, a group of people need to work on files in the <code
class="filename">/opt/myproject/</code> directory. Some people are
trusted to modify the contents of this directory, but not everyone.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ As <code class="systemitem">root</code>, create the <code
class="filename">/opt/myproject/</code> directory by typing the
following at a shell prompt:
+ </div><pre class="screen"><code
class="command">mkdir
/opt/myproject</code></pre></li><li class="step"><div
class="para">
+ Add the <code class="systemitem">myproject</code> group to
the system:
+ </div><pre class="screen"><code
class="command">groupadd myproject</code></pre></li><li
class="step"><div class="para">
+ Associate the contents of the <code
class="filename">/opt/myproject/</code> directory with the <code
class="systemitem">myproject</code> group:
+ </div><pre class="screen"><code
class="command">chown root:myproject
/opt/myproject</code></pre></li><li class="step"><div
class="para">
+ Allow users to create files within the directory, and set the setgid bit:
+ </div><pre class="screen"><code
class="command">chmod 2775
/opt/myproject</code></pre></li></ol></div><div
class="para">
+ At this point, all members of the <code
class="systemitem">myproject</code> group can create and edit files in
the <code class="filename">/opt/myproject/</code> directory without
the administrator having to change file permissions every time users write new files. To
verify that the permissions have been set correctly, run the following command:
+ </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-shadow-utilities"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-shadow-utilities">3.7. Shadow
Passwords</h2></div></div></div><a id="id951510"
class="indexterm"></a><a id="id951522"
class="indexterm"></a><div class="para">
+ In multiuser environments it is very important to use <em
class="firstterm">shadow passwords</em> (provided by the <code
class="filename">shadow-utils</code> package). Doing so enhances the
security of system authentication files. For this reason, the installation program enables
shadow passwords by default.
+ </div><div class="para">
+ The following list shows the advantages shadow passwords have over the traditional way
of storing passwords on UNIX-based systems:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Improves system security by moving encrypted password hashes from the world-readable
<code class="filename">/etc/passwd</code> file to <code
class="filename">/etc/shadow</code>, which is readable only by the
<code class="systemitem">root</code> user.
+ </div></li><li class="listitem"><div
class="para">
+ Stores information about password aging.
+ </div></li><li class="listitem"><div
class="para">
+ Allows the <code class="filename">/etc/login.defs</code> file
to enforce security policies.
+ </div></li></ul></div><div class="para">
+ Most utilities provided by the <code
class="filename">shadow-utils</code> package work properly whether or
not shadow passwords are enabled. However, since password aging information is stored
exclusively in the <code class="filename">/etc/shadow</code> file,
any commands which create or modify password aging information do not work.
+ </div><div class="para">
+ The following is a list of commands which do not work without first enabling shadow
passwords:
+ </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="command">usermod</code> <code
class="option">-e</code> or <code
class="option">-f</code> options
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">useradd</code> <code
class="option">-e</code> or <code
class="option">-f</code> options
+ </div></li></ul></div></div><div
class="section" id="s1-users-groups-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-additional-resources">3.8. Additional
Resources</h2></div></div></div><a id="id540012"
class="indexterm"></a><a id="id464936"
class="indexterm"></a><div class="para">
+ For more information about users and groups, and tools to manage them, refer to the
following resources.
+ </div><div class="section"
id="s2-users-groups-documentation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-users-groups-documentation">3.8.1. Installed
Documentation</h3></div></div></div><a id="id464961"
class="indexterm"></a><a id="id464977"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ Related man pages — There are a number of man pages for the various applications
and configuration files involved with managing users and groups. Some of the more
important man pages have been listed here:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">User and Group
Administrative Applications</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">man chage</code> — A command to
modify password aging policies and account expiration.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man gpasswd</code> — A command to
administer the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man groupadd</code> — A command to
add groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man grpck</code> — A command to
verify the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man groupdel</code> — A command to
remove groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man groupmod</code> — A command to
modify group membership.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man pwck</code> — A command to
verify the <code class="filename">/etc/passwd</code> and <code
class="filename">/etc/shadow</code> files.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man pwconv</code> — A tool to
convert standard passwords to shadow passwords.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man pwunconv</code> — A tool to
convert shadow passwords to standard passwords.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man useradd</code> — A command to
add users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man userdel</code> — A command to
remove users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man usermod</code> — A command to
modify users.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term">Configuration
Files</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">man 5 group</code> — The file
containing group information for the system.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man 5 passwd</code> — The file
containing user information for the system.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man 5 shadow</code> — The file
containing passwords and account expiration information for the system.
+ </div></li></ul></div></dd></dl></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">Part II. Package
Management</h1></div></div></div><div
class="partintro" id="id606297"><div></div><div
class="para">
+ All software on a Fedora system is divided into RPM packages, which can be installed,
upgraded, or removed. This part describes how to manage packages on Fedora using 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="toc"><p><strong>Table of
Contents</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. Checking For and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Checking_For_Updates">4.1.1.
Checking For Updates</a></span></dt><dt><span
class="section"><a href="#sec-Updating_Packages">4.1.2.
Updating Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Preserving_Configuration_File_Changes">4.1.3. Preserving
Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Packages_and_Package_Groups">4.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Searching_Packages">4.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="#sec-Listing_Packages">4.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Package_Information">4.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="#sec-Installing">4.2.4. Installing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-Removing">4.2.5. Removing
Packages</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Configuring_Yum_and_Yum_Repositories">4.3. Configuring Yum and Yum
Repositories</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Setting_main_Options">4.3.1.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_repository_Options">4.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="#sec-Using_Yum_Variables">4.3.3.
Using Yum Variables</a></span></dt><dt><span
class="section"><a
href="#sec-Creating_a_Yum_Repository">4.3.4. Creating a Yum
Repository</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Yum_Plugins">4.4. Yum
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Enabling,
Configuring and Disabling Yum Plugins</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_More_Yum_Plugins">4.4.2. Installing Additional Yum
Plugins</a></span></dt><dt><span
class="section"><a href="#sec-Plugin_Descriptions">4.4.3.
Plugin
Descriptions</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Additional_Resources">4.5.
Additional
Resources</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. Updating Packages
with Software
Update</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Setting_preferences_for_checking_for_updates">5.1.1. Setting the
Update-Checking Interval</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_preferences_for_software_sources">5.1.2. Setting the
Software
Sources</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Using_Add_Remove_Software">5.2.
Using Add/Remove
Software</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. Refreshing
Software Sources (Yum Repositories)</a></span></dt><dt><span
class="section"><a
href="#sec-Finding_Packages_with_Filters">5.2.2. Finding Packages with
Filters</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_and_Removing_Packages_and_Dependencies">5.2.3.
Installing and Removing Packages (and
Dependencies)</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_and_Removing_Package_Groups">5.2.4. Installing and
Removing Package Groups</a></span></dt><dt><span
class="section"><a
href="#sec-Viewing_the_Transaction_Log">5.2.5. Viewing the Transaction
Log</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-PackageKit_Architecture">5.3.
PackageKit Architecture</a></span></dt><dt><span cl
ass="section"><a
href="#ch-Graphical_Package_Management-sec-Additional_Resources">5.4.
Additional
Resources</a></span></dt></dl></dd></dl></div></div><div
xml:lang="en-US" class="chapter" id="ch-yum"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 4. Yum</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#sec-Checking_For_and_Updating_Packages">4.1. Checking For and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Checking_For_Updates">4.1.1.
Checking For Updates</a></span></dt><dt><span
class="section"><a href="#sec-Updating_Packages">4.1.2.
Updating Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Preserving_Configuration_File_Changes">4.1.3. Preserving
Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Packages_and_Package_Groups">4.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Searchin
g_Packages">4.2.1. Searching
Packages</a></span></dt><dt><span
class="section"><a href="#sec-Listing_Packages">4.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Package_Information">4.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="#sec-Installing">4.2.4. Installing
Packages</a></span></dt><dt><span
class="section"><a href="#sec-Removing">4.2.5. Removing
Packages</a></span></dt></dl></dd><dt><span
class="section"><a
href="#sec-Configuring_Yum_and_Yum_Repositories">4.3. Configuring Yum and Yum
Repositories</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-Setting_main_Options">4.3.1.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_repository_Options">4.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="#sec-Using_Yum_Variables">4.3.3.
Using Yum Variables</a></span></dt><dt><span
class="section"><a href="#sec-Creating
_a_Yum_Repository">4.3.4. Creating a Yum
Repository</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Yum_Plugins">4.4. Yum
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Enabling,
Configuring and Disabling Yum Plugins</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_More_Yum_Plugins">4.4.2. Installing Additional Yum
Plugins</a></span></dt><dt><span
class="section"><a href="#sec-Plugin_Descriptions">4.4.3.
Plugin
Descriptions</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Additional_Resources">4.5.
Additional Resources</a></span></dt></dl></div><div
class="para">
+ <span class="application"><strong>Yum</strong></span>
is the The Fedora Project package manager that is able to query for information about
packages, fetch packages from repositories, install and uninstall packages using automatic
dependency resolution, and update an entire system to the latest available packages.
<span class="application"><strong>Yum</strong></span>
performs automatic dependency resolution on packages you are updating, installing or
removing, and thus is able to automatically determine, fetch and install all available
dependent packages. <span
class="application"><strong>Yum</strong></span> can be
configured with new, additional repositories, or <em
class="firstterm">package sources</em>, and also provides many plugins
which enhance and extend its capabilities. <span
class="application"><strong>Yum</strong></span> is able to
perform many of the same tasks that <span
class="application"><strong>RPM</strong></span> can;
additionally, many of the command lin
e options are similar. <span
class="application"><strong>Yum</strong></span> enables
easy and simple package management on a single machine or on groups of them.
+ </div><div class="important"
id="important-Secure_Package_Management_with_GPG-Signed_Packages"><div
class="admonition_header"><h2>Secure package management with GPG-signed
packages</h2></div><div class="admonition"><div
class="para">
+ <span
class="application"><strong>Yum</strong></span> provides
secure package management by enabling GPG (Gnu Privacy Guard; also known as GnuPG)
signature verification on GPG-signed packages to be turned on for all package repositories
(i.e. package sources), or for individual repositories. When signature verification is
enabled, <span
class="application"><strong>Yum</strong></span> will refuse
to install any packages not GPG-signed with the correct key for that repository. This
means that you can trust that the <span
class="application"><strong>RPM</strong></span> packages
you download and install on your system are from a trusted source, such as The Fedora
Project, and were not modified during transfer. Refer to <a class="xref"
href="#sec-Configuring_Yum_and_Yum_Repositories">Section 4.3, “Configuring
Yum and Yum Repositories”</a> for details on enabling signature-checking with
<span class="application"><strong>Yum</strong></span>,
or <a class="xref" href="#s1-che
ck-rpm-sig">Section A.3, “Checking a Package's Signature”</a> for
information on working with and verifying GPG-signed <span
class="application"><strong>RPM</strong></span> packages in
general.
+ </div></div></div><div class="para">
+ <span class="application"><strong>Yum</strong></span>
also enables you to easily set up your own repositories of <span
class="application"><strong>RPM</strong></span> packages
for download and installation on other machines.
+ </div><div class="para">
+ Learning <span
class="application"><strong>Yum</strong></span> is a
worthwhile investment because it is often the fastest way to perform system administration
tasks, and it provides capabilities beyond those provided by the <span
class="application"><strong>PackageKit</strong></span>
graphical package management tools. Refer to <a class="xref"
href="#ch-PackageKit">Chapter 5, <em>PackageKit</em></a>
for details on using <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="note"
id="note-Note_Yum_and_Superuser_Privileges"><div
class="admonition_header"><h2>Yum and superuser
privileges</h2></div><div class="admonition"><div
class="para">
+ You must have superuser privileges in order to use <code
class="command">yum</code> to install, update or remove packages on
your system. All examples in this chapter assume that you have already obtained superuser
privileges by using either the <code class="command">su</code> or
<code class="command">sudo</code> command.
+ </div></div></div><div class="section"
id="sec-Checking_For_and_Updating_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-Checking_For_and_Updating_Packages">4.1. Checking For and Updating
Packages</h2></div></div></div><div class="section"
id="sec-Checking_For_Updates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Checking_For_Updates">4.1.1. Checking For
Updates</h3></div></div></div><a id="id553768"
class="indexterm"></a><div class="para">
+ You can use the <code class="command">yum check-update</code>
command to see which installed packages on your system have updates available:
+ </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">
+ The packages in the above output are listed as having updates available. The first
package in the list is <span
class="application"><strong>PackageKit</strong></span>, the
graphical package manager. The line in the example output tells us:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">PackageKit</code> — the name of
the package
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">x86_64</code> — the CPU
architecture the package was built for
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">0.6.14</code> — the version of
the updated package to be installed
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">fedora</code> — the repository
in which the updated package is located
+ </div></li></ul></div><div class="para">
+ The output also shows us that we can update the kernel (the <span
class="package">kernel</span> package), <span
class="application"><strong>Yum</strong></span> and
<span class="application"><strong>RPM</strong></span>
themselves (the <code class="filename">yum</code> and <code
class="filename">rpm</code> packages), as well as their dependencies
(such as the <span class="package">rpm-libs</span> and <span
class="package">rpm-python</span> packages), all using <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"
id="sec-Updating_Packages">4.1.2. Updating
Packages</h3></div></div></div><a id="id609951"
class="indexterm"></a><div class="para">
+ You can choose to update a single package, multiple packages, or all packages at
once. If any dependencies of the package (or packages) you update have updates available
themselves, then they are updated too.
+ </div><h4> Updating a Single Package </h4><a
id="id609973" class="indexterm"></a><div
class="para">
+ To update a single package, enter <code class="command">yum update
<em
class="replaceable"><code>package_name</code></em></code>,
for example:
+ </div><pre class="screen">~]# <code
class="command">yum update gdb</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+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">
+ This output contains several items of interest:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ <code class="computeroutput">Loaded plugins:</code> —
<code class="command">yum</code> always informs you which <span
class="application"><strong>Yum</strong></span> plugins are
installed and enabled. Here, <code class="command">yum</code> is
using the <span
class="application"><strong>langpacks</strong></span>,
<span
class="application"><strong>presto</strong></span>, and
<span
class="application"><strong>refresh-packagekit</strong></span>
plugins. Refer to <a class="xref"
href="#sec-Yum_Plugins">Section 4.4, “Yum Plugins”</a> for general
information on <span
class="application"><strong>Yum</strong></span> plugins, or
to <a class="xref"
href="#sec-Plugin_Descriptions">Section 4.4.3, “Plugin
Descriptions”</a> for descriptions of specific plugins.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">gdb.x86_64</code> — you can
download and install new <span class="package">gdb</span> package.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">yum</code> presents the update
information and then prompts you as to whether you want it to perform the update; <code
class="command">yum</code> runs interactively by default. If you
already know which transactions <code class="command">yum</code>
plans to perform, you can use the <code class="option">-y</code>
option to automatically answer <code class="command">yes</code> to
any questions <code class="command">yum</code> may ask (in which
case it runs non-interactively). However, you should always examine which changes <code
class="command">yum</code> plans to make to the system so that you can
easily troubleshoot any problems that might arise.
+ </div></li></ol></div><div class="para">
+ If a transaction does go awry, you can view <span
class="application"><strong>Yum</strong></span>'s log
of transactions by typing the <code class="command">cat
/var/log/yum.log</code> command at a shell prompt. The most recent transactions are
listed at the end of the log file.
+ </div><div class="important"
id="important-Important-Updating_and_Installing_Kernels_with_Yum"><div
class="admonition_header"><h2>Updating and installing kernels with
Yum</h2></div><div class="admonition"><div
class="para">
+ <code class="command">yum</code> always <span
class="emphasis"><em>installs</em></span> a new kernel in
the same sense that <span
class="application"><strong>RPM</strong></span> installs a
new kernel when you use the command <code class="command">rpm -i
kernel</code>. Therefore, you do not need to worry about the distinction between
<span class="emphasis"><em>installing</em></span> and
<span class="emphasis"><em>upgrading</em></span> a
kernel package when you use <code class="command">yum</code>: it
will do the right thing, regardless of whether you are using the <code
class="command">yum update</code> or <code
class="command">yum install</code> command.
+ </div><div class="para">
+ When using <span
class="application"><strong>RPM</strong></span>, on the
other hand, it is important to use the <code class="command">rpm -i
kernel</code> command (which installs a new kernel) instead of <code
class="command">rpm -u kernel</code> (which <span
class="emphasis"><em>replaces</em></span> the current
kernel). Refer to <a class="xref"
href="#sec-Installing_and_Upgrading">Section A.2.2, “Installing and
Upgrading”</a> for more information on installing/updating kernels with <span
class="application"><strong>RPM</strong></span>.
+ </div></div></div><h4> Updating All Packages and Their
Dependencies </h4><a id="id741827"
class="indexterm"></a><div class="para">
+ To update all packages and their dependencies, simply enter the <code
class="command">yum update</code> command (without any arguments):
+ </div><pre class="screen">~]# <code
class="command">yum update</code></pre><h4> Updating
Security-Related Packages </h4><a id="id741858"
class="indexterm"></a><a id="id846105"
class="indexterm"></a><a id="id846117"
class="indexterm"></a><div class="para">
+ Discovering which packages have security updates available and then updating those
packages quickly and easily is important. <span
class="application"><strong>Yum</strong></span> provides
the plugin for this purpose. The <span
class="application"><strong>security</strong></span> plugin
extends the <code class="command">yum</code> command with a set of
highly-useful security-centric commands, subcommands and options. Refer to <a
class="xref" href="#sec-Plugin_Descriptions">Section 4.4.3, “Plugin
Descriptions”</a> for specific information.
+ </div></div><div class="section"
id="sec-Preserving_Configuration_File_Changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Preserving_Configuration_File_Changes">4.1.3. Preserving
Configuration File Changes</h3></div></div></div><a
id="id589706" class="indexterm"></a><div
class="para">
+ You will inevitably make changes to the configuration files installed by packages as
you use your Fedora system. <span
class="application"><strong>RPM</strong></span>, which
<span class="application"><strong>Yum</strong></span>
uses to perform changes to the system, provides a mechanism for ensuring their integrity.
Refer to <a class="xref"
href="#sec-Installing_and_Upgrading">Section A.2.2, “Installing and
Upgrading”</a> for details on how to manage changes to configuration files across
package upgrades.
+ </div></div></div><div class="section"
id="sec-Packages_and_Package_Groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-Packages_and_Package_Groups">4.2. Packages and Package
Groups</h2></div></div></div><a id="id679431"
class="indexterm"></a><a id="id679443"
class="indexterm"></a><div class="section"
id="sec-Searching_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Searching_Packages">4.2.1. Searching
Packages</h3></div></div></div><a id="id679463"
class="indexterm"></a><a id="id897790"
class="indexterm"></a><div class="para">
+ You can search all <acronym class="acronym">RPM</acronym>
package names, descriptions and summaries by using the <code
class="command">yum search <em
class="replaceable"><code>term</code></em> [<span
class="optional"><em
class="replaceable"><code>more_terms</code></em></span>]</code>
command. <code class="command">yum</code> displays the list of
matches for each term, for example:
+ </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><div class="para">
+ The <code class="command">yum search</code> command is useful
for searching for packages you do not know the name of, but for which you know a related
term.
+ </div></div><div class="section"
id="sec-Listing_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Listing_Packages">4.2.2. Listing
Packages</h3></div></div></div><a id="id720702"
class="indexterm"></a><a id="id720718"
class="indexterm"></a><div class="para">
+ <code class="command">yum list</code> and related commands
provide information about packages, package groups, and repositories.
+ </div><div class="para">
+ All of <span
class="application"><strong>Yum</strong></span>'s list
commands allow you to filter the results by appending one or more <em
class="firstterm">glob expressions</em> as arguments. Glob expressions
are normal strings of characters which contain one or more of the wildcard characters
<code class="command">*</code> (which expands to match any character
multiple times) and <code class="command">?</code> (which expands to
match any one character).
+ </div><div class="note"
id="note-Tip-Filtering_Results_with_Glob_Expressions"><div
class="admonition_header"><h2>Filtering results with glob
expressions</h2></div><div class="admonition"><a
id="id789953" class="indexterm"></a><a
id="id429293" class="indexterm"></a><div
class="para">
+ Be careful to escape the glob expressions when passing them as arguments to a
<code class="command">yum</code> command, otherwise the Bash shell
will interpret these expressions as <em class="firstterm">pathname
expansions</em>, and potentially pass all files in the current directory that match
the globs to <code class="command">yum</code>. To make sure the glob
expressions are passed to <code class="command">yum</code> as
intended, either:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ escape the wildcard characters by preceding them with a backslash character
+ </div></li><li class="listitem"><div
class="para">
+ double-quote or single-quote the entire glob expression.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref"
href="#ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions">Example 4.1,
“Listing all ABRT addons and plugins using glob expressions”</a> and <a
class="xref"
href="#ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards">Example 4.4,
“Listing available packages using a single glob expression with escaped wildcard
characters”</a> for an example usage of both these methods.
+ </div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="command">yum list <em
class="replaceable"><code>glob_expr</code></em> [<span
class="optional"><em
class="replaceable"><code>more_glob_exprs</code></em></span>]</code>
</span></dt><dd><div class="para">
+ Lists information on installed and available packages matching all glob
expressions.
+ </div><div class="example"
id="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions"><h6>Example 4.1. Listing
all ABRT addons and plugins using glob expressions</h6><div
class="example-contents"><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="id568682"
class="indexterm"></a>
+ <a id="id598986" class="indexterm"></a>
+ <code class="command">yum list all</code>
</span></dt><dd><div class="para">
+ Lists all installed <span
class="emphasis"><em>and</em></span> available packages.
+ </div><div class="example"
id="ex-Listing_all_installed_and_available_packages"><h6>Example 4.2. Listing
all installed and available packages</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">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="id800918" class="indexterm"></a>
+ <a id="id800934" class="indexterm"></a>
+ <code class="command">yum list installed</code>
</span></dt><dd><div class="para">
+ Lists all packages installed on your system. The rightmost column in the output
lists the repository from which the package was retrieved.
+ </div><div class="example"
id="ex-Listing_installed_packages_using_a_double-quoted_glob_expression"><h6>Example 4.3. Listing
installed packages using a double-quoted glob expression</h6><div
class="example-contents"><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="id613059"
class="indexterm"></a>
+ <a id="id945953" class="indexterm"></a>
+ <code class="command">yum list available</code>
</span></dt><dd><div class="para">
+ Lists all available packages in all enabled repositories.
+ </div><div class="example"
id="ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards"><h6>Example 4.4. Listing
available packages using a single glob expression with escaped wildcard
characters</h6><div class="example-contents"><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="id977382"
class="indexterm"></a>
+ <a id="id977397" class="indexterm"></a>
+ <code class="command">yum grouplist</code>
</span></dt><dd><div class="para">
+ Lists all package groups.
+ </div><div class="example"
id="ex-Listing_all_package_groups"><h6>Example 4.5. Listing all package
groups</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">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="id527735" class="indexterm"></a>
+ <a id="id615058" class="indexterm"></a>
+ <code class="command">yum repolist</code>
</span></dt><dd><div class="para">
+ Lists the repository ID, name, and number of packages it provides for each
<span class="emphasis"><em>enabled</em></span>
repository.
+ </div><div class="example"
id="ex-Listing_enabled_repositories"><h6>Example 4.6. Listing enabled
repositories</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"
id="sec-Displaying_Package_Information">4.2.3. Displaying Package
Information</h3></div></div></div><a id="id542244"
class="indexterm"></a><a id="id542260"
class="indexterm"></a><div class="para">
+ The <code class="command">yum info <em
class="replaceable"><code>package_name</code></em>
[<span class="optional"><em
class="replaceable"><code>more_names</code></em></span>]</code>
command displays information about one or more packages (glob expressions are valid here
as well). For example, to display information about the <span
class="package">abrt</span> package, type:
+ </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><div class="para">
+ <code class="command">yum info <em
class="replaceable"><code>package_name</code></em></code>
is similar to the <code class="command">rpm -q --info <em
class="replaceable"><code>package_name</code></em></code>
command, but provides as additional information the ID of the <span
class="application"><strong>Yum</strong></span> repository
the RPM package is found in (look for the <code
class="computeroutput">From repo</code> line in the output).
+ </div><div class="para">
+ The <code class="command">yumdb info <em
class="replaceable"><code>package_name</code></em>
[<span class="optional"><em
class="replaceable"><code>more_names</code></em></span>]</code>
command can be used to query the <span
class="application"><strong>Yum</strong></span> database
for alternative and useful information about a package, including the checksum of the
package (and algorithm used to produce it, such as SHA-256), the command given on the
command line that was invoked to install the package (if any), and the reason that the
package is installed on the system (where <code
class="computeroutput">user</code> indicates it was installed by the
user, and <code class="computeroutput">dep</code> means it was
brought in as a dependency). For example, to display additional information about the
<span class="package">yum</span> package, type:
+ </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">
+ For more information on the <code class="command">yumdb</code>
command, see <code class="command">man yumdb</code>.
+ </div><div class="para">
+ Finally, the <code class="command">yum history</code> command
can be used to show a timeline of <span
class="application"><strong>Yum</strong></span>
transactions, the dates and times on when they occurred, the number of packages affected,
whether transactions succeeded or were aborted, and if the RPM database was changed
between transactions. Refer to the <code
class="computeroutput">history</code> section of <code
class="command">man yum</code> for details.
+ </div></div><div class="section"
id="sec-Installing"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Installing">4.2.4. Installing
Packages</h3></div></div></div><a id="id460545"
class="indexterm"></a><a id="id403740"
class="indexterm"></a><div class="para">
+ You can install a package and all of its non-installed dependencies by entering:
+ </div><pre class="screen"><code
class="command">yum install <em
class="replaceable"><code>package_name</code></em></code></pre><div
class="para">
+ You can install multiple packages simultaneously by appending their names as
arguments:
+ </div><pre class="screen"><code
class="command">yum install <em
class="replaceable"><code>package_name</code></em>
[<span class="optional"><em
class="replaceable"><code>more_names</code></em></span>]</code></pre><div
class="para">
+ If you are installing packages on a <em
class="firstterm">multilib</em> system, such as an AMD64 or Intel 64
machine, you can specify the architecture of the package (as long as it is available in an
enabled repository) by appending <em
class="replaceable"><code>.arch</code></em> to the package
name. For example, to install the <span
class="package">sqlite2</span> package for <code
class="systemitem">i686</code>, type:
+ </div><pre class="screen">~]# <code
class="command">yum install sqlite2.i686</code></pre><div
class="para">
+ You can use glob expressions to quickly install multiple similarly-named packages:
+ </div><pre class="screen">~]# <code
class="command">yum install
audacious-plugins-\*</code></pre><div class="para">
+ In addition to package names and glob expressions, you can also provide file names to
<code class="command">yum install</code>. If you know the name of
the binary you want to install, but not its package name, you can give <code
class="command">yum install</code> the path name:
+ </div><pre class="screen">~]# <code
class="command">yum install /usr/sbin/named</code></pre><div
class="para">
+ <code class="command">yum</code> then searches through its
package lists, finds the package which provides <code
class="filename">/usr/sbin/named</code>, if any, and prompts you as to
whether you want to install it.
+ </div><div class="note"
id="note-Finding_which_package_owns_a_file"><div
class="admonition_header"><h2>Finding which package owns a
file</h2></div><div class="admonition"><div
class="para">
+ If you know you want to install the package that contains the <code
class="filename">named</code> binary, but you do not know in which
<code class="filename">bin</code> or <code
class="filename">sbin</code> directory is the file installed, use the
<code class="command">yum provides</code> command with a glob
expression:
+ </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>
is a common and useful trick to find the packages that contain <em
class="replaceable"><code>file_name</code></em>.
+ </div></div></div><h4> Installing a Package Group
</h4><a id="id678622" class="indexterm"></a><a
id="id678634" class="indexterm"></a><div
class="para">
+ A package group is similar to a package: it is not useful by itself, but installing
one pulls a group of dependent packages that serve a common purpose. A package group has a
name and a <em class="firstterm">groupid</em>. The <code
class="command">yum grouplist -v</code> command lists the names of all
package groups, and, next to each of them, their groupid in parentheses. The groupid is
always the term in the last pair of parentheses, such as <code
class="literal">kde-desktop</code> in the following example:
+ </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">
+ You can install a package group by passing its full group name (without the groupid
part) to <code class="command">groupinstall</code>, for example:
+ </div><pre class="screen">~]# <code
class="command">yum groupinstall "KDE Software
Compilation"</code></pre><div class="para">
+ You can also install by groupid:
+ </div><pre class="screen">~]# <code
class="command">yum groupinstall kde-desktop</code></pre><div
class="para">
+ You can even pass the groupid (or quoted name) to the <code
class="command">install</code> command if you prepend it with an
<span class="keysym">@</span>-symbol (which tells <code
class="command">yum</code> that you want to perform a <code
class="command">groupinstall</code>):
+ </div><pre class="screen">~]# <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"
id="sec-Removing">4.2.5. Removing
Packages</h3></div></div></div><a id="id727812"
class="indexterm"></a><a id="id990131"
class="indexterm"></a><a id="id990143"
class="indexterm"></a><a id="id990159"
class="indexterm"></a><div class="para">
+ The <code class="command">yum remove <em
class="replaceable"><code>package_name</code></em></code>
uninstalls (removes in <span
class="application"><strong>RPM</strong></span> and
<span class="application"><strong>Yum</strong></span>
terminology) the package, as well as any packages that depend on it. As when you install
multiple packages, you can remove several at once by adding more package names to the
command. For example, to remove <span class="package">totem</span>,
<span class="package">rhythmbox</span>, and <span
class="package">sound-juicer</span>, type the following at a shell
prompt:
+ </div><pre class="screen">~]# <code
class="command">yum remove totem rhythmbox
sound-juicer</code></pre><div class="para">
+ Similar to <code class="command">install</code>, <code
class="command">remove</code> can take these arguments:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ package names
+ </div></li><li class="listitem"><div
class="para">
+ glob expressions
+ </div></li><li class="listitem"><div
class="para">
+ file lists
+ </div></li><li class="listitem"><div
class="para">
+ package provides
+ </div></li></ul></div><div class="warning"
id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It"><div
class="admonition_header"><h2>Removing a package when other packages
depend on it</h2></div><div class="admonition"><div
class="para">
+ <span
class="application"><strong>Yum</strong></span> is not able
to remove a package without also removing packages which depend on it. This type of
operation can only be performed by <span
class="application"><strong>RPM</strong></span>, is not
advised, and can potentially leave your system in a non-functioning state or cause
applications to misbehave and/or crash. For further information, refer to <a
class="xref" href="#s2-rpm-uninstalling">Section A.2.4,
“Uninstalling”</a> in the <span
class="application"><strong>RPM</strong></span> chapter.
+ </div></div></div><h4> Removing a Package Group
</h4><div class="para">
+ You can remove a package group using syntax congruent with the <code
class="command">install</code> syntax. The following are alternative
but equivalent ways of removing the <code class="literal">KDE Software
Compilation</code> group:
+ </div><pre class="screen">~]# <code
class="command">yum groupremove "KDE Software
Compilation"</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>Intelligent package group
removal</h2></div><div class="admonition"><a
id="id403484" class="indexterm"></a><a
id="id403496" class="indexterm"></a><div
class="para">
+ When you tell <span
class="application"><strong>yum</strong></span> to remove a
package group, it will remove every package in that group, even if those packages are
members of other package groups or dependencies of other installed packages. However, you
can instruct <code class="command">yum</code> to remove only those
packages which are not required by any other packages or groups by adding the <code
class="option">groupremove_leaf_only=1</code> directive to the <code
class="literal">[main]</code> section of the <code
class="filename">/etc/yum.conf</code> configuration file. For more
information on this directive, refer to <a class="xref"
href="#sec-Setting_main_Options">Section 4.3.1, “Setting [main]
Options”</a>.
+ </div></div></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"
id="sec-Configuring_Yum_and_Yum_Repositories">4.3. Configuring Yum and Yum
Repositories</h2></div></div></div><a id="id1000526"
class="indexterm"></a><a id="id1000538"
class="indexterm"></a><div class="para">
+ This section shows you how to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ set global <span
class="application"><strong>Yum</strong></span> options by
editing the <code class="literal">[main]</code> section of the
<code class="filename">/etc/yum.conf</code> configuration file;
+ </div></li><li class="listitem"><div
class="para">
+ set options for individual repositories by editing the <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections in <code class="filename">/etc/yum.conf</code> and <code
class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code> directory;
+ </div></li><li class="listitem"><div
class="para">
+ use <span
class="application"><strong>Yum</strong></span> variables
in <code class="filename">/etc/yum.conf</code> and files in <code
class="filename">/etc/yum.repos.d/</code> so that dynamic version and
architecture values are handled correctly; and,
+ </div></li><li class="listitem"><div
class="para">
+ set up your own custom <span
class="application"><strong>Yum</strong></span>
repository.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">/etc/yum.conf</code> configuration
file contains one mandatory <code class="literal">[main]</code>
section under which you can set <span
class="application"><strong>Yum</strong></span> options.
The values that you define in the <code
class="literal">[main]</code> section of <code
class="filename">yum.conf</code> have global effect, and may override
values set in individual <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections. You can also add <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections to <code class="filename">/etc/yum.conf</code>; however,
best practice is to define individual repositories in new or existing <code
class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code>directory. Refer to <a
class="xref" href="#sec-Setting_repository_Options">Section 4.3.2,
“Setting [repository] Options”</a> if you need to add or edit
repository-specific information.
+ </div><div class="section"
id="sec-Setting_main_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Setting_main_Options">4.3.1. Setting [main]
Options</h3></div></div></div><a id="id505542"
class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/yum.conf</code> configuration
file contains exactly one <code class="literal">[main]</code>
section. You can add many additional options under the <code
class="literal">[main]</code> section heading in <code
class="filename">/etc/yum.conf</code>. Some of the key-value pairs in
the <code class="literal">[main]</code> section affect how <code
class="command">yum</code> operates; others affect how <span
class="application"><strong>Yum</strong></span> treats
repositories. The best source of information for all <span
class="application"><strong>Yum</strong></span> options is
in the <code class="literal">[main] OPTIONS</code> and <code
class="literal">[repository] OPTIONS</code> sections of <code
class="command">man yum.conf</code>.
+ </div><div class="para">
+ A sample <code class="filename">/etc/yum.conf</code>
configuration file can look like this:
+ </div><pre class="screen">[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">[comments abridged]</span></em>
+# PUT YOUR REPOS HERE OR IN separate files named file.repo
+# in /etc/yum.repos.d</pre><div class="para">
+ The following is a list of the most commonly-used options in the <code
class="literal">[main]</code> section, and descriptions for each:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">assumeyes=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — <code
class="command">yum</code> should prompt for confirmation of critical
actions it performs. This is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — Do not prompt for
confirmation of critical <code class="command">yum</code> actions.
If <code class="literal">assumeyes=1</code> is set, <code
class="command">yum</code> behaves in the same way that the command
line option <code class="option">-y</code> does.
+ </div></dd><dt class="varlistentry"><span
class="term">cachedir=<code
class="filename">/var/cache/yum/$basearch/$releasever</code></span></dt><dd><div
class="para">
+ This option specifies the directory where <span
class="application"><strong>Yum</strong></span> should
store its cache and database files. By default, <span
class="application"><strong>Yum</strong></span>'s cache
directory is <code
class="filename">/var/cache/yum/$basearch/$releasever</code>. See <a
class="xref" href="#sec-Using_Yum_Variables">Section 4.3.3, “Using
Yum Variables”</a> for descriptions of the <code
class="varname">$basearch</code> and <code
class="varname">$releasever</code> <span
class="application"><strong>Yum</strong></span> variables.
+ </div></dd><dt class="varlistentry"><span
class="term">debuglevel=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is an integer
between <code class="constant">1</code> and <code
class="constant">10</code>. Setting a higher <code
class="literal">debuglevel</code> value causes <code
class="command">yum</code> to display more detailed debugging output.
<code class="literal">debuglevel=0</code> disables debugging output,
while <code class="literal">debuglevel=2</code> is the default.
+ </div></dd><dt class="varlistentry"><span
class="term">exactarch=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Do not take into account
the exact architecture when updating packages.
+ </div><div class="para">
+ <code class="constant">1</code> — Consider the exact
architecture when updating packages. With this setting, <code
class="command">yum</code> will not install an i686 package to update
an i386 package already installed on the system. This is the default.
+ </div></dd><dt class="varlistentry"><span
class="term">exclude=<em
class="replaceable"><code>package_name</code></em> [<span
class="optional"><em
class="replaceable"><code>more_package_names</code></em></span>]</span></dt><dd><div
class="para">
+ This option allows you to exclude packages by keyword during installation/updates.
Listing multiple packages for exclusion can be accomplished by quoting a space-delimited
list of packages. Shell globs using wildcards (for example, <code
class="literal">*</code> and <code
class="literal">?</code>) are allowed.
+ </div></dd><dt class="varlistentry"><span
class="term">gpgcheck=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable GPG
signature-checking on packages in all repositories, including local package installation.
+ </div><div class="para">
+ <code class="constant">1</code> — Enable GPG
signature-checking on all packages in all repositories, including local package
installation. <code class="literal">gpgcheck=1</code> is the
default, and thus all packages' signatures are checked.
+ </div><div class="para">
+ If this option is set in the <code
class="literal">[main]</code> section of the <code
class="filename">/etc/yum.conf</code> file, it sets the GPG-checking
rule for all repositories. However, you can also set <code
class="literal">gpgcheck=</code><em
class="replaceable"><code>value</code></em> for individual
repositories instead; i.e., you can enable GPG-checking on one repository while disabling
it on another. Setting <code class="literal">gpgcheck=<em
class="replaceable"><code>value</code></em></code>
for an individual repository in its corresponding <code
class="filename">.repo</code> file overrides the default if it is
present in <code class="filename">/etc/yum.conf</code>. Refer to
<a class="xref" href="#s1-check-rpm-sig">Section A.3, “Checking
a Package's Signature”</a> for further information on GPG signature-checking.
+ </div></dd><dt class="varlistentry"><span
class="term">groupremove_leaf_only=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — <code
class="command">yum</code> should <span
class="emphasis"><em>not</em></span> check the dependencies
of each package when removing a package group. With this setting, <code
class="command">yum</code> removes all packages in a package group,
regardless of whether those packages are required by other packages or groups. <code
class="literal">groupremove_leaf_only=0</code> is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — <code
class="command">yum</code> should check the dependencies of each
package when removing a package group, and remove only those packages which are not not
required by any other package or group.
+ </div><div class="para">
+ For more information on removing packages, refer to <a class="xref"
href="#important-Package_Group_Removal">Intelligent package group
removal</a>.
+ </div></dd><dt class="varlistentry"><span
class="term">installonlypkgs=<em
class="replaceable"><code>space</code></em> <em
class="replaceable"><code>separated</code></em> <em
class="replaceable"><code>list</code></em> <em
class="replaceable"><code>of</code></em> <em
class="replaceable"><code>packages</code></em></span></dt><dd><div
class="para">
+ Here you can provide a space-separated list of packages which <code
class="command">yum</code> can <span
class="emphasis"><em>install</em></span>, but will never
<span class="emphasis"><em>update</em></span>. Refer to
<code class="command">man yum.conf</code> for the list of packages
which are install-only by default. If you add the <code
class="literal">installonlypkgs</code> directive to <code
class="filename">/etc/yum.conf</code>, you should ensure that you list
<span class="emphasis"><em>all</em></span> of the
packages that should be install-only, including any of those listed under the <code
class="literal">installonlypkgs</code> section of <code
class="command">man yum.conf</code>. In particular, kernel packages
should always be listed in <code
class="literal">installonlypkgs</code> (as they are by default), and
<code class="literal">installonly_limit</code> should always be set
to a value greater than <code class="constant">2</code> so that a
backup kernel is a
lways available in case the default one fails to boot. Refer to <a
class="xref"
href="#varentry-installonly_limit_value">installonly_limit=<em
class="replaceable"><code>value</code></em></a> for
details on the <code class="literal">installonly_limit</code>
directive.
+ </div></dd><dt class="varlistentry"
id="varentry-installonly_limit_value"><span
class="term">installonly_limit=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is an integer
representing the maximum number of versions that can be installed simultaneously for any
single package listed in the <code
class="literal">installonlypkgs</code> directive. The defaults for the
<code class="literal">installonlypkgs</code> directive include
several different kernel packages, so be aware that changing the value of <code
class="literal">installonly_limit</code> will also affect the maximum
number of installed versions of any single kernel package. The default value listed in
<code class="filename">/etc/yum.conf</code> is <code
class="literal">installonly_limit=3</code>, and it is not recommended
to decrease this value, particularly below <code
class="constant">2</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">keepcache=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Do not retain the cache of
headers and packages after a successful installation. This is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — Retain the cache after a
successful installation.
+ </div></dd><dt class="varlistentry"><span
class="term">logfile=<code
class="filename">/var/log/yum.log</code></span></dt><dd><div
class="para">
+ This option specifies where <code class="command">yum</code>
should send its logging output. By default, <code
class="command">yum</code> logs to <code
class="filename">/var/log/yum.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">multilib_policy=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <strong
class="userinput"><code>best</code></strong> — install the
best-choice architecture for this system. For example, setting <code
class="literal">multilib_policy=best</code> on an AMD64 system causes
<code class="command">yum</code> to install 64-bit versions of all
packages.
+ </div><div class="para">
+ <strong
class="userinput"><code>all</code></strong> — always
install every possible architecture for every package. For example, with <code
class="literal">multilib_policy</code> set to <code
class="literal">all</code> on an AMD64 system, <code
class="command">yum</code> would install both the i686 and AMD64
versions of a package, if both were available.
+ </div></dd><dt class="varlistentry"><span
class="term">obsoletes=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable <code
class="command">yum</code>'s obsoletes processing logic when
performing updates.
+ </div><div class="para">
+ <code class="constant">1</code> — Enable <code
class="command">yum</code>'s obsoletes processing logic when
performing updates. When one package declares in its spec file that it <em
class="firstterm">obsoletes</em> another package, the latter package
will be replaced by the former package when the former package is installed. Obsoletes are
declared, for example, when a package is renamed. <code
class="literal">obsoletes=1</code> the default.
+ </div></dd><dt class="varlistentry"><span
class="term">plugins=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable all <span
class="application"><strong>Yum</strong></span> plugins
globally.
+ </div><div class="important"
id="important-Disabling_all_plugins_is_not_advised-main_options"><div
class="admonition_header"><h2>Disabling all plugins is not
advised</h2></div><div class="admonition"><div
class="para">
+ Disabling all plugins is not advised, because certain plugins provide important
<code class="command">Yum</code> services. Disabling plugins
globally is provided as a convenience option, and is generally only recommended when
diagnosing a potential problem with <code
class="command">Yum</code>.
+ </div></div></div><div class="para">
+ <code class="constant">1</code> — Enable all <span
class="application"><strong>Yum</strong></span> plugins
globally. With <code class="literal">plugins=1</code>, you can still
disable a specific <span
class="application"><strong>Yum</strong></span> plugin by
setting <code class="literal">enabled=0</code> in that plugin's
configuration file. Refer to <a class="xref"
href="#sec-Yum_Plugins">Section 4.4, “Yum Plugins”</a> for more
information about various <span
class="application"><strong>Yum</strong></span> plugins, or
to <a class="xref"
href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Section 4.4.1,
“Enabling, Configuring and Disabling Yum Plugins”</a> for further information on
controlling plugins.
+ </div></dd><dt class="varlistentry"><span
class="term">reposdir=<em
class="replaceable"><code>/absolute/path/to/directory/containing/repo/files</code></em></span></dt><dd><div
class="para">
+ This option allows you to specify a directory where <code
class="filename">.repo</code> files are located. All <code
class="filename">.repo</code> files contain repository information
(similar to the <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections of <code class="filename">/etc/yum.conf</code>). <code
class="command">yum</code> collects all repository information from
<code class="filename">.repo</code> files and the <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section of the <code class="filename">/etc/yum.conf</code> file to
create a master list of repositories to use for transactions. Refer to <a
class="xref" href="#sec-Setting_repository_Options">Section 4.3.2,
“Setting [repository] Options”</a> for more information about options you can use
for both the <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section and <code class="filename">.repo
</code> files. If <code class="literal">reposdir</code> is
not set, <code class="command">yum</code> uses the default directory
<code class="filename">/etc/yum.repos.d/</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">retries=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is an integer
<code class="constant">0</code> or greater. This value sets the
number of times <code class="command">yum</code> should attempt to
retrieve a file before returning an error. Setting this to <code
class="constant">0</code> makes <code
class="command">yum</code> retry forever. The default value is <code
class="constant">10</code>.
+ </div></dd></dl></div></div><div
class="section" id="sec-Setting_repository_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Setting_repository_Options">4.3.2. Setting [repository]
Options</h3></div></div></div><a id="id1371603"
class="indexterm"></a><div class="para">
+ The <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections (where <em
class="replaceable"><code>repository</code></em> is a
unique repository ID, such as <code
class="literal">my_personal_repo</code>) allow you to define individual
<span class="application"><strong>Yum</strong></span>
repositories. To define a new repository, either add this section to the <code
class="filename">/etc/yum.conf</code> file, or to a <code
class="filename">.repo</code> file in the <code
class="filename">/etc/yum.repos.d/</code> directory.
+ </div><div class="para">
+ All <code class="filename">.repo</code> files in <code
class="filename">/etc/yum.repos.d/</code>are read by <code
class="command">yum</code>, which allows you to create new, custom
<code class="filename">.repo</code> files in this directory. Best
practice is to define your repositories here instead of in <code
class="filename">/etc/yum.conf</code>.
+ </div><div class="para">
+ The following is a (bare-minimum) example of the form a <code
class="filename">.repo</code> file takes:
+ </div><pre class="screen">[repository_ID]
+name=A Repository Name
+baseurl=http://path/to/repo or ftp://path/to/repo or
file:///path/to/local/repo</pre><div class="para">
+ Every <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section must contain the following minimum directives:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">[<em
class="replaceable"><code>repository_ID</code></em>]</span></dt><dd><div
class="para">
+ The repository ID is a unique, one-word (no spaces; underscores are allowed)
string of characters (enclosed by brackets) that serves as a repository identifier.
+ </div></dd><dt class="varlistentry"><span
class="term">name=<em class="replaceable"><code>A
Repository Name</code></em></span></dt><dd><div
class="para">
+ This is a human-readable string describing the repository.
+ </div></dd><dt class="varlistentry"><span
class="term">baseurl=<em
class="replaceable"><code>http://path/to/repo, ftp://path/to/repo,
file:///path/to/local/repo</code></em></span></dt><dd><div
class="para">
+ This is a URL to the directory where the repodata directory of a repository is
located. Usually this URL is an HTTP link, such as:
+ </div><pre
class="screen">baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</pre><div
class="para">
+ Note that <span
class="application"><strong>Yum</strong></span> always
expands the <code class="varname">$releasever</code>, <code
class="varname">$arch</code> and <code
class="varname">$basearch</code> variables in URLs. See <a
class="xref" href="#sec-Using_Yum_Variables">Section 4.3.3, “Using
Yum Variables”</a> for explanations of all <span
class="application"><strong>Yum</strong></span> variables.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ If the repository is available over FTP, use: <code
class="literal">ftp://path/to/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If the repository is local to the machine, use <code
class="literal">file:///path/to/local/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If a specific online repository requires basic HTTP authentication, you can
specify your username and password in the <code
class="literal">http://path/to/repo</code> by prepending it as <code
class="command"><em
class="replaceable"><code>username</code></em>:<em
class="replaceable"><code>password</code></em>@<em
class="replaceable"><code>link</code></em></code>.
For example, if a repository on
http://www.example.com/repo/ requires a username of
<span class="quote">“<span
class="quote">user</span>”</span> and a password of <span
class="quote">“<span
class="quote">password</span>”</span>, then the <code
class="literal">baseurl</code> link could be specified as:
+ </div><pre class="screen">baseurl=http://<strong
class="userinput"><code>user</code></strong>:<strong
class="userinput"><code>password</code></strong>@www.example.com/repo/</pre></li></ul></div></dd></dl></div><div
class="para">
+ The following is another useful <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
directive:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">enabled=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — do not include this
repository as a package source when performing updates and installs. This is an easy way
of quickly turning repositories on and off, which is useful when you desire a single
package from a repository that you do not want to enable for updates or installs.
+ </div><div class="para">
+ <code class="constant">1</code> — include this repository as
a package source.
+ </div><div class="para">
+ Turning repositories on and off can also be performed by passing either the
<code class="option">--enablerepo=<em
class="replaceable"><code>repo_name</code></em></code>
or <code class="option">--disablerepo=<em
class="replaceable"><code>repo_name</code></em></code>
option to <code class="command">yum</code>, or through the <span
class="guilabel"><strong>Add/Remove
Software</strong></span> window of the <span
class="application"><strong>PackageKit</strong></span>
utility.
+ </div></dd></dl></div><div class="para">
+ Many more <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
options exist. Refer to the <code class="literal">[repository]
OPTIONS</code> section of <code class="command">man
yum.conf</code> for the exhaustive list and descriptions for each.
+ </div></div><div class="section"
id="sec-Using_Yum_Variables"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Using_Yum_Variables">4.3.3. Using Yum
Variables</h3></div></div></div><a id="id464308"
class="indexterm"></a><div class="para">
+ You can use and reference the following built-in variables in <code
class="command">yum</code> commands and in all <span
class="application"><strong>Yum</strong></span>
configuration files (that is, <code
class="filename">/etc/yum.conf</code> and all <code
class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code> directory):
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="varname">$releasever</code>
</span></dt><dd><div class="para">
+ You can use this variable to reference the release version of Fedora. <span
class="application"><strong>Yum</strong></span> obtains the
value of <code class="varname">$releasever</code> from the <code
class="literal">distroverpkg=<em
class="replaceable"><code>value</code></em></code>
line in the <code class="filename">/etc/yum.conf</code>
configuration file. If there is no such line in <code
class="filename">/etc/yum.conf</code>, then <code
class="command">yum</code> infers the correct value by deriving the
version number from the <span class="package">redhat-release</span>
package.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="varname">$arch</code>
</span></dt><dd><div class="para">
+ You can use this variable to refer to the system's CPU architecture as
returned when calling Python's <code
class="methodname">os.uname()</code> function. Valid values for
<code class="varname">$arch</code> include: <code
class="literal">i586</code>, <code
class="literal">i686</code>, and <code
class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="varname">$basearch</code>
</span></dt><dd><div class="para">
+ You can use <code class="varname">$basearch</code> to
reference the base architecture of the system. For example, i686 and i586 machines both
have a base architecture of <code class="literal">i386</code>, and
AMD64 and Intel 64 machines have a base architecture of <code
class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="varname">$uuid</code>
</span></dt><dd><div class="para">
+ You can use this variable to refer to a <em
class="firstterm">universally unique identifier</em> (UUID) for the
machine.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="varname">$YUM0-9</code>
</span></dt><dd><div class="para">
+ These ten variables are each replaced with the value of any shell environment
variables with the same name. If one of these variables is referenced (in <code
class="filename">/etc/yum.conf</code> for example) and a shell
environment variable with the same name does not exist, then the configuration file
variable is not replaced.
+ </div></dd></dl></div><div class="para">
+ To define a custom variable or to override the value of an existing one, create a
file with the same name as the variable (without the <span
class="quote">“<span class="quote"><code
class="literal">$</code></span>”</span> sign) in the
<code class="filename">/etc/yum/vars/</code> directory, and add the
desired value on its first line.
+ </div><div class="example"
id="exam-Using_Yum_Variables"><h6>Example 4.7. Using a custom <span
class="application">Yum</span> variable</h6><div
class="example-contents"><div class="para">
+ Repository descriptions often include the operating system name. To define a new
variable called <code class="varname">$osname</code>, create a new
file with <span class="quote">“<span
class="quote">Fedora</span>”</span> on the first line and save it
as <code class="filename">/etc/yum/vars/osname</code>. For example:
+ </div><pre class="screen">~]# <code
class="command">echo "Fedora" >
/etc/yum/vars/osname</code></pre><div class="para">
+ Instead of <span class="quote">“<span
class="quote">Fedora 15</span>”</span>, you can now use the
following in the <code class="filename">.repo</code> files:
+ </div><pre class="screen">name=$osname
$releasever</pre></div></div><br class="example-break"
/></div><div class="section"
id="sec-Creating_a_Yum_Repository"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Creating_a_Yum_Repository">4.3.4. Creating a Yum
Repository</h3></div></div></div><a id="id676065"
class="indexterm"></a><div class="para">
+ To set up a <span
class="application"><strong>Yum</strong></span> repository,
follow these steps:
+ </div><div class="procedure"
id="procedure-Setting_Up_a_Yum_repository"><ol
class="1"><li class="step"><div
class="para">
+ Install the <span class="package">createrepo</span> package:
+ </div><pre class="screen">~]# <code
class="command">yum install
createrepo</code></pre></li><li class="step"><div
class="para">
+ Copy all of the packages into one directory, such as <code
class="filename">/mnt/local_repo/</code>.
+ </div></li><li class="step"><div
class="para">
+ Run the <code class="command">createrepo --database</code>
command on that directory:
+ </div><pre class="screen">~]# <code
class="command">createrepo --database
/mnt/local_repo/</code></pre></li></ol></div><div
class="para">
+ This will create the necessary metadata for your <span
class="application"><strong>Yum</strong></span> 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"
id="sec-Yum_Plugins">4.4. Yum
Plugins</h2></div></div></div><a id="id801254"
class="indexterm"></a><div class="para">
+ <span
class="application"><strong>Yum</strong></span> provides
plugins that extend and enhance its operations. Certain plugins are installed by default.
<span class="application"><strong>Yum</strong></span>
always informs you which plugins, if any, are loaded and active whenever you call any
<code class="command">yum</code> command:
+ </div><pre class="screen">~]# <code
class="command">yum info yum</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre><div class="para">
+ Note that the plugin names which follow <code class="command">Loaded
plugins</code> are the names you can provide to the <code
class="option">--disableplugins=<em
class="replaceable"><code>plugin_name</code></em></code>
option.
+ </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"
id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Enabling,
Configuring and Disabling Yum Plugins</h3></div></div></div><a
id="id1292880" class="indexterm"></a><a
id="id682663" class="indexterm"></a><a
id="id682675" class="indexterm"></a><div
class="para">
+ To enable <span
class="application"><strong>Yum</strong></span> plugins,
ensure that a line beginning with <code
class="command">plugins=</code> is present in the <code
class="literal">[main]</code> section of <code
class="filename">/etc/yum.conf</code>, and that its value is set to
<code class="constant">1</code>:
+ </div><pre class="screen">plugins=1</pre><div
class="para">
+ You can disable all plugins by changing this line to <code
class="command">plugins=0</code>.
+ </div><div class="important"
id="important-Disabling_all_plugins_is_not_advised-plugins"><div
class="admonition_header"><h2>Disabling all plugins is not
advised</h2></div><div class="admonition"><div
class="para">
+ Disabling all plugins is not advised because certain plugins provide important
<code class="command">Yum</code> services. Disabling plugins
globally is provided as a convenience option, and is generally only recommended when
diagnosing a potential problem with <code
class="command">Yum</code>.
+ </div></div></div><div class="para">
+ Every installed plugin has its own configuration file in the <code
class="filename">/etc/yum/pluginconf.d/</code> directory. You can set
plugin-specific options in these files. For example, the following is the content of
<code class="filename">refresh-packagekit.conf</code>, the
configuration file for the <span
class="application"><strong>refresh-packagekit</strong></span>
plugin:
+ </div><pre class="screen">[main]
+enabled=1</pre><div class="para">
+ Plugin configuration files always contain a <code
class="literal">[main]</code> section (similar to <span
class="application"><strong>Yum</strong></span>'s
<code class="filename">/etc/yum.conf</code> file) in which there is
(or you can place if it is missing) an <code
class="literal">enabled=</code> option that controls whether the plugin
is enabled when you run <code class="command">yum</code> commands.
+ </div><div class="para">
+ If you disable all plugins by setting <code
class="command">enabled=0</code> in <code
class="filename">/etc/yum.conf</code>, then all plugins are disabled
regardless of whether they are enabled in their individual configuration files.
+ </div><div class="para">
+ If you merely want to disable all <span
class="application"><strong>Yum</strong></span> plugins for
a single <code class="command">yum</code> command, use the <code
class="option">--noplugins</code> option.
+ </div><div class="para">
+ If you want to disable one or more <span
class="application"><strong>Yum</strong></span> plugins for
a single <code class="command">yum</code> command, add the <code
class="option">--disableplugin=<em
class="replaceable"><code>plugin_name</code></em></code>
option to the command. For example, to disable the <span
class="application"><strong>presto</strong></span> plugin
while updating a system, type:
+ </div><pre class="screen">~]# <code
class="command">yum update
--disableplugin=presto</code></pre><div class="para">
+ The plugin names you provide to the <code
class="option">--disableplugin=</code> option are the same names listed
after the <code class="command">Loaded plugins</code> line in the
output of any <code class="command">yum</code> command. You can
disable multiple plugins by separating their names with commas. In addition, you can match
multiple plugin names or shorten long ones by using glob expressions:
+ </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"
id="sec-Installing_More_Yum_Plugins">4.4.2. Installing Additional Yum
Plugins</h3></div></div></div><div class="para">
+ <span
class="application"><strong>Yum</strong></span> plugins
usually adhere to the <code class="filename">yum-plugin-<em
class="replaceable"><code>plugin_name</code></em></code>
package-naming convention, but not always: the package which provides the <span
class="application"><strong>presto</strong></span> plugin
is named <code class="filename">yum-presto</code>, for example. You
can install a <span
class="application"><strong>Yum</strong></span> plugin in
the same way you install other packages. For instance, to install the <span
class="application"><strong>security</strong></span>
plugin, type the following at a shell prompt:
+ </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"
id="sec-Plugin_Descriptions">4.4.3. Plugin
Descriptions</h3></div></div></div><div
class="para">
+ The following are descriptions of a few commonly installed <span
class="application"><strong>Yum</strong></span> plugins:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id464029" class="indexterm"></a>
+ <span
class="application"><strong>presto</strong></span>
(<span class="package">yum-presto</span>)
</span></dt><dd><div class="para">
+ The <span
class="application"><strong>presto</strong></span> plugin
adds support to <span
class="application"><strong>Yum</strong></span> for
downloading <em class="firstterm">delta RPM</em> packages, during
updates, from repositories which have <span
class="application"><strong>presto</strong></span> metadata
enabled. Delta RPMs contain only the differences between the version of the package
installed on the client requesting the RPM package and the updated version in the
repository.
+ </div><div class="para">
+ Downloading a delta RPM is much quicker than downloading the entire updated
package, and can speed up updates considerably. Once the delta RPMs are downloaded, they
must be rebuilt to apply the difference to the currently-installed package and thus create
the full, updated package. This process takes CPU time on the installing machine. Using
delta RPMs is therefore a tradeoff between time-to-download, which depends on the network
connection, and time-to-rebuild, which is CPU-bound. Using the <span
class="application"><strong>presto</strong></span> plugin
is recommended for fast machines and systems with slower network connections, while slower
machines on very fast connections <span
class="emphasis"><em>may</em></span> benefit more from
downloading normal RPM packages, that is, by disabling <span
class="application"><strong>presto</strong></span>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id401346"
class="indexterm"></a>
+ <span
class="application"><strong>refresh-packagekit</strong></span>
(<span class="package">PackageKit-yum-plugin</span>)
</span></dt><dd><div class="para">
+ The <span
class="application"><strong>refresh-packagekit</strong></span>
plugin updates metadata for <span
class="application"><strong>PackageKit</strong></span>
whenever <code class="command">yum</code> is run. The <span
class="application"><strong>refresh-packagekit</strong></span>
plugin is installed by default.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id1451169"
class="indexterm"></a>
+ <span
class="application"><strong>rhnplugin</strong></span>
(<span class="package">yum-rhn-plugin</span>)
</span></dt><dd><div class="para">
+ The <span
class="application"><strong>rhnplugin</strong></span>
provides support for connecting to <code class="systemitem">RHN
Classic</code>. This allows systems registered with <code
class="systemitem">RHN Classic</code> to update and install packages
from this system.
+ </div><div class="para">
+ Refer to <code class="command">man rhnplugin</code> for more
information about the plugin.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id1310972"
class="indexterm"></a>
+ <span
class="application"><strong>security</strong></span>
(<span class="package">yum-plugin-security</span>)
</span></dt><dd><div class="para">
+ Discovering information about and applying security updates easily and often is
important to all system administrators. For this reason <span
class="application"><strong>Yum</strong></span> provides
the <span
class="application"><strong>security</strong></span>
plugin, which extends <code class="command">yum</code> with a set of
highly-useful security-related commands, subcommands and options.
+ </div><div class="para">
+ You can check for security-related updates as follows:
+ </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">[output
truncated]</span></em></pre><div class="para">
+ You can then use either <code class="command">yum update
--security</code> or <code class="command">yum update-minimal
--security</code> to update those packages which are affected by security
advisories. Both of these commands update all packages on the system for which a security
advisory has been issued. <code class="command">yum update-minimal
--security</code> updates them to the latest packages which were released as part of
a security advisory, while <code class="command">yum update
--security</code> will update all packages affected by a security advisory <span
class="emphasis"><em>to the latest version of that package
available</em></span>.
+ </div><div class="para">
+ In other words, if:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ the <span class="package">kernel-2.6.38.4-20</span>
package is installed on your system;
+ </div></li><li class="listitem"><div
class="para">
+ the <span class="package">kernel-2.6.38.6-22</span>
package was released as a security update;
+ </div></li><li class="listitem"><div
class="para">
+ then <span class="package">kernel-2.6.38.6-26</span> was
released as a bug fix update,
+ </div></li></ul></div><div class="para">
+ ...then <code class="command">yum update-minimal
--security</code> will update you to <span
class="package">kernel-2.6.38.6-22</span>, and <code
class="command">yum update --security</code> will update you to
<span class="package">kernel-2.6.38.6-26</span>. Conservative system
administrators may want to use <code
class="command">update-minimal</code> to reduce the risk incurred by
updating packages as much as possible.
+ </div><div class="para">
+ Refer to <code class="command">man yum-security</code> for
usage details and further explanation of the enhancements the <span
class="application"><strong>security</strong></span> plugin
adds to <code class="command">yum</code>.
+ </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"
id="sec-Additional_Resources">4.5. Additional
Resources</h2></div></div></div><a id="id460250"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl...
</span></dt><dd><div class="para">
+ The <code class="literal">Yum Guides</code> section of the
<span class="application"><strong>Yum</strong></span>
wiki contains more documentation.
+ </div></dd></dl></div></div></div><div
xml:lang="en-US" class="chapter" id="ch-PackageKit"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 5. PackageKit</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#sec-Updating_Packages_with_Software_Update">5.1. Updating Packages
with Software
Update</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Setting_preferences_for_checking_for_updates">5.1.1. Setting the
Update-Checking Interval</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_preferences_for_software_sources">5.1.2. Setting the
Software Sources</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Using_Add_Remove_Software">5.2.
Using Add/Remove
Software</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. Refreshing
Software Sources (Yum Repositories)</a></span></dt><dt><span
class="section"><a href="#sec-Finding_Pac
kages_with_Filters">5.2.2. Finding Packages with
Filters</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_and_Removing_Packages_and_Dependencies">5.2.3.
Installing and Removing Packages (and
Dependencies)</a></span></dt><dt><span
class="section"><a
href="#sec-Installing_and_Removing_Package_Groups">5.2.4. Installing and
Removing Package Groups</a></span></dt><dt><span
class="section"><a
href="#sec-Viewing_the_Transaction_Log">5.2.5. Viewing the Transaction
Log</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-PackageKit_Architecture">5.3.
PackageKit Architecture</a></span></dt><dt><span
class="section"><a
href="#ch-Graphical_Package_Management-sec-Additional_Resources">5.4.
Additional Resources</a></span></dt></dl></div><a
id="id421592" class="indexterm"></a><a
id="id822440" class="indexterm"></a><a
id="id389952" class="indexterm"></a><a
id="id797409" class="indexterm"></a><a
id="id575046" class="indexterm"></a><a
id="id550331" class="indexter
m"></a><a id="id840676"
class="indexterm"></a><a id="id1305403"
class="indexterm"></a><a id="id421297"
class="indexterm"></a><a id="id1002958"
class="indexterm"></a><a id="id431765"
class="indexterm"></a><div class="para">
+ Fedora provides <span
class="application"><strong>PackageKit</strong></span> for
viewing, managing, updating, installing and uninstalling packages compatible with your
system. <span
class="application"><strong>PackageKit</strong></span>
consists of several graphical interfaces that can be opened from the GNOME panel menu, or
from the Notification Area when <span
class="application"><strong>PackageKit</strong></span>
alerts you that updates are available. For more information on <span
class="application"><strong>PackageKit's</strong></span>
architecture and available front ends, refer to <a class="xref"
href="#sec-PackageKit_Architecture">Section 5.3, “PackageKit
Architecture”</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"
id="sec-Updating_Packages_with_Software_Update">5.1. Updating Packages with
Software Update</h2></div></div></div><a
id="id941150" class="indexterm"></a><a
id="id537141" class="indexterm"></a><div
class="para">
+ You can open <span class="application"><strong>Software
Updates</strong></span> by clicking <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>Software Update</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
running the <code class="command">gpk-update-viewer</code> command
at the shell prompt. In the <span class="guilabel"><strong>Software
Updates</strong></span> window, all available updates are listed along with
the names of the packages being updated (minus the <code
class="filename">.rpm</code> suffix, but including the CPU
architecture), a short summary of the package, and, usually, short descriptions of the
changes the update provides. Any updates you do not wish to install can be de-selected
here by unchecking the checkbox corresponding to the update.
+ </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="Installing updates with Software
Update" /><div class="longdesc"><div
class="para">
+ installing 56 updates with PackageKit's software update window
+ </div></div></div></div><h6>Figure 5.1. Installing
updates with Software Update</h6></div><br class="figure-break"
/><div class="para">
+ The updates presented in the <span
class="guilabel"><strong>Software Updates</strong></span>
window only represent the currently-installed packages on your system for which updates
are available;
+ <a id="id780194" class="indexterm"></a>
+ <a id="id780209" class="indexterm"></a>
+ dependencies of those packages, whether they are existing packages on your system or
new ones, are not shown until you click <span
class="guibutton"><strong>Install Updates</strong></span>.
+ </div><div class="para">
+ <span
class="application"><strong>PackageKit</strong></span>
<a id="id448294" class="indexterm"></a>
+ <a id="id448309" class="indexterm"></a>
+ <a id="id448321" class="indexterm"></a>
+ utilizes the fine-grained user authentication
+ <a id="id448329" class="indexterm"></a>
+ capabilities provided by the <span
class="application"><strong>PolicyKit</strong></span>
toolkit whenever you request it to make changes to the system. Whenever you instruct
<span
class="application"><strong>PackageKit</strong></span> to
update, install or remove packages, you will be prompted to enter the superuser password
before changes are made to the system.
+ </div><div class="para">
+ If you instruct <span
class="application"><strong>PackageKit</strong></span> to
update the <code class="filename">kernel</code> package, then it
will prompt you after installation, asking you whether you want to reboot the system and
thereby boot into the newly-installed kernel.
+ </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"
id="sec-Setting_preferences_for_checking_for_updates">5.1.1. Setting the
Update-Checking Interval</h3></div></div></div><a
id="id544253" class="indexterm"></a><div
class="para">
+ Selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>Other</strong></span> →
<span class="guimenuitem"><strong>Software
Updates</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu
opens the <span class="guilabel"><strong>Software Update
Preferences</strong></span> window. The <span
class="guilabel"><strong>Update Settings</strong></span>
tab allows you to define the interval at which <span
class="application"><strong>PackageKit</strong></span>
checks for package updates, as well as whether or not to automatically install all updates
or only security updates. Leaving the <span
class="guilabel"><strong>Check for updates when using mobile
broadband</strong></span> box unchecked is handy for avoiding extraneous
bandwidth usage when using a wireless connection on which you are charged for the amount
of data you download.
+ </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="Setting PackageKit's
update-checking interval" /><div class="longdesc"><div
class="para">
+ Setting the update-checking interval for PackageKit
+ </div></div></div></div><h6>Figure 5.2. Setting
PackageKit's update-checking interval</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"
id="sec-Setting_preferences_for_software_sources">5.1.2. Setting the Software
Sources</h3></div></div></div><div class="para">
+ To select which package repositories to use to install software updates, select
<span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>Other</strong></span> →
<span class="guimenuitem"><strong>Software
Updates</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu,
and click the <span class="guilabel"><strong>Software
Sources</strong></span> tab of the <span
class="guilabel"><strong>Software Update
Preferences</strong></span> window.
+ </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="Setting
PackageKit's software sources" /><div class="longdesc"><div
class="para">
+ Setting the software sources for PackageKit
+ </div></div></div></div><h6>Figure 5.3. Setting
PackageKit's software sources</h6></div><br
class="figure-break" /><a id="id888530"
class="indexterm"></a><a id="id487080"
class="indexterm"></a><div class="para">
+ <span
class="application"><strong>PackageKit</strong></span>
refers to <span
class="application"><strong>Yum</strong></span>
repositories as software sources. It obtains all packages from enabled software
sources.The <span class="guilabel"><strong>Software
Sources</strong></span> tab shows the repository name, as written on the
<code class="computeroutput">name=<em
class="replaceable"><code>My Repository
Name</code></em></code> field of all [<em
class="replaceable"><code>repository</code></em>] sections
in the <code class="filename">/etc/yum.conf</code> configuration
file, and in all <code class="filename"><em
class="replaceable"><code>repository</code></em>.repo</code>
files in the <code class="filename">/etc/yum.repos.d/</code>
directory.
+ </div><div class="para">
+ Entries which are checked in the <span
class="guilabel"><strong>Enabled</strong></span> column
indicate that the corresponding repository will be used to locate packages to satisfy all
update and installation requests (including dependency resolution). The <span
class="guilabel"><strong>Enabled</strong></span> column
corresponds to the <code class="computeroutput">enabled=<em
class="replaceable"><code><1 or
0></code></em></code> field in [<em
class="replaceable"><code>repository</code></em>] sections.
Checking an unchecked box enables the Yum repository, and unchecking it disables it.
Performing either function causes <span
class="application"><strong>PolicyKit</strong></span> to
prompt for superuser authentication to enable or disable the repository. <span
class="application"><strong>PackageKit</strong></span>
actually inserts the <code class="literal">enabled=<em
class="replaceable"><code><1 or
0></code></em></code> line into the correct [<em
class="replace
able"><code>repository</code></em>] section if it does not
exist, or changes the value if it does. This means that enabling or disabling a repository
through the <span class="guilabel"><strong>Software
Sources</strong></span> window causes that change to persist after closing the
window or rebooting the system. The ability to quickly enable and disable repositories
based on our needs is a highly-convenient feature of <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Note that it is not possible to add or remove <span
class="application"><strong>Yum</strong></span>
repositories through <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="note"
id="note-Showing_Source_RPM_and_Test_Repositories"><div
class="admonition_header"><h2>Showing source RPM, test, and debuginfo
repositories</h2></div><div class="admonition"><div
class="para">
+ Checking the box at the bottom of the <span
class="guilabel"><strong>Software Sources</strong></span>
tab causes <span
class="application"><strong>PackageKit</strong></span> to
display source RPM, testing and debuginfo repositories as well. This box is unchecked by
default.
+ </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"
id="sec-Using_Add_Remove_Software">5.2. Using Add/Remove
Software</h2></div></div></div><a id="id818085"
class="indexterm"></a><a id="id818097"
class="indexterm"></a><div class="para">
+ <span
class="application"><strong>PackageKit</strong></span>'s
<span class="application"><strong>Software
Update</strong></span> GUI window is a separate application from its <span
class="guilabel"><strong>Add/Remove
Software</strong></span> application, although the two have intuitively
similar interfaces. To find and install a new package, select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>Add/Remove
Software</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
run the <code class="command">gpk-application</code> command at the
shell prompt.
+ </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's Add/Remove
Software window" /><div class="longdesc"><div
class="para">
+ Viewing PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>Figure 5.4. PackageKit's
Add/Remove Software window</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"
id="sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. Refreshing
Software Sources (Yum Repositories)</h3></div></div></div><div
class="para">
+ To enable or disable a <span
class="application"><strong>Yum</strong></span> repository,
open a dialog box by sclicking <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software
Sources</strong></span>, and select the <span
class="guilabel"><strong>Software Sources</strong></span>
tab. Refer to <a class="xref"
href="#sec-Setting_preferences_for_software_sources">Section 5.1.2, “Setting
the Software Sources”</a> for more information on available configuration options.
+ </div><div class="para">
+ After enabling and/or disabling the correct <span
class="application"><strong>Yum</strong></span>
repositories, make sure that you have the latest list of available packages. Click on
<span class="guimenu"><strong>System</strong></span> →
<span class="guimenuitem"><strong>Refresh Package
Lists</strong></span> and <span
class="application"><strong>PackageKit</strong></span> will
obtain the latest lists of packages from all enabled software sources, that is, <span
class="application"><strong>Yum</strong></span>
repositories.
+ </div></div><div class="section"
id="sec-Finding_Packages_with_Filters"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Finding_Packages_with_Filters">5.2.2. Finding Packages with
Filters</h3></div></div></div><a id="id637648"
class="indexterm"></a><div class="para">
+ You can view the list of all <span
class="emphasis"><em>configured</em></span> and unfiltered
(see below) <span
class="application"><strong>Yum</strong></span>
repositories by opening <span class="guilabel"><strong>Add/Remove
Software</strong></span> and clicking <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software
Sources</strong></span>. Once the software sources have been updated, it is
often beneficial to apply some filters so that <span
class="application"><strong>PackageKit</strong></span>
retrieves the results of our <span
class="guilabel"><strong>Find</strong></span> queries
faster. This is especially helpful when performing many package searches. Four of the
filters in the <span
class="guimenu"><strong>Filters</strong></span> drop-down
menu are used to split results by matching or not matching a single criterion. By default
when <span
class="application"><strong>PackageKit</strong></span>
starts, these filters are a
ll unapplied (<span class="guibutton"><strong>No
Filter</strong></span>), but once you do filter by one of them, that filter
remains set until you either change it or close <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Because you are usually searching for available packages that are <span
class="emphasis"><em>not</em></span> installed on the
system, click <span
class="guimenu"><strong>Filters</strong></span> → <span
class="guimenuitem"><strong>Installed</strong></span> and
select the <span class="guimenuitem"><strong>Only
Available</strong></span> radio button.
+ <a id="id509708" class="indexterm"></a>
+ <a id="id509724" class="indexterm"></a>
+ <a id="id509736" class="indexterm"></a>
+ <a id="id509751" class="indexterm"></a>
+ <a id="id620464" 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="Filtering out
already-installed packages" /><div class="longdesc"><div
class="para">
+ filtering out packages which are already installed
+ </div></div></div></div><h6>Figure 5.5. Filtering out
already-installed packages</h6></div><br class="figure-break"
/><div class="para">
+ <a id="id1454083" class="indexterm"></a>
+ <a id="id1454099" class="indexterm"></a>
+ <a id="id1454114" class="indexterm"></a>
+ Also, unless we require development files such as C header files, we can filter for
<span class="guimenu"><strong>Only End User
Files</strong></span> and, in doing so, filter out all of the <code
class="filename"><em
class="replaceable"><code>package_name</code></em>-devel</code>
packages we are not interested in.
+ </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="Filtering out
development packages from the list of Find results" /><div
class="longdesc"><div class="para">
+ filtering out development packages from our results
+ </div></div></div></div><h6>Figure 5.6. Filtering out
development packages from the list of Find results</h6></div><br
class="figure-break" /><div class="para">
+ The two remaining filters with submenus are:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <span
class="guisubmenu"><strong>Graphical</strong></span> <a
id="id479963" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Narrows the search to either applications which provide a GUI interface (<span
class="guibutton"><strong>Only Graphical</strong></span>)
or those that do not. This filter is useful when browsing for GUI applications that
perform a specific function.
+ </div></dd><dt class="varlistentry"><span
class="term"> <span
class="guisubmenu"><strong>Free</strong></span> <a
id="id661092" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Search for packages which are considered to be free software Refer to the <a
href="https://fedoraproject.org/wiki/Licensing#SoftwareLicenses"...
Licensing List</a> for details on approved licenses.
+ </div></dd></dl></div><div class="para">
+ The remaining checkbox filters are always either checked or unchecked. They are:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <span
class="guimenuitem"><strong>Hide
Subpackages</strong></span> </span></dt><dd><div
class="para">
+ Checking the <span class="guimenuitem"><strong>Hide
Subpackages</strong></span> <a id="id1292552"
class="indexterm"></a>
+ checkbox filters out generally-uninteresting packages that are typically only
dependencies of other packages that we want. For example, checking <span
class="guimenuitem"><strong>Hide
Subpackages</strong></span> and searching for <code
class="filename"><em
class="replaceable"><code>package</code></em> </code>
would cause the following related packages to be filtered out of the <span
class="guibutton"><strong>Find</strong></span> results (if
it exists):
+ </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>Only Newest
Packages</strong></span> </span></dt><dd><div
class="para">
+ Checking <span class="guimenuitem"><strong>Only Newest
Packages</strong></span> <a id="id697911"
class="indexterm"></a>
+ filters out all older versions of the same package from the list of results,
which is generally what we want.
+ </div><div class="important"
id="important-Using_the_Only_newest_items_filter"><div
class="admonition_header"><h2>Using the Only Newest Packages
filter</h2></div><div class="admonition"><div
class="para">
+ Checking <span class="guimenuitem"><strong>Only Newest
Packages</strong></span> filters out all but the most recent version of any
package from the results list. This filter is often combined with the <span
class="guimenuitem"><strong>Only Available</strong></span>
filter to search for the latest available versions of new (not installed) packages.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term">Only native
packages</span></dt><dd><div class="para">
+ Checking the <span class="guimenuitem"><strong>Only Native
Packages</strong></span> <a id="id698777"
class="indexterm"></a>
+ box on a multilib system causes <span
class="application"><strong>PackageKit</strong></span> to
omit listing results for packages compiled for the architecture that runs in <span
class="emphasis"><em>compatibility mode</em></span>. For
example, enabling this filter on a 64-bit system with an AMD64 CPU would cause all
packages built for the 32-bit x86 CPU architecture not to be shown in the list of results,
even though those packages are able to run on an AMD64 machine. Packages which are
architecture-agnostic (i.e. <em class="firstterm">noarch</em>
packages such as <code
class="filename">crontabs-1.10-32.1.el6.noarch.rpm</code>) are never
filtered out by checking <span class="guimenuitem"><strong>Only
Native Packages</strong></span>. This filter has no affect on non-multilib
systems, such as x86 machines.
+ </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"
id="sec-Installing_and_Removing_Packages_and_Dependencies">5.2.3. Installing
and Removing Packages (and
Dependencies)</h3></div></div></div><a id="id1278622"
class="indexterm"></a><a id="id1278633"
class="indexterm"></a><div class="para">
+ With the two filters selected, <span
class="guibutton"><strong>Only Available</strong></span>
and <span class="guibutton"><strong>Only End User
Files</strong></span>, search for the <span
class="application"><strong>htop</strong></span>
interactive process viewer and highlight the package. You now have access to some very
useful information about it, including: a clickable link to the project homepage; the
<span class="application"><strong>Yum</strong></span>
package group it is found in, if any; the license of the package; a pointer to the GNOME
menu location from where the application can be opened, if applicable; and the size of the
package, which is relevant when we download and install it.
+ </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="Viewing and installing a
package with PackageKit's Add/Remove Software window" /><div
class="longdesc"><div class="para">
+ Viewing and installing a package with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>Figure 5.7. Viewing and
installing a package with PackageKit's Add/Remove Software
window</h6></div><br class="figure-break" /><div
class="para">
+ When the checkbox next to a package or group is checked, then that item is already
installed on the system. Checking an unchecked box causes it to be <span
class="emphasis"><em>marked</em></span> for installation,
which only occurs when the <span
class="guibutton"><strong>Apply</strong></span> button is
clicked. In this way, you can search for and select multiple packages or package groups
before performing the actual installation transactions. Additionally, you can remove
installed packages by unchecking the checked box, and the removal will occur along with
any pending installations when <span
class="guibutton"><strong>Apply</strong></span> is pressed.
Dependency resolution
+ <a id="id730025" class="indexterm"></a>
+ , which may add additional packages to be installed or removed, is performed after
pressing <span
class="guibutton"><strong>Apply</strong></span>. <span
class="application"><strong>PackageKit</strong></span> will
then display a window listing those additional packages to install or remove, and ask for
confirmation to proceed.
+ </div><div class="para">
+ Check <span
class="application"><strong>htop</strong></span> and click
the <span
class="guibutton"><strong>Apply</strong></span> button. You
will then be prompted for the superuser password; enter it, and <span
class="application"><strong>PackageKit</strong></span> will
install <span
class="application"><strong>htop</strong></span>. One nice
feature of <span
class="application"><strong>PackageKit</strong></span> is
that, following installation, it sometimes presents you with a list of your
newly-installed applications and offer you the choice of running them immediately.
Alternatively, you will remember that finding a package and selecting it in the <span
class="guilabel"><strong>Add/Remove
Software</strong></span> window shows you the <span
class="guilabel"><strong>Location</strong></span> of where
in the GNOME menus its application shortcut is located, which is helpful when you want to
run it.
+ </div><div class="para">
+ Once it is installed, you can run <code
class="command">htop</code>, a colorful and enhanced version of the
<code class="command">top</code> process viewer, by opening a shell
prompt and entering:
+ </div><pre class="screen"><code
class="command">htop</code></pre><div
class="para">
+ <span
class="application"><strong>htop</strong></span> is nifty,
but we decide that <code class="command">top</code> is good enough
for us and we want to uninstall it. Remembering that we need to change the <span
class="guibutton"><strong>Only Available</strong></span>
filter we recently used to install it to <span
class="guibutton"><strong>Only Installed</strong></span> in
<span class="guimenu"><strong>Filters</strong></span> →
<span
class="guimenuitem"><strong>Installed</strong></span>, we
search for <span
class="application"><strong>htop</strong></span> again and
uncheck it. The program did not install any dependencies of its own; if it had, those
would be automatically removed as well, as long as they were not also dependencies of any
other packages still installed on our system.
+ </div><div class="warning"
id="warning-PackageKit-Removing_a_Package_Without_Removing_Packages_Depending_on_It"><div
class="admonition_header"><h2>Removing a package when other packages
depend on it</h2></div><div class="admonition"><div
class="para">
+ Although <span
class="application"><strong>PackageKit</strong></span>
automatically resolves dependencies during package installation and removal, it is unable
to remove a package without also removing packages which depend on it. This type of
operation can only be performed by <span
class="application"><strong>RPM</strong></span>, is not
advised, and can potentially leave your system in a non-functioning state or cause
applications to misbehave and/or crash.
+ </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="Removing a package with
PackageKit's Add/Remove Software window" /><div
class="longdesc"><div class="para">
+ Removing the htop package with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>Figure 5.8. Removing a
package with PackageKit's Add/Remove Software window</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"
id="sec-Installing_and_Removing_Package_Groups">5.2.4. Installing and
Removing Package Groups</h3></div></div></div><a
id="id603830" class="indexterm"></a><a
id="id894495" class="indexterm"></a><a
id="id894507" class="indexterm"></a><a
id="id894518" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>PackageKit</strong></span> also
has the ability to install <span
class="application"><strong>Yum</strong></span> package
groups, which it calls <span class="guilabel"><strong>Package
collections</strong></span>. Clicking on <span
class="guilabel"><strong>Package
collections</strong></span> in the top-left list of categories in the <span
class="guilabel"><strong>Software Updates</strong></span>
window allows us to scroll through and find the package group we want to install. In this
case, we want to install Czech language support (the <span
class="guilabel"><strong>Czech Support</strong></span>
group). Checking the box and clicking <span
class="guibutton"><strong>Apply</strong></span> informs us
how many <span
class="emphasis"><em>additional</em></span> packages must
be installed in order to fulfill the dependencies of the package group.
+ </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="Installing the
Czech Support package group" /><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>Figure 5.9. Installing
the Czech Support package group</h6></div><br
class="figure-break" /><div class="para">
+ Similarly, installed package groups can be uninstalled by selecting <span
class="guilabel"><strong>Package
collections</strong></span>, unchecking the appropriate checkbox, and
applying.
+ </div></div><div class="section"
id="sec-Viewing_the_Transaction_Log"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Viewing_the_Transaction_Log">5.2.5. Viewing the Transaction
Log</h3></div></div></div><div class="para">
+ <span
class="application"><strong>PackageKit</strong></span>
maintains a log of the transactions
+ <a id="id1307257" class="indexterm"></a>
+ <a id="id715512" class="indexterm"></a>
+ that it performs. To view the log, from the <span
class="guilabel"><strong>Add/Remove
Software</strong></span> window, click <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software Log</strong></span>,
or run the <code class="command">gpk-log</code> command at the shell
prompt.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Software Log
Viewer</strong></span> shows the <span
class="guilabel"><strong>Action</strong></span>, such as
<code class="literal">Updated Packages</code> or <code
class="literal">Installed Packages</code>, the <span
class="guilabel"><strong>Date</strong></span> on which that
action was performed, the <span
class="guilabel"><strong>Username</strong></span> of the
user who performed the action, and the front end <span
class="guilabel"><strong>Application</strong></span> the
user used (such as <code class="literal">Add/Remove Software</code>,
or <code class="literal">Update System</code>). The <span
class="guilabel"><strong>Details</strong></span> column
provides the types of the transactions, such as <code
class="literal">Updated</code>, <code
class="literal">Installed</code>, or <code
class="literal">Removed</code>, as well as the list of packages the
transactions were performed on.
+ </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="Viewing the log of package
management transactions with the Software Log Viewer" /><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>Figure 5.10. Viewing the
log of package management transactions with the Software Log
Viewer</h6></div><br class="figure-break" /><div
class="para">
+ Typing the name of a package in the top text entry field filters the list of
transactions to those which affected that package.
+ </div></div></div><div class="section"
id="sec-PackageKit_Architecture"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-PackageKit_Architecture">5.3. PackageKit
Architecture</h2></div></div></div><a id="id555679"
class="indexterm"></a><div class="para">
+ Fedora provides the <span
class="application"><strong>PackageKit</strong></span>
suite of applications for viewing, updating, installing and uninstalling packages and
package groups compatible with your system. Architecturally, <span
class="application"><strong>PackageKit</strong></span>
consists of several graphical front ends that communicate with the <code
class="command">packagekitd</code> daemon back end, which communicates
with a package manager-specific back end that utilizes <span
class="application"><strong>Yum</strong></span> to perform
the actual transactions, such as installing and removing packages, etc.
+ </div><div class="para">
+ <a class="xref"
href="#table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands">Table 5.1,
“PackageKit GUI windows, menu locations, and shell prompt commands”</a> shows the
name of the GUI window, how to start the window from the GNOME desktop or from the
<span class="guilabel"><strong>Add/Remove
Software</strong></span> window, and the name of the command line application
that opens that window.
+ </div><div class="table"
id="table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands"><h6>Table 5.1. PackageKit
GUI windows, menu locations, and shell prompt commands</h6><div
class="table-contents"><table summary="PackageKit GUI windows, menu
locations, and shell prompt commands" 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 align="left">
+ Window Title
+ </th><th align="left">
+ Function
+ </th><th align="left">
+ How to Open
+ </th><th align="left">
+ Shell Command
+ </th></tr></thead><tbody><tr><td
align="left">
+ Add/Remove Software
+ </td><td align="left">
+ Install, remove or view package info
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Administration</strong></span>
→ <span class="guimenuitem"><strong>Add/Remove
Software</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-application
+ </td></tr><tr><td align="left">
+ Software Update
+ </td><td align="left">
+ Perform package updates
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Administration</strong></span>
→ <span class="guimenuitem"><strong>Software
Update</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-update-viewer
+ </td></tr><tr><td align="left">
+ Software Sources
+ </td><td align="left">
+ Enable and disable <span
class="application"><strong>Yum</strong></span>
repositories
+ </td><td align="left">
+ <div class="para">
+ From <span class="guilabel"><strong>Add/Remove
Software</strong></span>: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software
Sources</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-repo
+ </td></tr><tr><td align="left">
+ Software Log Viewer
+ </td><td align="left">
+ View the transaction log
+ </td><td align="left">
+ <div class="para">
+ From <span class="guilabel"><strong>Add/Remove
Software</strong></span>: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software Log</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-log
+ </td></tr><tr><td align="left">
+ Software Update Preferences
+ </td><td align="left">
+ Set <span
class="application"><strong>PackageKit</strong></span>
preferences
+ </td><td align="left">
+ </td><td align="left">
+ gpk-prefs
+ </td></tr><tr><td align="left">
+ (Notification Area Alert)
+ </td><td align="left">
+ Alerts you when updates are available
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Preferences</strong></span> →
<span class="guimenuitem"><strong>Startup
Applications</strong></span>, <span
class="guilabel"><strong>Startup Programs</strong></span>
tab
+ </div>
+
+ </td><td align="left">
+ gpk-update-icon
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The <code class="command">packagekitd</code> daemon runs outside
the user session and communicates with the various graphical front ends. The <code
class="command">packagekitd</code> daemon<sup>[<a
id="footnote-Daemons" href="#ftn.footnote-Daemons"
class="footnote">1</a>]</sup> communicates via the <span
class="application"><strong>DBus</strong></span> system
message bus with another back end, which utilizes <span
class="application"><strong>Yum</strong></span>'s
Python API to perform queries and make changes to the system. On Linux systems other than
Red Hat Enterprise Linux and Fedora, <code
class="command">packagekitd</code> can communicate with other back ends
that are able to utilize the native package manager for that system. This modular
architecture provides the abstraction necessary for the graphical interfaces to work with
many different package managers to perform essentially the same types of package
management tasks. Learning how to use the <span class="appli
cation"><strong>PackageKit</strong></span> front ends means
that you can use the same familiar graphical interface across many different Linux
distributions, even when they utilize a native package manager other than <span
class="application"><strong>Yum</strong></span>.
+ </div><div class="para">
+ In addition, <span
class="application"><strong>PackageKit</strong></span>'s
separation of concerns provides reliability in that a crash of one of the GUI windows—or
even the user's X Window session—will not affect any package management tasks being
supervised by the <code class="command">packagekitd</code> daemon,
which runs outside of the user session.
+ </div><div class="para">
+ All of the front end graphical applications discussed in this chapter are provided by
the <code class="filename">gnome-packagekit</code> package instead
of by <span
class="application"><strong>PackageKit</strong></span> and
its dependencies. Users working in a KDE environment may prefer to install the <code
class="filename">kpackagekit</code> package, which provides a KDE
interface for <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Finally, <span
class="application"><strong>PackageKit</strong></span> also
comes with a console-based front end called <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"
id="ch-Graphical_Package_Management-sec-Additional_Resources">5.4. Additional
Resources</h2></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <span
class="application"><strong>PackageKit</strong></span> home
page — <a
href="http://www.packagekit.org/index.html">http://www.packa...
</span></dt><dd><div class="para">
+ Information about and mailing lists for <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.pack...
</span></dt><dd><div class="para">
+ An informative list of Frequently Asked Questions for the <span
class="application"><strong>PackageKit</strong></span>
software suite.
+ </div></dd><dt class="varlistentry"><span
class="term"> <span
class="application"><strong>PackageKit</strong></span>
Feature Matrix — <a
href="http://www.packagekit.org/pk-matrix.html">http://www.p...
</span></dt><dd><div class="para">
+ Cross-reference <span
class="application"><strong>PackageKit</strong></span>-provided
features with the long list of package manager back ends.
+ </div></dd></dl></div></div><div
class="footnotes"><br /><hr width="100"
align="left" /><div class="footnote"
id="footnote-Daemons"><div class="para"><sup>[<a
id="ftn.footnote-Daemons" href="#footnote-Daemons"
class="para">1</a>] </sup>
+ System daemons are typically long-running processes that provide services to the user
or to other programs, and which are started, often at boot time. Daemons respond to the
<code class="command">systemctl</code> command and can be turned on
or off permanently by using the <code class="command">systemctl
enable</code> or <code class="command">systemctl
disable</code>commands. They can typically be recognized by a <span
class="quote">“<span class="quote"><span
class="emphasis"><em>d</em></span></span>”</span>
appended to their name, such as the <code
class="command">packagekitd</code> daemon. Refer to <a
class="xref" href="#ch-Services_and_Daemons">Chapter 7,
<em>Services and Daemons</em></a> for information about system
services.
+ </div></div></div></div></div><div
class="part" id="part-Networking"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part III. Networking</h1></div></div></div><div
class="partintro" id="id481659"><div></div><div
class="para">
+ This part describes how to configure the network on Fedora.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a href="#ch-Network_Interfaces">6. Network
Interfaces</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-networkscripts-files">6.1.
Network Configuration Files</a></span></dt><dt><span
class="section"><a href="#s1-networkscripts-interfaces">6.2.
Interface Configuration
Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-eth0">6.2.1. Ethernet
Interfaces</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-chan">6.2.2. Channel Bonding
Interfaces</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-alias">6.2.3. Alias and Clone
Files</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-ppp0">6.2.4. Dialup
Interfaces</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-other">6.2.5. Other
Interfaces</a></span></dt></dl></dd>
<dt><span class="section"><a
href="#s1-networkscripts-control">6.3. Interface Control
Scripts</a></span></dt><dt><span
class="section"><a
href="#s1-networkscripts-static-routes">6.4. Configuring Static
Routes</a></span></dt><dt><span
class="section"><a href="#s1-networkscripts-functions">6.5.
Network Function Files</a></span></dt><dt><span
class="section"><a href="#s1-networkscripts-resources">6.6.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-networkscripts-docs-inst">6.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd></dl></div></div><div
xml:lang="en-US" class="chapter" id="ch-Network_Interfaces"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 6. Network
Interfaces</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-networkscripts-files">6.1. Network Configuration
Files</a></span></dt><dt><span
class="section"><a href="#s1-networkscripts-interfaces">6.2.
Interface C
onfiguration
Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-eth0">6.2.1. Ethernet
Interfaces</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-chan">6.2.2. Channel Bonding
Interfaces</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-alias">6.2.3. Alias and Clone
Files</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-ppp0">6.2.4. Dialup
Interfaces</a></span></dt><dt><span
class="section"><a
href="#s2-networkscripts-interfaces-other">6.2.5. Other
Interfaces</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-networkscripts-control">6.3.
Interface Control Scripts</a></span></dt><dt><span
class="section"><a
href="#s1-networkscripts-static-routes">6.4. Configuring Static
Routes</a></span></dt><dt><span
class="section"><a href="#s1-networkscripts-functions">6.5.
Network Function Files</a></span></dt><dt><span
class="section"><a href=
"#s1-networkscripts-resources">6.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-networkscripts-docs-inst">6.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id947926" class="indexterm"></a><a
id="id1250325" class="indexterm"></a><div
class="para">
+ Under Fedora, all network communications occur between configured software <em
class="firstterm">interfaces</em> and <em
class="firstterm">physical networking devices</em> connected to the
system.
+ </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">Interface configuration files</em>
+ </div></li><li class="listitem"><div
class="para">
+ <em class="firstterm">Interface control scripts</em>
+ </div></li><li class="listitem"><div
class="para">
+ <em class="firstterm">Network function files</em>
+ </div></li></ol></div><div class="para">
+ The files in each of these categories work together to enable various network devices.
+ </div><div class="para">
+ This chapter explores the relationship between these files and how they are used.
+ </div><div class="section"
id="s1-networkscripts-files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-files">6.1. Network Configuration
Files</h2></div></div></div><a id="id572426"
class="indexterm"></a><div class="para">
+ Before delving into the interface configuration files, let us first itemize the
primary configuration files used in network configuration. Understanding the role these
files play in setting up the network stack can be helpful when customizing a Fedora
system.
+ </div><div class="para">
+ The primary network configuration files are as follows:
+ </div><div class="variablelist"><dl><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="command">127.0.0.1</code>) as <code
class="command">localhost.localdomain</code>. For more information,
refer to the <code class="filename">hosts</code> man 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 <code
class="filename">resolv.conf</code> man page.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="filename">/etc/sysconfig/network</code>
</span></dt><dd><div class="para">
+ 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">Section B.1.13, “
/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">
+ For each network interface, there is a corresponding interface configuration
script. Each of these files provide information specific to a particular network
interface. Refer to <a class="xref"
href="#s1-networkscripts-interfaces">Section 6.2, “Interface Configuration
Files”</a> for more information on this type of file and the directives it accepts.
+ </div></dd></dl></div><div
class="warning"><div
class="admonition_header"><h2>Warning</h2></div><div
class="admonition"><div class="para">
+ The <code class="filename">/etc/sysconfig/networking/</code>
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
<span class="bold bold"><strong>not</strong></span> be
edited manually. Using only one method for network configuration is strongly encouraged,
due to the risk of configuration deletion.
+ </div></div></div></div><div class="section"
id="s1-networkscripts-interfaces"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-interfaces">6.2. Interface Configuration
Files</h2></div></div></div><a id="id626737"
class="indexterm"></a><a id="id626750"
class="indexterm"></a><div class="para">
+ Interface configuration files control the software interfaces for individual network
devices. As the system boots, it uses these files to determine what interfaces to bring up
and how to configure them. These files are usually named <code
class="filename">ifcfg-<em
class="replaceable"><code>name</code></em> </code>,
where <em class="replaceable"><code>name</code></em>
refers to the name of the device that the configuration file controls.
+ </div><div class="section"
id="s2-networkscripts-interfaces-eth0"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-networkscripts-interfaces-eth0">6.2.1. Ethernet
Interfaces</h3></div></div></div><a id="id561170"
class="indexterm"></a><a id="id561188"
class="indexterm"></a><div class="para">
+ One of the most common interface files is <code
class="filename">ifcfg-eth0</code>, which controls the first Ethernet
<em class="firstterm">network interface card</em> or <em
class="firstterm">NIC</em> 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">
+ The following is a sample <code
class="filename">ifcfg-eth0</code> file for a system using a fixed IP
address:
+ </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">
+ The values required in an interface configuration file can change based on other
values. For example, the <code class="filename">ifcfg-eth0</code>
file for an interface using DHCP looks different because IP information is provided by the
DHCP server:
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ The <span class="application"><strong>Network Administration
Tool</strong></span> (<code
class="command">system-config-network</code>) is an easy way to make
changes to the various network interface configuration files.
+ </div><div class="para">
+ However, it is also possible to manually edit the configuration files for a given
network interface.
+ </div><div class="para">
+ Below is a listing of the configurable parameters in an Ethernet interface
configuration file:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="command">BONDING_OPTS=<em
class="replaceable"><code>parameters</code></em>
</code> </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">Section 6.2.2, “Channel Bonding
Interfaces”</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="command">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="command">BOOTPROTO=<em
class="replaceable"><code>protocol</code></em>
</code> </span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>protocol</code></em>
</code> is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">none</code> — No boot-time protocol
should be used.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">bootp</code> — The BOOTP protocol
should be used.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">dhcp</code> — The DHCP protocol
should be used.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">BROADCAST=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the broadcast address. This directive is deprecated, as the value is calculated
automatically with <code class="command">ifcalc</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">DEVICE=<em
class="replaceable"><code>name</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>name</code></em> </code> 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="command">DHCP_HOSTNAME</code>
</span></dt><dd><div class="para">
+ Use this option only if the DHCP server requires the client to specify a hostname
before receiving an IP address.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">DNS<em
class="replaceable"><code>{1,2}</code></em>=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is a name server address to be placed in <code
class="filename">/etc/resolv.conf</code> if the <code
class="command">PEERDNS</code> directive is set to <code
class="command">yes</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">ETHTOOL_OPTS=<em
class="replaceable"><code>options</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>options</code></em> </code>
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"><code
class="command">ETHTOOL_OPTS="autoneg off speed 100 duplex
full"</code></pre><div class="para">
+ Instead of a custom initscript, use <code
class="command">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="note"><div
class="admonition_header"><h2>Set "autoneg off" 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="command">autoneg off</code>
option. This needs to be stated first, as the option entries are order-dependent.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">GATEWAY=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <em
class="replaceable"><code>address</code></em> is the IP
address of the network router or gateway device (if any).
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">HWADDR=<em
class="replaceable"><code>MAC-address</code></em>
</code> </span></dt><dd><div class="para">
+ where <em
class="replaceable"><code>MAC-address</code></em> is the
hardware address of the Ethernet device in the form <em
class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em>.
This directive must be used in machines containing more than one NIC to ensure that the
interfaces are assigned the correct device names regardless of the configured load order
for each NIC's module. This directive should <span class="bold
bold"><strong>not</strong></span> be used in conjunction with
<code class="command">MACADDR</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">IPADDR=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the IP address.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">MACADDR=<em
class="replaceable"><code>MAC-address</code></em>
</code> </span></dt><dd><div class="para">
+ where <em
class="replaceable"><code>MAC-address</code></em> is the
hardware address of the Ethernet device in the form <em
class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em>.
This directive is used to assign a MAC address to an interface, overriding the one
assigned to the physical NIC. This directive should <span class="bold
bold"><strong>not</strong></span> be used in conjunction with
<code class="command">HWADDR</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">MASTER=<em
class="replaceable"><code>bond-interface</code></em>
</code> </span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>bond-interface</code></em>
</code> is the channel bonding interface to which the Ethernet interface is linked.
+ </div><div class="para">
+ This directive is used in conjunction with the <code
class="command">SLAVE</code> directive.
+ </div><div class="para">
+ Refer to <a class="xref"
href="#s2-networkscripts-interfaces-chan">Section 6.2.2, “Channel Bonding
Interfaces”</a> for more information about channel bonding interfaces.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">NETMASK=<em
class="replaceable"><code>mask</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>mask</code></em> </code> is
the netmask value.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">NETWORK=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the network address. This directive is deprecated, as the value is calculated
automatically with <code class="command">ifcalc</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">ONBOOT=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — This device should be
activated at boot-time.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — This device should not
be activated at boot-time.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">PEERDNS=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — Modify <code
class="filename">/etc/resolv.conf</code> if the DNS directive is set.
If using DHCP, then <code class="command">yes</code> is the
default.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — Do not modify <code
class="filename">/etc/resolv.conf</code>.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">SLAVE=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — This device is
controlled by the channel bonding interface specified in the <code
class="command">MASTER</code> directive.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — This device is <span
class="emphasis"><em>not</em></span> controlled by the
channel bonding interface specified in the <code
class="command">MASTER</code> directive.
+ </div></li></ul></div><div class="para">
+ This directive is used in conjunction with the <code
class="command">MASTER</code> directive.
+ </div><div class="para">
+ Refer to <a class="xref"
href="#s2-networkscripts-interfaces-chan">Section 6.2.2, “Channel Bonding
Interfaces”</a> for more about channel bonding interfaces.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">SRCADDR=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the specified source IP address for outgoing packets.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">USERCTL=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — Non-<code
class="systemitem">root</code> users are allowed to control this
device.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — Non-<code
class="systemitem">root</code> users are not allowed to control this
device.
+ </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"
id="s2-networkscripts-interfaces-chan">6.2.2. Channel Bonding
Interfaces</h3></div></div></div><a id="id630666"
class="indexterm"></a><a id="id676783"
class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind multiple network interfaces 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><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="command">DEVICE=</code> directive must be <code
class="command">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">
+ The following is a sample channel bonding configuration file:
+ </div><div class="example"
id="ex-Sample_ifcfg-bond0_interface_configuration_file"><h6>Example 6.1. Sample
ifcfg-bond0 interface configuration file</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>bonding parameters
separated by
spaces</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="command">MASTER=</code> and <code
class="command">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="filename">eth0</code> and <code
class="filename">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">
+ In this example, replace <em
class="replaceable"><code>N</code></em> with the numerical
value for the interface.
+ </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 <code class="systemitem">root</code> 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="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><div class="important"><div
class="admonition_header"><h2>Put all bonding module parameters in
ifcfg-bondN files</h2></div><div class="admonition"><div
class="para">
+ Parameters for the bonding kernel module must be specified as a space-separated list
in the <em class="parameter"><code>BONDING_OPTS="<em
class="replaceable"><code>bonding
parameters</code></em>"</code></em> directive in the
ifcfg-bond<em class="replaceable"><code>N</code></em>
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">Section 21.7.2, “Using Channel
Bonding”</a>.
+ </div></div></div></div><div class="section"
id="s2-networkscripts-interfaces-alias"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-networkscripts-interfaces-alias">6.2.3. Alias and Clone
Files</h3></div></div></div><a id="id440886"
class="indexterm"></a><a id="id440904"
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.
+ </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="computeroutput">DEVICE=eth0:0</code> and a static IP address of
10.0.0.2, 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="filename">eth0</code> is
bound to a dynamic IP address, but the same physical network card can receive requests via
the fixed, 10.0.0.2 IP address.
+ </div><div class="warning"><div
class="admonition_header"><h2>Caution</h2></div><div
class="admonition"><div class="para">
+ Alias interfaces do not support 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="filename">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="command">USERCTL</code> directive is <code
class="command">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="filename">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">
+ The easiest way to create alias and clone interface configuration files is to use the
graphical <span class="application"><strong>Network Administration
Tool</strong></span>.
+ </div></div><div class="section"
id="s2-networkscripts-interfaces-ppp0"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-networkscripts-interfaces-ppp0">6.2.4. Dialup
Interfaces</h3></div></div></div><a id="id451774"
class="indexterm"></a><div class="para">
+ If you are connecting to the Internet via a dialup connection, a configuration file
is necessary for the interface.
+ </div><div class="para">
+ PPP interface files are named using the following format:
+ <div class="variablelist"><dl><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">
+ where <em
class="replaceable"><code>X</code></em> is a unique number
corresponding to a specific interface.
+ </div></dd></dl></div>
+
+ </div><div class="para">
+ The PPP interface configuration file is created automatically when <code
class="command">wvdial</code>, the <span
class="application"><strong>Network Administration
Tool</strong></span> or <span
class="application"><strong>Kppp</strong></span> is used to
create a dialup account. It is also possible to create and edit this file manually.
+ </div><div class="para">
+ The following is a typical <code
class="filename">ifcfg-ppp0</code> file:
+ </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 (SLIP)</em>
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">
+ Other options that may be used in these files include:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="command">DEFROUTE=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — Set this interface as
the default route.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — Do not set this
interface as the default route.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">DEMAND=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — This interface allows
<code class="command">pppd</code> to initiate a connection when
someone attempts to use it.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — A connection must be
manually established for this interface.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">IDLETIMEOUT=<em
class="replaceable"><code>value</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>value</code></em> </code>
is the number of seconds of idle activity before the interface disconnects itself.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">INITSTRING=<em
class="replaceable"><code>string</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>string</code></em> </code>
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="command">LINESPEED=<em
class="replaceable"><code>value</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>value</code></em> </code>
is the baud rate of the device. Possible standard values include <code
class="command">57600</code>, <code
class="command">38400</code>, <code
class="command">19200</code>, and <code
class="command">9600</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">MODEMPORT=<em
class="replaceable"><code>device</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>device</code></em> </code>
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="command">MTU=<em
class="replaceable"><code>value</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>value</code></em> </code>
is the <em class="firstterm">Maximum Transfer Unit (MTU)</em>
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="command">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="command">NAME=<em
class="replaceable"><code>name</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>name</code></em> </code> is
the reference to the title given to a collection of dialup connection configurations.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">PAPNAME=<em
class="replaceable"><code>name</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>name</code></em> </code> is
the username given during the <em class="firstterm">Password
Authentication Protocol (PAP)</em> exchange that occurs to allow connections to a
remote system.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">PERSIST=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">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="command">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="command">REMIP=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the IP address of the remote system. This is usually left unspecified.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">WVDIALSECT=<em
class="replaceable"><code>name</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>name</code></em> </code>
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"
id="s2-networkscripts-interfaces-other">6.2.5. Other
Interfaces</h3></div></div></div><div
class="para">
+ Other common interface configuration files include the following:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="filename">ifcfg-lo</code>
</span></dt><dd><div class="para">
+ A local <em class="firstterm">loopback interface</em> is
often used in testing, as well as being used in a variety of applications that require an
IP address pointing back to the same system. Any data sent to the loopback device is
immediately returned to the host's network layer.
+ </div><div class="warning"><div
class="admonition_header"><h2>Do not manually edit the ifcfg-lo
script</h2></div><div class="admonition"><div
class="para">
+ The loopback interface script, <code
class="filename">/etc/sysconfig/network-scripts/ifcfg-lo</code>, should
never be edited manually. Doing so can prevent the system from operating correctly.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term"> <code
class="filename">ifcfg-irlan0</code>
</span></dt><dd><div class="para">
+ An <em class="firstterm">infrared interface</em> allows
information between devices, such as a laptop and a printer, to flow over an infrared
link. This works in a similar way to an Ethernet device except that it commonly occurs
over a peer-to-peer connection.
+ </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
(PLIP)</em> 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"
id="s1-networkscripts-control">6.3. Interface Control
Scripts</h2></div></div></div><a id="id480069"
class="indexterm"></a><a id="id480090"
class="indexterm"></a><a id="id480112"
class="indexterm"></a><a id="id555594"
class="indexterm"></a><div class="para">
+ The interface control scripts activate and deactivate system interfaces. There are two
primary interface control scripts that call on control scripts located in the <code
class="filename">/etc/sysconfig/network-scripts/</code> directory:
<code class="command">/sbin/ifdown</code> and <code
class="command">/sbin/ifup</code>.
+ </div><div class="para">
+ The <code class="filename">ifup</code> and <code
class="filename">ifdown</code> interface scripts are symbolic links to
scripts in the <code class="filename">/sbin/</code> directory. When
either of these scripts are called, they require the value of the interface to be
specified, such as:
+ </div><pre class="screen"><code
class="command">ifup eth0</code></pre><div
class="warning"><div class="admonition_header"><h2>Use
the ifup and ifdown interface scripts</h2></div><div
class="admonition"><div class="para">
+ The <code class="filename">ifup</code> and <code
class="filename">ifdown</code> interface scripts are the only scripts
that the user should use to bring up and take down network interfaces.
+ </div><div class="para">
+ The following scripts are described for reference purposes only.
+ </div></div></div><div class="para">
+ Two files used to perform a variety of network initialization tasks during the process
of bringing up a network interface are <code
class="filename">/etc/rc.d/init.d/functions</code> and <code
class="filename">/etc/sysconfig/network-scripts/network-functions</code>.
Refer to <a class="xref"
href="#s1-networkscripts-functions">Section 6.5, “Network Function
Files”</a> for more information.
+ </div><div class="para">
+ After verifying that an interface has been specified and that the user executing the
request is allowed to control the interface, the correct script brings the interface up or
down. The following are common interface control scripts found within the <code
class="filename">/etc/sysconfig/network-scripts/</code> directory:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="filename">ifup-aliases</code>
</span></dt><dd><div class="para">
+ Configures IP aliases from interface configuration files when more than one IP
address is associated with an interface.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-ippp</code>
and <code class="filename">ifdown-ippp</code>
</span></dt><dd><div class="para">
+ Brings ISDN interfaces up and down.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-ipv6</code>
and <code class="filename">ifdown-ipv6</code>
</span></dt><dd><div class="para">
+ Brings IPv6 interfaces up and down.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-plip</code>
</span></dt><dd><div class="para">
+ Brings up a PLIP interface.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-plusb</code>
</span></dt><dd><div class="para">
+ Brings up a USB interface for network connections.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-post</code>
and <code class="filename">ifdown-post</code>
</span></dt><dd><div class="para">
+ Contains commands to be executed after an interface is brought up or down.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-ppp</code>
and <code class="filename">ifdown-ppp</code>
</span></dt><dd><div class="para">
+ Brings a PPP interface up or down.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-routes</code>
</span></dt><dd><div class="para">
+ Adds static routes for a device as its interface is brought up.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifdown-sit</code>
and <code class="filename">ifup-sit</code>
</span></dt><dd><div class="para">
+ Contains function calls related to bringing up and down an IPv6 tunnel within an
IPv4 connection.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="filename">ifup-wireless</code>
</span></dt><dd><div class="para">
+ Brings up a wireless interface.
+ </div></dd></dl></div><div
class="warning"><div class="admonition_header"><h2>Be
careful when removing or modifying network scripts!</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 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">
+ Here, <em
class="replaceable"><code>action</code></em> can be either
<code class="command">start</code>, <code
class="command">stop</code>, or <code
class="command">restart</code>.
+ </div><div class="para">
+ To view a list of configured devices and currently active network interfaces, use the
following command:
+ </div><pre class="screen"><code
class="command">service network
status</code></pre></div><div class="section"
id="s1-networkscripts-static-routes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-static-routes">6.4. Configuring Static
Routes</h2></div></div></div><div class="para">
+ If static routes are required, they can be configured for each interface. This can be
useful if you have multiple interfaces in different subnets. Use the <code
class="command">route</code> command to display the IP routing table.
+ </div><div class="para">
+ 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 eth0 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><div class="formalpara"><h5 class="formalpara"
id="id758103">IP Command Arguments Format</h5>
+ Define a default gateway on the first line. This is only required if the default
gateway is not set via DHCP:
+ </div><pre class="programlisting">default <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</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.
+ </div><div class="para">
+ Define a static route. Each line is parsed as an individual route:
+ </div><pre class="programlisting"><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>
is the network number and netmask for the static route. <em
class="replaceable"><code>X.X.X.X</code></em> and <em
class="replaceable"><code>interface</code></em> are the IP
address and interface for the default gateway respectively. The <em
class="replaceable"><code>X.X.X.X</code></em> address does
not have to be the default gateway IP address. In most cases, <em
class="replaceable"><code>X.X.X.X</code></em> will be an IP
address in a different subnet, and <em
class="replaceable"><code>interface</code></em> will be the
interface that is connected to, or can reach, that subnet. Add as many static routes as
required.
+ </div><div class="para">
+ The following is a sample <code
class="filename">route-eth0</code> file using the IP command arguments
format. The default gateway is 192.168.0.1, interface eth0. The two static routes are for
the 10.10.10.0/24 and 172.16.1.0/24 networks:
+ </div><pre class="programlisting">default 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 eth0 interface
in the 192.168.0.0/24 subnet, and an eth1 interface (10.10.10.1) in the 10.10.10.0/24
subnet:
+ </div><pre class="programlisting">10.10.10.0/24 via 10.10.10.1
dev eth1</pre><div class="warning"><div
class="admonition_header"><h2>Duplicate default
gateways</h2></div><div class="admonition"><div
class="para">
+ If the default gateway is already assigned from DHCP, the IP command arguments format
can cause one of two errors during start-up, or when bringing up an interface from the
down state using the <code class="command">ifup</code> command:
"RTNETLINK answers: File exists" or 'Error: either "to" is a
duplicate, or "<em
class="replaceable"><code>X.X.X.X</code></em>" is a
garbage.', where <em
class="replaceable"><code>X.X.X.X</code></em> is the
gateway, or a different IP address. These errors can also occur if you have another route
to another network using the default gateway. Both of these errors are safe to ignore.
+ </div></div></div><div class="formalpara"><h5
class="formalpara" id="id536655">Network/Netmask Directives
Format</h5>
+ 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="programlisting">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 eth0. 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">
+ Subsequent static routes must be numbered sequentially, and must not skip any values.
For example, <code class="computeroutput">ADDRESS0</code>, <code
class="computeroutput">ADDRESS1</code>, <code
class="computeroutput">ADDRESS2</code>, and so on.
+ </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 eth0 interface in the 192.168.0.0/24
subnet, and an eth1 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">
+ Note that if DHCP is used, it can assign these settings automatically.
+ </div></div><div class="section"
id="s1-networkscripts-functions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-functions">6.5. Network Function
Files</h2></div></div></div><a id="id425211"
class="indexterm"></a><div class="para">
+ Fedora makes use of several files that contain important common functions used to
bring interfaces up and down. Rather than forcing each interface control file to contain
these functions, they are grouped together in a few files that are called upon when
necessary.
+ </div><div class="para">
+ The <code
class="filename">/etc/sysconfig/network-scripts/network-functions</code>
file contains the most commonly used IPv4 functions, which are useful to many interface
control scripts. These functions include contacting running programs that have requested
information about changes in the status of an interface, setting hostnames, finding a
gateway device, verifying whether or not a particular device is down, and adding a default
route.
+ </div><div class="para">
+ As the functions required for IPv6 interfaces are different from IPv4 interfaces, a
<code
class="filename">/etc/sysconfig/network-scripts/network-functions-ipv6</code>
file exists specifically to hold this information. The functions in this file configure
and delete static IPv6 routes, create and remove tunnels, add and remove IPv6 addresses to
an interface, and test for the existence of an IPv6 address on an interface.
+ </div></div><div class="section"
id="s1-networkscripts-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-resources">6.6. Additional
Resources</h2></div></div></div><a id="id1229676"
class="indexterm"></a><div class="para">
+ The following are resources which explain more about network interfaces.
+ </div><div class="section"
id="s2-networkscripts-docs-inst"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-networkscripts-docs-inst">6.6.1. Installed
Documentation</h3></div></div></div><div
class="variablelist"><dl><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 guide to available options for network configuration files, including IPv6
options not covered in this chapter.
+ </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">
+ This file contains a wealth of information about the <code
class="command">ip</code> command, which can be used to manipulate
routing tables, among other things. Use the <span
class="application"><strong>ggv</strong></span> or <span
class="application"><strong>kghostview</strong></span>
application to view this file.
+ </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">Part IV. Infrastructure
Services</h1></div></div></div><div class="partintro"
id="id423776"><div></div><div class="para">
+ This part provides information how to configure services and daemons, configure
authentication, and enable remote logins.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a href="#ch-Services_and_Daemons">7.
Services and
Daemons</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-services-configuring">7.1.
Configuring
Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-configuration-enabling">7.1.1. Enabling the
Service</a></span></dt><dt><span
class="section"><a
href="#s3-services-configuration-disabling">7.1.2. Disabling the
Service</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-services-running">7.2. Running
Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-running-checking">7.2.1. Checking the Service
Status</a></span></dt><dt><span
class="section"><a href="#s3-services-running-running">7.2.2.
Running the Service</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-stopping">7.2.3. Stopping the
Service</a></span></dt><dt><span class="section
"><a href="#s3-services-running-restarting">7.2.4. Restarting the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-services-additional-resources">7.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-services-additional-resources-installed">7.3.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-services-additional-resources-books">7.3.2. Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Configuring_Authentication">8.
Configuring
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool">8.1. The Authentication
Configuration Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1.
Identity & Authentication</a></span></dt><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Advanced
_Options">8.1.2. Advanced
Options</a></span></dt><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3.
Command Line
Version</a></span></dt></dl></dd><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Introduction">8.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">8.2.1. What is
SSSD?</a></span></dt><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">8.2.2. SSSD
Features</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Setting_Up_SSSD">8.2.3. Setting Up
SSSD</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Configuring_Services">8.2.4. Configuring
Services</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Configuring_Domains">8.2.5. Configuring
Domains</a></span></dt><dt><span
class="section"><a href="#sect-SSSD_Use
r_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">8.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">8.2.7.
Configuring a Proxy Domain</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Troubleshooting">8.2.8.
Troubleshooting</a></span></dt><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">8.2.9.
SSSD Configuration File
Format</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-OpenSSH">9.
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-ssh-protocol">9.1. The SSH
Protocol</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-why">9.1.1. Why Use
SSH?</a></span></dt><dt><span
class="section"><a href="#s2-ssh-features">9.1.2. Main
Features</a></span></dt><dt><span
class="section"><a href="#s2-ssh-ver
sions">9.1.3. Protocol
Versions</a></span></dt><dt><span
class="section"><a href="#s2-ssh-conn">9.1.4. Event Sequence
of an SSH
Connection</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-configuration">9.2. An
OpenSSH
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-ssh-configuration-configs">9.2.1. Configuration
Files</a></span></dt><dt><span
class="section"><a href="#s2-ssh-configuration-sshd">9.2.2.
Starting an OpenSSH Server</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-requiring">9.2.3. Requiring SSH for Remote
Connections</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-keypairs">9.2.4. Using a Key-Based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-clients">9.3. OpenSSH
Clients</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-clients-ssh">9.3.1. Using
the ssh Utility</a></span></dt><dt><span
class="section"><a href="#s2-
ssh-clients-scp">9.3.2. Using the <code
class="command">scp</code>
Utility</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-sftp">9.3.3. Using
the <code class="command">sftp</code>
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-beyondshell">9.4. More Than
a Secure Shell</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-beyondshell-x11">9.4.1. X11
Forwarding</a></span></dt><dt><span
class="section"><a href="#s2-ssh-beyondshell-tcpip">9.4.2.
Port Forwarding</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-openssh-additional-resources">9.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-openssh-installed-docs">9.5.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-openssh-useful-websites">9.5.2.
Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></div></div><div
xml:lang="en-US" class="chapter"
id="ch-Services_and_Daemons" lang="en-
US"><div class="titlepage"><div><div><h2
class="title">Chapter 7. Services and
Daemons</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-services-configuring">7.1. Configuring
Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-configuration-enabling">7.1.1. Enabling the
Service</a></span></dt><dt><span
class="section"><a
href="#s3-services-configuration-disabling">7.1.2. Disabling the
Service</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-services-running">7.2. Running
Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s3-services-running-checking">7.2.1. Checking the Service
Status</a></span></dt><dt><span
class="section"><a href="#s3-services-running-running">7.2.2.
Running the Service</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-stopping">7.2.3. Stopping the
Service</a></span></dt><dt><span
class="section"><a
href="#s3-services-running-restarting">7.2
.4. Restarting the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-services-additional-resources">7.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-services-additional-resources-installed">7.3.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-services-additional-resources-books">7.3.2. Related
Books</a></span></dt></dl></dd></dl></div><a
id="id439174" class="indexterm"></a><div
class="para">
+ Maintaining security on your system is extremely important, and one approach for this
task is to manage access to system services carefully. Your system may need to provide
open access to particular services (for example, <code
class="systemitem">httpd</code> if you are running a web server).
However, if you do not need to provide a service, you should turn it off to minimize your
exposure to possible bug exploits.
+ </div><div class="para">
+ This chapter 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 <span
class="application"><strong>systemctl</strong></span>
utility.
+ </div><div class="important"><div
class="admonition_header"><h2>Keep the system
secure</h2></div><div class="admonition"><div
class="para">
+ When you allow access for new services, always remember that both the firewall and
<span
class="application"><strong>SELinux</strong></span> need to
be configured as well. One of the most common mistakes committed when configuring a new
service is neglecting to implement the necessary firewall configuration and SELinux
policies to allow access for it. Refer to the Fedora <em
class="citetitle">Security Guide</em> (see <a class="xref"
href="#s1-services-additional-resources">Section 7.3, “Additional
Resources”</a>) for more information.
+ </div></div></div><div class="section"
id="s1-services-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-services-configuring">7.1. Configuring
Services</h2></div></div></div><a id="id423924"
class="indexterm"></a><a id="id788781"
class="indexterm"></a><div class="para">
+ To allow you to configure which services are started at boot time, Fedora is shipped
with the <span
class="application"><strong>systemctl</strong></span>
command line tool.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not use the ntsysv and chkconfig
utilities</h2></div><div class="admonition"><div
class="para">
+ Although it is still possible to use the <span
class="application"><strong>ntsysv</strong></span> and
<span
class="application"><strong>chkconfig</strong></span>
utilities to manage services that have init scripts installed in the <code
class="filename">/etc/rc.d/init.d/</code> directory, it is advised that
you use the <span
class="application"><strong>systemctl</strong></span>
utility.
+ </div></div></div><div class="important"><div
class="admonition_header"><h2>Enabling the irqbalance
service</h2></div><div class="admonition"><div
class="para">
+ To ensure optimal performance on POWER architecture, it is recommended that the
<code class="systemitem">irqbalance</code> service is enabled. In
most cases, this service is installed and configured to run during the Fedora 15
installation. To verify that <code
class="systemitem">irqbalance</code> is running, type the following at
a shell prompt:
+ </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"
id="s3-services-configuration-enabling">7.1.1. Enabling the
Service</h3></div></div></div><div class="para">
+ To configure a service to be automatically started at boot time, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to enable the <code
class="systemitem">httpd</code> service, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable
httpd.service</code></pre><div class="para">
+ The service will be started the next time you boot the system. If you need to start
the service immediately, use the <code
class="command">systemctl</code> command as described in <a
class="xref" href="#s3-services-running-running">Section 7.2.2,
“Running the Service”</a>.
+ </div></div><div class="section"
id="s3-services-configuration-disabling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s3-services-configuration-disabling">7.1.2. Disabling the
Service</h3></div></div></div><div class="para">
+ To disable starting a service at boot time, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to disable the <code
class="systemitem">httpd</code> service, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable
httpd.service</code></pre><div class="para">
+ The next time you boot the system, the service will <span
class="emphasis"><em>not</em></span> be started. If you
need to stop the service immediately, use the <code
class="command">systemctl</code> command as described in <a
class="xref" href="#s3-services-running-stopping">Section 7.2.3,
“Stopping the Service”</a>.
+ </div></div></div><div class="section"
id="s1-services-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-services-running">7.2. Running
Services</h2></div></div></div><a id="id849229"
class="indexterm"></a><a id="id792552"
class="indexterm"></a><div class="para">
+ The <span
class="application"><strong>systemctl</strong></span>
utility also allows you to determine the status of a particular service, as well as to
start, stop, or restart a service.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not use the service
utility</h2></div><div class="admonition"><div
class="para">
+ Although it is still possible to use the <span
class="application"><strong>service</strong></span> utility
to manage services that have init scripts installed in the <code
class="filename">/etc/rc.d/init.d/</code> directory, it is advised that
you use the <span
class="application"><strong>systemctl</strong></span>
utility.
+ </div></div></div><div class="section"
id="s3-services-running-checking"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s3-services-running-checking">7.2.1. Checking the Service
Status</h3></div></div></div><div class="para">
+ To determine the status of a service, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to determine the status of the <code
class="systemitem">httpd</code> service, type the following at a shell
prompt:
+ </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 class="para">
+ The above command provides a detailed information on the service status. If you only
need to verify that a service is running, use the <code
class="command">systemctl</code> command in the following form
instead:
+ </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="para">
+ For example:
+ </div><pre class="screen">~]$ <code
class="command">systemctl is-active httpd.service</code>
+active</pre><div class="para">
+ To display a list of all active system services, type:
+ </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">[output
truncated]</span></em></pre><div class="para">
+ As you can see, each line consists of the following columns:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">UNIT</code> — Provides
information whether the <code class="systemitem">systemd</code> unit
was properly loaded.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">ACTIVE</code> — Provides a
high-level unit activation state.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">SUB</code> — Provides a
low-level unit activation state.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">JOB</code> — Displays a pending
job for a unit.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">DESCRIPTION</code> — Provides a
brief description of the service.
+ </div></li></ul></div><div class="para">
+ In the example above, the <code class="systemitem">abrtd</code>
service is loaded, active, and running, and it does not have any pending jobs.
+ </div></div><div class="section"
id="s3-services-running-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s3-services-running-running">7.2.2. Running the
Service</h3></div></div></div><div class="para">
+ To run a service, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to start the <code class="systemitem">httpd</code>
service, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl start
httpd.service</code></pre></div><div class="section"
id="s3-services-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s3-services-running-stopping">7.2.3. Stopping the
Service</h3></div></div></div><div class="para">
+ To stop a service, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to stop the <code class="systemitem">httpd</code>
service, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop
httpd.service</code></pre></div><div class="section"
id="s3-services-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s3-services-running-restarting">7.2.4. Restarting the
Service</h3></div></div></div><div class="para">
+ To restart a service, use the <code
class="command">systemctl</code> command in the following form:
+ </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="para">
+ For example, to restart the <code
class="systemitem">httpd</code> service, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
httpd.service</code></pre></div></div><div
class="section" id="s1-services-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-services-additional-resources">7.3. Additional
Resources</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"
id="s2-services-additional-resources-installed">7.3.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="literal">systemctl</code>(1) — The manual page
for the <span
class="application"><strong>systemctl</strong></span>
utility.
+ </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"
id="s2-services-additional-resources-books">7.3.2. Related
Books</h3></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <em
class="citetitle">Security Guide</em>
</span></dt><dd><div class="para">
+ A guide to securing Fedora. It contains valuable information on how to set up the
firewall, as well as the configuration of <span
class="application"><strong>SELinux</strong></span>.
+ </div></dd></dl></div></div></div></div><div
xml:lang="en-US" class="chapter"
id="ch-Configuring_Authentication" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 8. Configuring
Authentication</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#sect-The_Authentication_Configuration_Tool">8.1. The Authentication
Configuration Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1.
Identity & Authentication</a></span></dt><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">8.1.2.
Advanced Options</a></span></dt><dt><span
class="section"><a
href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3.
Command Line
Version</a></span></dt></dl></dd><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Introduction">8.2. The System Security Services
Daemon (SSSD)</a></spa
n></dt><dd><dl><dt><span class="section"><a
href="#sect-SSSD_User_Guide-Introduction-What_is_SSSD">8.2.1. What is
SSSD?</a></span></dt><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">8.2.2. SSSD
Features</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Setting_Up_SSSD">8.2.3. Setting Up
SSSD</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Configuring_Services">8.2.4. Configuring
Services</a></span></dt><dt><span
class="section"><a
href="#chap-SSSD_User_Guide-Configuring_Domains">8.2.5. Configuring
Domains</a></span></dt><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">8.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">8.2.7.
Configuring a Proxy Domain</a></span></dt><dt><span
class="section"><a href="#chap-SSSD_
User_Guide-Troubleshooting">8.2.8.
Troubleshooting</a></span></dt><dt><span
class="section"><a
href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">8.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"
id="sect-The_Authentication_Configuration_Tool">8.1. The Authentication
Configuration Tool</h2></div></div></div><a
id="id1301138" class="indexterm"></a><a
id="id1301124" class="indexterm"></a><div
class="para">
+ When a user logs in to a Fedora system, the username and password combination must be
verified, or <em class="firstterm">authenticated</em>, as a valid
and active user. Sometimes the information to verify the user is located on the local
system, and other times the system defers the authentication to a user database on a
remote system.
+ </div><div class="para">
+ The <span class="application"><strong>Authentication
Configuration Tool</strong></span> provides a graphical interface for
configuring user information retrieval from <em
class="firstterm">Lightweight Directory Access Protocol</em> (LDAP),
<em class="firstterm"> Network Information Service</em> (NIS), and
<em class="firstterm">Winbind</em> user account databases. This tool
also allows you to configure Kerberos to be used as the authentication protocol when using
LDAP or NIS.
+ </div><div class="note"><div
class="admonition_header"><h2>Using a high or medium security
level</h2></div><div class="admonition"><div
class="para">
+ If you configured a medium or high security level during installation (or with the
<span class="application"><strong>Security Level Configuration
Tool</strong></span>), then the firewall will prevent NIS authentication. For
more information about firewalls, refer to the <em
class="citetitle">"Firewalls"</em> section of the Fedora
<em class="citetitle">Security Guide</em>.
+ </div></div></div><a id="id552946"
class="indexterm"></a><a id="id552923"
class="indexterm"></a><div class="para">
+ To start the graphical version of the <span
class="application"><strong>Authentication
Configuration</strong></span> tool from the desktop, select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>Other</strong></span> →
<span
class="guimenuitem"><strong>Authentication</strong></span>
form the <span
class="guimenu"><strong>Activities</strong></span> menu or
type the command <code
class="command">system-config-authentication</code> at a shell prompt
(for example, in an <span
class="application"><strong>XTerm</strong></span> or a
<span class="application"><strong>GNOME</strong></span>
terminal).
+ </div><div class="important"><div
class="admonition_header"><h2>Your changes are immediately
applied</h2></div><div class="admonition"><div
class="para">
+ After exiting the authentication program, any changes you made take effect
immediately.
+ </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"
id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1. Identity
& Authentication</h3></div></div></div><div
class="para">
+ The <span class="guilabel"><strong>Identity &
Authentication</strong></span> tab allows you to configure how users should be
authenticated, and has several options for each method of authentication. To select which
user account database should be used, select an option from the drop-down list.
+ </div><div class="figure"><div
class="figure-contents"><div class="mediaobject"
align="center"><img src="images/authconfig_LDAP_kerb.png"
align="middle" alt="Identity & Authentication; changing the option
in the User Account Database drop-down list changes the contents of the tab"
/></div></div><h6>Figure 8.1. Identity & Authentication;
changing the option in the User Account Database drop-down list changes the contents of
the tab</h6></div><br class="figure-break" /><div
class="para">
+ The following list explains what each option configures:
+ </div><h4 id="id708011">LDAP</h4><a
id="id708019" class="indexterm"></a><div
class="para">
+ The <span
class="guilabel"><strong>LDAP</strong></span> option
instructs the system to retrieve user information via LDAP. It contains the following
specifications:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP Search Base
DN</strong></span> — Specifies that user information should be retrieved using
the listed Distinguished Name (DN).
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>LDAP
Server</strong></span> — Specifies the address of the <code
class="systemitem">LDAP</code> server.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Use TLS to encrypt
connections</strong></span> — When enabled, <code
class="systemitem">Transport Layer Security</code> (TLC) will be used
to encrypt passwords sent to the <code
class="systemitem">LDAP</code> server. The <span
class="guibutton"><strong>Download CA
Certificate</strong></span> option allows you to specify a URL from which to
download a valid <em class="firstterm">Certificate Authority
certificate</em> (CA). A valid CA certificate must be in the <em
class="firstterm">Privacy Enhanced Mail</em> (PEM) format.
+ </div><div class="important"><div
class="admonition_header"><h2>Using ldaps:// in the LDAP Server
field</h2></div><div class="admonition"><div
class="para">
+ The <span class="guilabel"><strong>Use TLS to encrypt
connections</strong></span> option must not be ticked if an <code
class="systemitem">ldaps://</code> server address is specified in the
<span class="guilabel"><strong>LDAP
Server</strong></span> field.
+ </div></div></div><div class="para">
+ For more information about CA Certificates, refer to <a class="xref"
href="#s3-apache-mod_ssl-certificates">Section 12.1.8.1, “An Overview of
Certificates and Security”</a>.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">openldap-clients</code> package must
be installed for this option to work.
+ </div><div class="para">
+ For more information about LDAP, refer to <a class="xref"
href="#s1-OpenLDAP">Section 14.1, “OpenLDAP”</a>.
+ </div><div class="para">
+ LDAP provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><a id="id573687"
class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Kerberos
password</strong></span> — This option enables Kerberos authentication. It
contains the following specifications:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Realm</strong></span> — Configures
the realm for the Kerberos server. The realm is the network that uses Kerberos, composed
of one or more KDCs and a potentially large number of clients.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>KDCs</strong></span> — Defines the
Key Distribution Centers (KDC), which are servers that issue Kerberos tickets.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Admin
Servers</strong></span> — Specifies the administration server(s) running
<code class="command">kadmind</code>.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The <span class="guimenu"><strong>Kerberos
Settings</strong></span> dialog also allows you to use DNS to resolve hosts to
realms and locate KDCs for realms.
+ </div><div class="para">
+ The <code class="filename">krb5-libs</code> and <code
class="filename">krb5-workstation</code> packages must be installed for
this option to work. For more information about Kerberos, refer to section <em
class="citetitle">Using Kerberos</em> of the Fedora 15 <em
class="citetitle">Managing Single Sign-On and Smart Cards</em> guide.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>LDAP
password</strong></span> — This option instructs standard PAM-enabled
applications to use LDAP authentication with options specified in the User Account
Configuration of LDAP. When using this option, you must provide an <code
class="systemitem">ldaps://</code> server address or use TLS for LDAP
authentication.
+ </div></li></ul></div><div
class="note"><div class="admonition_header"><h2>Setting
up the SSSD service</h2></div><div class="admonition"><div
class="para">
+ The SSSD service is used as a client for LDAP and Kerberos servers. Thus, offline
login is enabled and supported by default. No user interaction is needed to set up the
SSSD service with the <span
class="application"><strong>Authentication Configuration
Tool</strong></span>. For more information about the SSSD service, refer to
<a class="xref"
href="#chap-SSSD_User_Guide-Introduction">Section 8.2, “The System Security
Services Daemon (SSSD)”</a>
+ </div></div></div><h4
id="id573649">NIS</h4><a id="id476444"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>NIS</strong></span> option
configures the system to connect to a NIS server (as an NIS client) for user and password
authentication. To configure this option, specify the NIS domain and NIS server. If the
NIS server is not specified, the daemon attempts to find it via broadcast.
+ </div><div class="para">
+ The <span class="package">ypbind</span> package must be
installed for this option to work. If the NIS user account database is used, the <code
class="systemitem">portmap</code> and <code
class="systemitem">ypbind</code> services are started and are also
enabled to start at boot time.
+ </div><div class="para">
+ For more information about NIS, refer to section <em
class="citetitle">"Securing NIS"</em> of the Fedora <em
class="citetitle">Security Guide</em>.
+ </div><div class="para">
+ NIS provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Kerberos
password</strong></span> — This option enables Kerberos authentication. For
more information about configuration of the Kerberos authentication method, refer to the
previous section on LDAP.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="id476366" class="indexterm"></a>
+ <span class="guilabel"><strong>NIS
password</strong></span> — This option enables NIS authentication. NIS can
provide authentication information to outside processes to authenticate users.
+ </div></li></ul></div><h4
id="id417712">Winbind</h4><a id="id417708"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>Winbind</strong></span> option
configures the system to connect to a Windows Active Directory or a Windows domain
controller. User information from the specified directory or domain controller can then be
accessed, and server authentication options can be configured. It contains the following
specifications:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind
Domain</strong></span> — Specifies the Windows Active Directory or domain
controller to connect to.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Security
Model</strong></span> — Allows you to select a security model, which
configures the Samba client mode of operation. The drop-down list allows you to select any
of the following:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>ads</strong></span> — This mode
instructs Samba to act as a domain member in an Active Directory Server (ADS) realm. To
operate in this mode, the <code class="filename">krb5-server</code>
package must be installed, and Kerberos must be configured properly.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>domain</strong></span> — In this
mode, Samba will attempt to validate the username/password by authenticating it through a
Windows NT Primary or Backup Domain Controller, similar to how a Windows NT Server would.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>server</strong></span> — In this
mode, Samba will attempt to validate the username/password by authenticating it through
another SMB server (for example, a Windows NT Server). If the attempt fails, the <span
class="guilabel"><strong>user</strong></span> mode will
take effect instead.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>user</strong></span> — This is the
default mode. With this level of security, a client must first log in with a valid
username and password. Encrypted passwords can also be used in this security mode.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Winbind ADS
Realm</strong></span> — When the <span
class="guilabel"><strong>ads</strong></span> Security Model
is selected, this allows you to specify the ADS Realm the Samba server should act as a
domain member of.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Winbind Domain
Controllers</strong></span> — Use this option to specify which domain
controller <code class="command">winbind</code> should use. For more
information about domain controllers, please refer to <a class="xref"
href="#s3-samba-domain-controller">Section 15.1.6.3, “Domain
Controller”</a>.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Template
Shell</strong></span> — When filling out the user information for a Windows NT
user, the <code class="command">winbindd</code> daemon uses the
value chosen here to specify the login shell for that user.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Allow offline
login</strong></span> — By checking this option, you allow authentication
information to be stored in a local cache (provided by SSSD). This information is then
used when a user attempts to authenticate while offline.
+ </div></li></ul></div><div class="para">
+ For more information about the <code
class="command">winbindd</code> service, refer to <a
class="xref" href="#s2-samba-daemons">Section 15.1.2, “Samba
Daemons and Related Services”</a>.
+ </div><a id="id785398"
class="indexterm"></a><div class="para">
+ Winbind provides only one method of authentication, <span
class="guilabel"><strong>Winbind password</strong></span>.
This method of authentication uses the options specified in the User Account Configuration
of Winbind to connect to a Windows Active Directory or a Windows domain controller.
+ </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"
id="sect-The_Authentication_Configuration_Tool-Advanced_Options">8.1.2. Advanced
Options</h3></div></div></div><div class="para">
+ This tab allows you to configure advanced options, as listed below.
+ </div><div class="figure"><div
class="figure-contents"><div class="mediaobject"
align="center"><img src="images/authconfig_advanced.png"
align="middle" width="444" alt="Advanced Options"
/></div></div><h6>Figure 8.2. Advanced
Options</h6></div><br class="figure-break" /><h4
id="id806942">Local Authentication Options</h4><div
class="itemizedlist"><ul><li class="listitem"><a
id="id806936" class="indexterm"></a><div
class="para">
+ <span class="guilabel"><strong>Enable fingerprint reader
support</strong></span> — By checking this option, you enable fingerprint
authentication to log in by scanning your finger with the fingerprint reader.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Enable local access
control</strong></span> — When enabled, <code
class="filename">/etc/security/access.conf</code> is consulted for
authorization of a user.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Password Hashing
Algorithm</strong></span> — This option lets you specify which hashing or
cryptographic algorithm should be used to encrypt locally stored passwords.
+ </div></li></ul></div><h4
id="id591955">Other Authentication Options</h4><div
class="para">
+ <span class="guilabel"><strong>Create home directories on the
first login</strong></span> — When enabled, the user's home directory is
automatically created when they log in if it does not already exist.
+ </div><h4 id="id591977">Smart Card Authentication
Options</h4><a id="id591972"
class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Enable smart card
support</strong></span> — This option enables smart card authentication. Smart
card authentication allows you to log in using a certificate and a key associated with a
smart card.
+ </div><div class="para">
+ When the <span class="guilabel"><strong>Enable smart card
support</strong></span> option is checked, the following options can be
specified:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Card Removal
Action</strong></span> — This option defines what action the system performs
when the card is removed from the card reader during an active session. Two alternatives
are available:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Ignore</strong></span> — The card
removal is ignored and the system continues to function as normal.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Lock</strong></span> — The current
session is immediately locked.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Require smart card
login</strong></span> — Requires the user to login and authenticate with a
smart card. It essentially disables any other type of password authentication. This option
should not be selected until after you have successfully logged in using a smart card.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The <span class="package">pam_pkcs11</span> and the <span
class="package">coolkey</span> packages must be installed for this
option to work. For more information about smart cards, refer to the Red Hat Enterprise
Linux 6 <a
href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/h...
Single Sign-On and Smart Cards Guide</a>.
+ <div class="note"><div
class="admonition_header"><h2>Click Revert to restore the previous
configuration</h2></div><div class="admonition"><div
class="para">
+ You can restore all of the options specified in the <span
class="application"><strong>Authentication Configuration
Tool</strong></span> to the previous configuration setup by clicking <span
class="guibutton"><strong>Revert</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"
id="sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3. Command
Line Version</h3></div></div></div><a id="id1015969"
class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Authentication
Configuration</strong></span> tool also supports a command line interface. The
command line version can be used in a configuration script or a kickstart script. The
authentication options are summarized in <a class="xref"
href="#tb-authconfig-cmd-line">Table 8.1, “Command line options”</a>.
+ </div><div class="note"><div
class="admonition_header"><h2>Getting the list of supported
authentication options</h2></div><div
class="admonition"><div class="para">
+ These options can also be found in the <code
class="command">authconfig</code> man page or by typing <code
class="command">authconfig --help</code> at the shell prompt.
+ </div></div></div><div class="table"
id="tb-authconfig-cmd-line"><h6>Table 8.1. Command line
options</h6><div class="table-contents"><table
summary="Command line options" border="1"><colgroup><col
width="60%" class="option" /><col width="40%"
class="description" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">--enableshadow, --useshadow</code>
+ </td><td>
+ Enable shadow passwords
+ </td></tr><tr><td>
+ <code class="command">--disableshadow</code>
+ </td><td>
+ Disable shadow passwords
+ </td></tr><tr><td>
+ <code class="command">--passalgo=<em
class="replaceable"><code>descrypt|bigcrypt|md5|sha256|sha512</code></em></code>
+ </td><td>
+ Hash/crypt algorithm to be used
+ </td></tr><tr><td>
+ <code class="command">--enablenis</code>
+ </td><td>
+ Enable NIS for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disablenis</code>
+ </td><td>
+ Disable NIS for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--nisdomain=<em
class="replaceable"><code>domain</code></em> </code>
+ </td><td>
+ Specify an NIS domain
+ </td></tr><tr><td>
+ <code class="command">--nisserver=<em
class="replaceable"><code>server</code></em> </code>
+ </td><td>
+ Specify an NIS server
+ </td></tr><tr><td>
+ <code class="command">--enableldap</code>
+ </td><td>
+ Enable LDAP for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disableldap</code>
+ </td><td>
+ Disable LDAP for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--enableldaptls</code>
+ </td><td>
+ Enable use of TLS with LDAP
+ </td></tr><tr><td>
+ <code class="command">--disableldaptls</code>
+ </td><td>
+ Disable use of TLS with LDAP
+ </td></tr><tr><td>
+ <code class="command">--enablerfc2307bis</code>
+ </td><td>
+ Enable use of RFC-2307bis schema for LDAP user information lookups
+ </td></tr><tr><td>
+ <code class="command">--disablerfc2307bis</code>
+ </td><td>
+ Disable use of RFC-2307bis schema for LDAP user information lookups
+ </td></tr><tr><td>
+ <code class="command">--enableldapauth</code>
+ </td><td>
+ Enable LDAP for authentication
+ </td></tr><tr><td>
+ <code class="command">--disableldapauth</code>
+ </td><td>
+ Disable LDAP for authentication
+ </td></tr><tr><td>
+ <code class="command">--ldapserver=<em
class="replaceable"><code>server</code></em> </code>
+ </td><td>
+ Specify an LDAP server
+ </td></tr><tr><td>
+ <code class="command">--ldapbasedn=<em
class="replaceable"><code>dn</code></em> </code>
+ </td><td>
+ Specify an LDAP base DN (Distinguished Name)
+ </td></tr><tr><td>
+ <code class="command">--ldaploadcacert=<em
class="replaceable"><code>URL</code></em> </code>
+ </td><td>
+ Load a CA certificate from the specified URL
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5</code>
+ </td><td>
+ Enable Kerberos for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5</code>
+ </td><td>
+ Disable Kerberos for authentication
+ </td></tr><tr><td>
+ <code class="command">--krb5kdc=<em
class="replaceable"><code>server</code></em> </code>
+ </td><td>
+ Specify Kerberos KDC server
+ </td></tr><tr><td>
+ <code class="command">--krb5adminserver=<em
class="replaceable"><code>server</code></em> </code>
+ </td><td>
+ Specify Kerberos administration server
+ </td></tr><tr><td>
+ <code class="command">--krb5realm=<em
class="replaceable"><code>realm</code></em> </code>
+ </td><td>
+ Specify Kerberos realm
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5kdcdns</code>
+ </td><td>
+ Enable use of DNS to find Kerberos KDCs
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5kdcdns</code>
+ </td><td>
+ Disable use of DNS to find Kerberos KDCs
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5realmdns</code>
+ </td><td>
+ Enable use of DNS to find Kerberos realms
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5realmdns</code>
+ </td><td>
+ Disable use of DNS to find Kerberos realms
+ </td></tr><tr><td>
+ <code class="command">--enablewinbind</code>
+ </td><td>
+ Enable winbind for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disablewinbind</code>
+ </td><td>
+ Disable winbind for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindauth</code>
+ </td><td>
+ Enable winbindauth for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindauth</code>
+ </td><td>
+ Disable winbindauth for authentication
+ </td></tr><tr><td>
+ <code class="command">--winbindseparator=<em
class="replaceable"><code>\</code></em> </code>
+ </td><td>
+ Character used to separate the domain and user part of winbind usernames if
<code class="command">winbindusedefaultdomain</code> is not enabled
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplatehomedir=<em
class="replaceable"><code>/home/%D/%U</code></em>
</code>
+ </td><td>
+ Directory that winbind users have as their home
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplateprimarygroup=<em
class="replaceable"><code>nobody</code></em> </code>
+ </td><td>
+ Group that winbind users have as their primary group
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplateshell=<em
class="replaceable"><code>/bin/false</code></em>
</code>
+ </td><td>
+ Shell that winbind users have as their default login shell
+ </td></tr><tr><td>
+ <code
class="command">--enablewinbindusedefaultdomain</code>
+ </td><td>
+ Configures winbind to assume that users with no domain in their usernames are
domain users
+ </td></tr><tr><td>
+ <code
class="command">--disablewinbindusedefaultdomain</code>
+ </td><td>
+ Configures winbind to assume that users with no domain in their usernames are not
domain users
+ </td></tr><tr><td>
+ <code class="command">--winbindjoin=<em
class="replaceable"><code>Administrator</code></em>
</code>
+ </td><td>
+ Joins the winbind domain or ADS realm as the specified administrator
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindoffline</code>
+ </td><td>
+ Configures winbind to allow offline login
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindoffline</code>
+ </td><td>
+ Configures winbind to prevent offline login
+ </td></tr><tr><td>
+ <code class="command">--smbsecurity=<em
class="replaceable"><code>user|server|domain|ads</code></em></code>
+ </td><td>
+ Security mode to use for the Samba and Winbind services
+ </td></tr><tr><td>
+ <code class="command">--smbrealm=<em
class="replaceable"><code>realm</code></em></code>
+ </td><td>
+ Default realm for Samba and Winbind services when <span
class="guilabel"><strong>security</strong></span> is set to
<span class="guimenuitem"><strong>ads</strong></span>
+ </td></tr><tr><td>
+ <code class="command">--enablewins</code>
+ </td><td>
+ Enable Wins for hostname resolution
+ </td></tr><tr><td>
+ <code class="command">--disablewins</code>
+ </td><td>
+ Disable Wins for hostname resolution
+ </td></tr><tr><td>
+ <code class="command">--enablesssd</code>
+ </td><td>
+ Enable SSSD for user information
+ </td></tr><tr><td>
+ <code class="command">--disablesssd</code>
+ </td><td>
+ Disable SSSD for user information
+ </td></tr><tr><td>
+ <code class="command">--enablecache</code>
+ </td><td>
+ Enable <code class="command">nscd</code>
+ </td></tr><tr><td>
+ <code class="command">--disablecache</code>
+ </td><td>
+ Disable <code class="command">nscd</code>
+ </td></tr><tr><td>
+ <code class="command">--enablelocauthorize</code>
+ </td><td>
+ Local authorization is sufficient for local users
+ </td></tr><tr><td>
+ <code class="command">--disablelocauthorize</code>
+ </td><td>
+ Local users are also authorized through a remote service
+ </td></tr><tr><td>
+ <code class="command">--enablesysnetauth</code>
+ </td><td>
+ Authenticate system accounts with network services
+ </td></tr><tr><td>
+ <code class="command">--disablesysnetauth</code>
+ </td><td>
+ Authenticate system accounts with local files only
+ </td></tr><tr><td>
+ <code class="command">--enablepamaccess</code>
+ </td><td>
+ Check <code
class="filename">/etc/security/access.conf</code> during account
authorization
+ </td></tr><tr><td>
+ <code class="command">--disablepamaccess</code>
+ </td><td>
+ Do not check <code
class="filename">/etc/security/access.conf</code> during account
authorization
+ </td></tr><tr><td>
+ <code class="command">--enablemkhomedir</code>
+ </td><td>
+ Create a home directory for a user on the first login
+ </td></tr><tr><td>
+ <code class="command">--disablemkhomedir</code>
+ </td><td>
+ Do not create a home directory for a user on the first login
+ </td></tr><tr><td>
+ <code class="command">--enablesmartcard</code>
+ </td><td>
+ Enable authentication with a smart card
+ </td></tr><tr><td>
+ <code class="command">--disablesmartcard</code>
+ </td><td>
+ Disable authentication with a smart card
+ </td></tr><tr><td>
+ <code class="command">--enablerequiresmartcard</code>
+ </td><td>
+ Require smart card for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablerequiresmartcard</code>
+ </td><td>
+ Do not require smart card for authentication
+ </td></tr><tr><td>
+ <code class="command">--smartcardmodule=<em
class="replaceable"><code>module</code></em></code>
+ </td><td>
+ Default smart card module to use
+ </td></tr><tr><td>
+ <code class="command">--smartcardaction=<em
class="replaceable"><code>0=Lock|1=Ignore</code></em></code>
+ </td><td>
+ Action to be taken when smart card removal is detected
+ </td></tr><tr><td>
+ <code class="command">--enablefingerprint</code>
+ </td><td>
+ Enable fingerprint authentication
+ </td></tr><tr><td>
+ <code class="command">--disablefingerprint</code>
+ </td><td>
+ Disable fingerprint authentication
+ </td></tr><tr><td>
+ <code class="command">--nostart</code>
+ </td><td>
+ Do not start or stop the <code
class="command">portmap</code>, <code
class="command">ypbind</code>, or <code
class="command">nscd</code> services even if they are configured
+ </td></tr><tr><td>
+ <code class="command">--test</code>
+ </td><td>
+ Do not update the configuration files, only print the new settings
+ </td></tr><tr><td>
+ <code class="command">--update, --kickstart</code>
+ </td><td>
+ Opposite of <code class="command">--test</code>, update
configuration files with changed settings
+ </td></tr><tr><td>
+ <code class="command">--updateall</code>
+ </td><td>
+ Update all configuration files
+ </td></tr><tr><td>
+ <code class="command">--probe</code>
+ </td><td>
+ Probe and display network defaults
+ </td></tr><tr><td>
+ <code class="command">--savebackup=<em
class="replaceable"><code>name</code></em></code>
+ </td><td>
+ Save a backup of all configuration files
+ </td></tr><tr><td>
+ <code class="command">--restorebackup=<em
class="replaceable"><code>name</code></em></code>
+ </td><td>
+ Restore a backup of all configuration files
+ </td></tr><tr><td>
+ <code class="command">--restorelastbackup</code>
+ </td><td>
+ Restore the backup of configuration files saved before the previous configuration
change
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div></div><div
xml:lang="en-US" class="section"
id="chap-SSSD_User_Guide-Introduction" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="chap-SSSD_User_Guide-Introduction">8.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"
id="sect-SSSD_User_Guide-Introduction-What_is_SSSD">8.2.1. What is
SSSD?</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"
id="sect-SSSD_User_Guide-Introduction-SSSD_Features">8.2.2. SSSD
Features</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"
id="sect-SSSD_User_Guide-SSSD_Features-Offline_Authentication">8.2.2.1. Offline
Authentication</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"
id="sect-SSSD_User_Guide-SSSD_Features-Server_Load_Reduction">8.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"
id="sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">8.2.2.3. Support
for Multiple Domains</h4></div></div></div><a
id="id462445" 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="id462394">Considerations Associated with
Deleting Cache Files</h5><a id="id462389"
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"><div class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="id790243">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id790231">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id790215">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id790199">8.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"
id="sect-SSSD_User_Guide-SSSD_Features-Differentiating_Like_named_Users">8.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(a)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"
id="sect-SSSD_User_Guide-SSSD_Features-Integration_with_IPA">8.2.2.6. Integration
with 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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id558125">8.2.2.6.1. Support for Dynamic DNS
Updates</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="id558098">Setting up Dynamic DNS
Updates</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"
id="chap-SSSD_User_Guide-Setting_Up_SSSD">8.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"
id="sect-SSSD_User_Guide-Setting_Up_SSSD-Installing_SSSD">8.2.3.1. Installing
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"
id="sect-SSSD_User_Guide-Installing_SSSD-Upgrading_from_a_Previous_Version">8.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><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"
id="sect-SSSD_User_Guide-Installing_SSSD-Starting_and_Stopping_SSSD">8.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">Section 8.2.5, “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"
id="sect-SSSD_User_Guide-Setting_Up_SSSD-Configuring_SSSD">8.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">Section 8.2.9,
“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"
id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS">8.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"
id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h6 class="title"
id="id606944">8.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"
id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id1301394">8.2.3.2.3. Configuring Access
Control</h5></div></div></div><a id="id676422"
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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h6 class="title"
id="id1301434">8.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="id450542">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="id471764">Access Control
Rules</h5><a id="id725944" 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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h6 class="title"
id="id896796">8.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="id636742">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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover">8.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">Section 8.2.3.2.4.1,
“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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">8.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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-How_the_Failover_Mechanism_Works">8.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">Section 8.2.3.2.4.1,
“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"
id="chap-SSSD_User_Guide-Configuring_Services">8.2.4. Configuring
Services</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"
id="sect-SSSD_User_Guide-Configuring_Services-Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Configuration_Options-General_Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Configuration_Options-NSS_Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Configuration_Options-PAM_Configuration_Options">8.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"
id="chap-SSSD_User_Guide-Configuring_Domains">8.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><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">Section 8.2.5.2,
“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">Section 8.2.6,
“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">Section 8.2.7,
“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"
id="sect-SSSD_User_Guide-Configuring_Domains-Domain_Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Domain_Configuration_Options-General_Domain_Configuration_Options">8.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">Section 8.2.7,
“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@IPA</code>
+ipauser01@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@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@domain</code>, not <code
class="systemitem">name@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"
id="sect-SSSD_User_Guide-Domain_Configuration_Options-Proxy_Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">8.2.5.2. Configuring
an LDAP Domain</h4></div></div></div><a id="id480675"
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...
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="id639261" 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@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="id771294" 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">Section 8.2.3.2.4.1,
“Using SRV Records with Failover”</a>.
+ </div></div></div><h5
id="id606977"></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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">8.2.5.3. Configuring
a Microsoft Active Directory Domain</h4></div></div></div><a
id="id480270" 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...
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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2003">8.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">Section 8.2.5.3.2,
“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="id762595">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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008">8.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"
id="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">8.2.6. Setting
Up Kerberos Authentication</h3></div></div></div><a
id="id818815" 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@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">Section 8.2.3.2.4.1,
“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"
id="sect-setting-up-sasl-gssapi-authentication">8.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="important"><div
class="admonition_header"><h2>Setting up the SASL/GSSAPI authentication
on Fedora 6.0</h2></div><div class="admonition"><div
class="para">
+ The following setup works correctly on all Fedora 6.1 systems and any systems
released after it. However, when using Fedora 6.0, you must correctly configure the
<code class="option">default_realm</code> option in the <code
class="option">[libdefaults]</code> section and <code
class="option">kdc</code> option for your realm in the <code
class="option">[realms]</code> section in the <code
class="filename">/etc/krb5.conf</code> configuration file not only on
the directory server and the KDC but also on the client running SSSD. For more information
on various <code class="filename">/etc/krb5.conf</code> options,
refer to <code class="command">man krb5.conf</code>
+ </div></div></div><div
class="variablelist"><dl><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><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(a)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"
id="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">8.2.7. Configuring
a Proxy Domain</h3></div></div></div><a id="id840981"
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"
id="sect-SSSD-proxy-krb5">8.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">Section 8.2.6,
“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"
id="sect-SSSD-LDAP-proxy">8.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">Section 8.2.5.2,
“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"
id="sect-SSSD-proxy-proxy">8.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"
id="chap-SSSD_User_Guide-Troubleshooting">8.2.8. Troubleshooting</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"
id="sect-SSSD_User_Guide-Troubleshooting-Using_SSSD_Log_Files">8.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"
id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Configuration">8.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"
id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Service_Configuration">8.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"
id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_NSS">8.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">Section 8.2.3.2.1,
“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"
id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_PAM">8.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@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">Section 8.2.3.2.2,
“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"><div class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id660704">8.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"
id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Domain_Configuration">8.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"
id="sect-SSSD_User_Guide-Troubleshooting-Additional_Resources">8.2.8.5. Additional
Resources</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"
id="sect-SSSD_User_Guide-Additional_Resources-Manual_Pages">8.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"
id="sect-SSSD_User_Guide-Additional_Resources-Mailing_Lists">8.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">...
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"
id="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">8.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="en-US"
class="chapter" id="ch-OpenSSH" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 9. OpenSSH</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-ssh-protocol">9.1. The SSH
Protocol</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-why">9.1.1. Why Use
SSH?</a></span></dt><dt><span
class="section"><a href="#s2-ssh-features">9.1.2. Main
Features</a></span></dt><dt><span
class="section"><a href="#s2-ssh-versions">9.1.3. Protocol
Versions</a></span></dt><dt><span
class="section"><a href="#s2-ssh-conn">9.1.4. Event Sequence
of an SSH
Connection</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-configuration">9.2. An
OpenSSH
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-ssh-configuration-configs">9.2.1. Configuration
Files</a></span></dt><dt><span
class="section"><a href="#s2-ssh-configuration-sshd">9.2.2.
Starting an Op
enSSH Server</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-requiring">9.2.3. Requiring SSH for Remote
Connections</a></span></dt><dt><span
class="section"><a
href="#s2-ssh-configuration-keypairs">9.2.4. Using a Key-Based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-clients">9.3. OpenSSH
Clients</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-clients-ssh">9.3.1. Using
the ssh Utility</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-scp">9.3.2. Using
the <code class="command">scp</code>
Utility</a></span></dt><dt><span
class="section"><a href="#s2-ssh-clients-sftp">9.3.3. Using
the <code class="command">sftp</code>
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-ssh-beyondshell">9.4. More Than
a Secure Shell</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ssh-beyondshell-x11">9.4.1. X11
Forwarding</a></span></dt><dt><span
class="section"><a h
ref="#s2-ssh-beyondshell-tcpip">9.4.2. Port
Forwarding</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-openssh-additional-resources">9.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-openssh-installed-docs">9.5.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-openssh-useful-websites">9.5.2.
Useful
Websites</a></span></dt></dl></dd></dl></div><a
id="id833789" class="indexterm"></a><div
class="para">
+ <code class="systemitem">SSH</code> (Secure Shell) is a protocol
which facilitates secure communications between two systems using a client/server
architecture and allows users to log into server host systems remotely. Unlike other
remote communication protocols, such as <code
class="systemitem">FTP</code> or <code
class="systemitem">Telnet</code>, SSH encrypts the login session,
rendering the connection difficult for intruders to collect unencrypted passwords.
+ </div><div class="para">
+ The <span
class="application"><strong>ssh</strong></span> program is
designed to replace older, less secure terminal applications used to log into remote
hosts, such as <code class="command">telnet</code> or <code
class="command">rsh</code>. A related program called <code
class="command">scp</code> replaces older programs designed to copy
files between hosts, such as <code class="command">rcp</code>.
Because these older applications do not encrypt passwords transmitted between the client
and the server, avoid them whenever possible. Using secure methods to log into remote
systems decreases the risks for both the client system and the remote host.
+ </div><div class="para">
+ Fedora includes the general OpenSSH package (<span
class="package">openssh</span>) as well as the OpenSSH server (<span
class="package">openssh-server</span>) and client (<span
class="package">openssh-clients</span>) packages. Note that the OpenSSH
packages require the OpenSSL package (<span
class="package">openssl</span>), which installs several important
cryptographic libraries, enabling OpenSSH to provide encrypted communications.
+ </div><div class="section" id="s1-ssh-protocol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-ssh-protocol">9.1. The SSH
Protocol</h2></div></div></div><div class="section"
id="s2-ssh-why"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-why">9.1.1. Why Use
SSH?</h3></div></div></div><a id="id1461039"
class="indexterm"></a><div class="para">
+ Potential intruders have a variety of tools at their disposal enabling them to
disrupt, intercept, and re-route network traffic in an effort to gain access to a system.
In general terms, these threats can be categorized as follows:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">Interception of
communication between two systems</span></dt><dd><div
class="para">
+ The attacker can be somewhere on the network between the communicating parties,
copying any information passed between them. He may intercept and keep the information, or
alter the information and send it on to the intended recipient.
+ </div><div class="para">
+ This attack is usually performed using a <em
class="firstterm">packet sniffer</em>, a rather common network utility
that captures each packet flowing through the network, and analyzes its content.
+ </div></dd><dt class="varlistentry"><span
class="term">Impersonation of a particular
host</span></dt><dd><div class="para">
+ Attacker's system is configured to pose as the intended recipient of a
transmission. If this strategy works, the user's system remains unaware that it is
communicating with the wrong host.
+ </div><div class="para">
+ This attack can be performed using a technique known as <em
class="firstterm">DNS poisoning</em>, or via so-called <em
class="firstterm">IP spoofing</em>. In the first case, the intruder
uses a cracked DNS server to point client systems to a maliciously duplicated host. In the
second case, the intruder sends falsified network packets that appear to be from a trusted
host.
+ </div></dd></dl></div><div class="para">
+ Both techniques intercept potentially sensitive information and, if the interception
is made for hostile reasons, the results can be disastrous. If SSH is used for remote
shell login and file copying, these security threats can be greatly diminished. This is
because the SSH client and server use digital signatures to verify their identity.
Additionally, all communication between the client and server systems is encrypted.
Attempts to spoof the identity of either side of a communication does not work, since each
packet is encrypted using a key known only by the local and remote systems.
+ </div></div><div class="section"
id="s2-ssh-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-features">9.1.2. Main
Features</h3></div></div></div><a id="id1459274"
class="indexterm"></a><a id="id1459286"
class="indexterm"></a><div class="para">
+ The SSH protocol provides the following safeguards:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">No one can pose as
the intended server</span></dt><dd><div class="para">
+ After an initial connection, the client can verify that it is connecting to the
same server it had connected to previously.
+ </div></dd><dt class="varlistentry"><span
class="term">No one can capture the authentication
information</span></dt><dd><div class="para">
+ The client transmits its authentication information to the server using strong,
128-bit encryption.
+ </div></dd><dt class="varlistentry"><span
class="term">No one can intercept the
communication</span></dt><dd><div class="para">
+ All data sent and received during a session is transferred using 128-bit
encryption, making intercepted transmissions extremely difficult to decrypt and read.
+ </div></dd></dl></div><div class="para">
+ Additionally, it also offers the following options:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">It provides secure
means to use graphical applications over a
network</span></dt><dd><div class="para">
+ Using a technique called <em class="firstterm">X11
forwarding</em>, the client can forward <em
class="firstterm">X11</em> (<em class="firstterm">X
Window System</em>) applications from the server.
+ </div></dd><dt class="varlistentry"><span
class="term">It provides a way to secure otherwise insecure
protocols</span></dt><dd><div class="para">
+ The SSH protocol encrypts everything it sends and receives. Using a technique
called <em class="firstterm">port forwarding</em>, an SSH server can
become a conduit to securing otherwise insecure protocols, like <acronym
class="acronym">POP</acronym>, and increasing overall system and data
security.
+ </div></dd><dt class="varlistentry"><span
class="term">It can be used to create a secure
channel</span></dt><dd><div class="para">
+ The OpenSSH server and client can be configured to create a tunnel similar to a
virtual private network for traffic between server and client machines.
+ </div></dd><dt class="varlistentry"><span
class="term">It supports the Kerberos
authentication</span></dt><dd><div class="para">
+ OpenSSH servers and clients can be configured to authenticate using the
<acronym class="acronym">GSSAPI</acronym> (Generic Security Services
Application Program Interface) implementation of the Kerberos network authentication
protocol.
+ </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"
id="s2-ssh-versions">9.1.3. Protocol
Versions</h3></div></div></div><a id="id590561"
class="indexterm"></a><a id="id590573"
class="indexterm"></a><div class="para">
+ Two varieties of SSH currently exist: version 1, and newer version 2. The OpenSSH
suite under Fedora uses SSH version 2, which has an enhanced key exchange algorithm not
vulnerable to the known exploit in version 1. However, for compatibility reasons, the
OpenSSH suite does support version 1 connections as well.
+ </div><div class="important"><div
class="admonition_header"><h2>Avoid using SSH version
1</h2></div><div class="admonition"><div
class="para">
+ To ensure maximum security for your connection, it is recommended that only SSH
version 2-compatible servers and clients are used whenever possible.
+ </div></div></div></div><div class="section"
id="s2-ssh-conn"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-conn">9.1.4. Event Sequence of an SSH
Connection</h3></div></div></div><a id="id962484"
class="indexterm"></a><div class="para">
+ The following series of events help protect the integrity of SSH communication
between two hosts.
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ A cryptographic handshake is made so that the client can verify that it is
communicating with the correct server.
+ </div></li><li class="listitem"><div
class="para">
+ The transport layer of the connection between the client and remote host is
encrypted using a symmetric cipher.
+ </div></li><li class="listitem"><div
class="para">
+ The client authenticates itself to the server.
+ </div></li><li class="listitem"><div
class="para">
+ The remote client interacts with the remote host over the encrypted connection.
+ </div></li></ol></div><div class="section"
id="s2-ssh-protocol-conn-transport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s2-ssh-protocol-conn-transport">9.1.4.1. Transport
Layer</h4></div></div></div><a id="id805650"
class="indexterm"></a><div class="para">
+ The primary role of the transport layer is to facilitate safe and secure
communication between the two hosts at the time of authentication and during subsequent
communication. The transport layer accomplishes this by handling the encryption and
decryption of data, and by providing integrity protection of data packets as they are sent
and received. The transport layer also provides compression, speeding the transfer of
information.
+ </div><div class="para">
+ Once an SSH client contacts a server, key information is exchanged so that the two
systems can correctly construct the transport layer. The following steps occur during this
exchange:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Keys are exchanged
+ </div></li><li class="listitem"><div
class="para">
+ The public key encryption algorithm is determined
+ </div></li><li class="listitem"><div
class="para">
+ The symmetric encryption algorithm is determined
+ </div></li><li class="listitem"><div
class="para">
+ The message authentication algorithm is determined
+ </div></li><li class="listitem"><div
class="para">
+ The hash algorithm is determined
+ </div></li></ul></div><div class="para">
+ During the key exchange, the server identifies itself to the client with a unique
<em class="firstterm">host key</em>. If the client has never
communicated with this particular server before, the server's host key is unknown to
the client and it does not connect. OpenSSH gets around this problem by accepting the
server's host key. This is done after the user is notified and has both accepted and
verified the new host key. In subsequent connections, the server's host key is checked
against the saved version on the client, providing confidence that the client is indeed
communicating with the intended server. If, in the future, the host key no longer matches,
the user must remove the client's saved version before a connection can occur.
+ </div><div class="warning"><div
class="admonition_header"><h2>Always verify the integrity of a new SSH
server</h2></div><div class="admonition"><div
class="para">
+ It is possible for an attacker to masquerade as an SSH server during the initial
contact since the local system does not know the difference between the intended server
and a false one set up by an attacker. To help prevent this, verify the integrity of a new
SSH server by contacting the server administrator before connecting for the first time or
in the event of a host key mismatch.
+ </div></div></div><div class="para">
+ SSH is designed to work with almost any kind of public key algorithm or encoding
format. After an initial key exchange creates a hash value used for exchanges and a shared
secret value, the two systems immediately begin calculating new keys and algorithms to
protect authentication and future data sent over the connection.
+ </div><div class="para">
+ After a certain amount of data has been transmitted using a given key and algorithm
(the exact amount depends on the SSH implementation), another key exchange occurs,
generating another set of hash values and a new shared secret value. Even if an attacker
is able to determine the hash and shared secret value, this information is only useful for
a limited period of time.
+ </div></div><div class="section"
id="s2-ssh-protocol-authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s2-ssh-protocol-authentication">9.1.4.2. Authentication</h4></div></div></div><a
id="id539885" class="indexterm"></a><div
class="para">
+ Once the transport layer has constructed a secure tunnel to pass information between
the two systems, the server tells the client the different authentication methods
supported, such as using a private key-encoded signature or typing a password. The client
then tries to authenticate itself to the server using one of these supported methods.
+ </div><div class="para">
+ SSH servers and clients can be configured to allow different types of
authentication, which gives each side the optimal amount of control. The server can decide
which encryption methods it supports based on its security model, and the client can
choose the order of authentication methods to attempt from the available options.
+ </div></div><div class="section"
id="s2-ssh-protocol-connection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s2-ssh-protocol-connection">9.1.4.3. Channels</h4></div></div></div><a
id="id536838" class="indexterm"></a><div
class="para">
+ After a successful authentication over the SSH transport layer, multiple channels
are opened via a technique called <em
class="firstterm">multiplexing</em><sup>[<a
id="id764450" href="#ftn.id764450"
class="footnote">2</a>]</sup>. Each of these channels handles
communication for different terminal sessions and for forwarded X11 sessions.
+ </div><div class="para">
+ Both clients and servers can create a new channel. Each channel is then assigned a
different number on each end of the connection. When the client attempts to open a new
channel, the clients sends the channel number along with the request. This information is
stored by the server and is used to direct communication to that channel. This is done so
that different types of sessions do not affect one another and so that when a given
session ends, its channel can be closed without disrupting the primary SSH connection.
+ </div><div class="para">
+ Channels also support <em class="firstterm">flow-control</em>,
which allows them to send and receive data in an orderly fashion. In this way, data is not
sent over the channel until the client receives a message that the channel is open.
+ </div><div class="para">
+ The client and server negotiate the characteristics of each channel automatically,
depending on the type of service the client requests and the way the user is connected to
the network. This allows great flexibility in handling different types of remote
connections without having to change the basic infrastructure of the protocol.
+ </div></div></div></div><div class="section"
id="s1-ssh-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-ssh-configuration">9.2. An OpenSSH
Configuration</h2></div></div></div><div
class="para">
+ In order to perform tasks described in this section, you must have superuser
privileges. To obtain them, log in as <code
class="systemitem">root</code> by typing:
+ </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"
id="s2-ssh-configuration-configs">9.2.1. Configuration
Files</h3></div></div></div><a id="id830725"
class="indexterm"></a><div class="para">
+ There are two different sets of configuration files: those for client programs (that
is, <code class="command">ssh</code>, <code
class="command">scp</code>, and <code
class="command">sftp</code>), and those for the server (the <code
class="command">sshd</code> daemon).
+ </div><a id="id833351"
class="indexterm"></a><div class="para">
+ System-wide SSH configuration information is stored in the <code
class="filename">/etc/ssh/</code> directory. See <a
class="xref"
href="#table-ssh-configuration-configs-system">Table 9.1, “System-wide
configuration files”</a> for a description of its content.
+ </div><div class="table"
id="table-ssh-configuration-configs-system"><h6>Table 9.1. System-wide
configuration files</h6><div class="table-contents"><table
summary="System-wide configuration files"
border="1"><colgroup><col width="38%"
class="filename" /><col width="63%"
class="description" /></colgroup><thead><tr><th>
+ Configuration File
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc/ssh/moduli</code>
+ </td><td>
+ Contains Diffie-Hellman groups used for the Diffie-Hellman key exchange which is
critical for constructing a secure transport layer. When keys are exchanged at the
beginning of an SSH session, a shared, secret value is created which cannot be determined
by either party alone. This value is then used to provide host authentication.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_config</code>
+ </td><td>
+ The default SSH client configuration file. Note that it is overridden by <code
class="filename">~/.ssh/config</code> if it exists.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/sshd_config</code>
+ </td><td>
+ The configuration file for the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_dsa_key</code>
+ </td><td>
+ The DSA private key used by the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code
class="filename">/etc/ssh/ssh_host_dsa_key.pub</code>
+ </td><td>
+ The DSA public key used by the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_key</code>
+ </td><td>
+ The RSA private key used by the <code
class="command">sshd</code> daemon for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_key.pub</code>
+ </td><td>
+ The RSA public key used by the <code
class="command">sshd</code> daemon for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_rsa_key</code>
+ </td><td>
+ The RSA private key used by the <code
class="command">sshd</code> daemon for version 2 of the SSH protocol.
+ </td></tr><tr><td>
+ <code
class="filename">/etc/ssh/ssh_host_rsa_key.pub</code>
+ </td><td>
+ The RSA public key used by the <code
class="command">sshd</code> for version 2 of the SSH protocol.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="id489516"
class="indexterm"></a><div class="para">
+ User-specific SSH configuration information is stored in the user's home
directory within the <code class="filename">~/.ssh/</code>
directory. See <a class="xref"
href="#table-ssh-configuration-configs-user">Table 9.2, “User-specific
configuration files”</a> for a description of its content.
+ </div><div class="table"
id="table-ssh-configuration-configs-user"><h6>Table 9.2. User-specific
configuration files</h6><div class="table-contents"><table
summary="User-specific configuration files"
border="1"><colgroup><col width="38%"
class="filename" /><col width="63%"
class="description" /></colgroup><thead><tr><th>
+ Configuration File
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">~/.ssh/authorized_keys</code>
+ </td><td>
+ Holds a list of authorized public keys for servers. When the client connects to a
server, the server authenticates the client by checking its signed public key stored
within this file.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_dsa</code>
+ </td><td>
+ Contains the DSA private key of the user.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_dsa.pub</code>
+ </td><td>
+ The DSA public key of the user.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_rsa</code>
+ </td><td>
+ The RSA private key used by <code
class="command">ssh</code> for version 2 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_rsa.pub</code>
+ </td><td>
+ The RSA public key used by <code class="command">ssh</code>
for version 2 of the SSH protocol
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/identity</code>
+ </td><td>
+ The RSA private key used by <code
class="command">ssh</code> for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/identity.pub</code>
+ </td><td>
+ The RSA public key used by <code class="command">ssh</code>
for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/known_hosts</code>
+ </td><td>
+ Contains DSA host keys of SSH servers accessed by the user. This file is very
important for ensuring that the SSH client is connecting the correct SSH server.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Refer to the <code class="command">ssh_config</code> and
<code class="command">sshd_config</code> man pages for information
concerning the various directives available in the SSH configuration files.
+ </div></div><div class="section"
id="s2-ssh-configuration-sshd"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-configuration-sshd">9.2.2. Starting an OpenSSH
Server</h3></div></div></div><a id="id1243970"
class="indexterm"></a><div class="note"><div
class="admonition_header"><h2>Make sure you have relevant packages
installed</h2></div><div class="admonition"><div
class="para">
+ To run an OpenSSH server, you must have the <span
class="package">openssh-server</span> and <span
class="package">openssh</span> packages installed. Refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><a id="id566707"
class="indexterm"></a><div class="para">
+ To start the <code class="command">sshd</code> daemon, type the
following at a shell prompt:
+ </div><pre class="screen"><code
class="command">systemctl start sshd.service</code></pre><a
id="id566736" class="indexterm"></a><div
class="para">
+ To stop the running <code class="command">sshd</code> daemon,
use the following command:
+ </div><pre class="screen"><code
class="command">systemctl stop sshd.service</code></pre><div
class="para">
+ If you want the daemon to start automatically at the boot time, type:
+ </div><pre class="screen"><code
class="command">systemctl enable sshd.service</code></pre><div
class="para">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div><div class="para">
+ Note that if you reinstall the system, a new set of identification keys will be
created. As a result, clients who had connected to the system with any of the OpenSSH
tools before the reinstall will see the following message:
+ </div><pre
class="screen">@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
+Someone could be eavesdropping on you right now (man-in-the-middle attack)!
+It is also possible that the RSA host key has just been changed.</pre><div
class="para">
+ To prevent this, you can back up the relevant files from the <code
class="filename">/etc/ssh/</code> directory (see <a
class="xref"
href="#table-ssh-configuration-configs-system">Table 9.1, “System-wide
configuration files”</a> for a complete list), and restore them whenever you
reinstall the system.
+ </div></div><div class="section"
id="s2-ssh-configuration-requiring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-configuration-requiring">9.2.3. Requiring SSH for Remote
Connections</h3></div></div></div><a id="id929661"
class="indexterm"></a><a id="id929673"
class="indexterm"></a><div class="para">
+ For SSH to be truly effective, using insecure connection protocols should be
prohibited. Otherwise, a user's password may be protected using SSH for one session,
only to be captured later while logging in using Telnet. Some services to disable include
<code class="command">telnet</code>, <code
class="command">rsh</code>, <code
class="command">rlogin</code>, and <code
class="command">vsftpd</code>.
+ </div><div class="para">
+ To make sure these services are not running, type the following commands at a shell
prompt:
+ </div><pre class="screen"><code
class="command">systemctl stop telnet.service</code>
+<code class="command">systemctl stop rsh.service</code>
+<code class="command">systemctl stop rlogin.service</code>
+<code class="command">systemctl stop
vsftpd.service</code></pre><div class="para">
+ To disable running these services at startup, type:
+ </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">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s2-ssh-configuration-keypairs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-configuration-keypairs">9.2.4. Using a Key-Based
Authentication</h3></div></div></div><a id="id427626"
class="indexterm"></a><div class="para">
+ To improve the system security even further, you can enforce the key-based
authentication by disabling the standard password authentication. To do so, open the
<code class="filename">/etc/ssh/sshd_config</code> configuration
file in a text editor, and change the <code
class="option">PasswordAuthentication</code> option as follows:
+ </div><pre class="programlisting">PasswordAuthentication
no</pre><div class="para">
+ To be able to use <code class="command">ssh</code>, <code
class="command">scp</code>, or <code
class="command">sftp</code> to connect to the server from a client
machine, generate an authorization key pair by following the steps below. Note that keys
must be generated for each user separately.
+ </div><div class="para">
+ Fedora 15 uses SSH Protocol 2 and RSA keys by default (see <a
class="xref" href="#s2-ssh-versions">Section 9.1.3, “Protocol
Versions”</a> for more information).
+ </div><div class="important"><div
class="admonition_header"><h2>Do not generate key pairs as
root</h2></div><div class="admonition"><div
class="para">
+ If you complete the steps as <code
class="systemitem">root</code>, only <code
class="systemitem">root</code> will be able to use the keys.
+ </div></div></div><div class="note"><div
class="admonition_header"><h2>Backup your ~/.ssh/
directory</h2></div><div class="admonition"><div
class="para">
+ If you reinstall your system and want to keep previously generated key pair, backup
the <code class="filename">~/.ssh/</code> directory. After
reinstalling, copy it back to your home directory. This process can be done for all users
on your system, including <code class="systemitem">root</code>.
+ </div></div></div><div class="section"
id="s3-ssh-configuration-keypairs-generating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ssh-configuration-keypairs-generating">9.2.4.1. Generating Key
Pairs</h4></div></div></div><a id="id642681"
class="indexterm"></a><a id="id642693"
class="indexterm"></a><div class="para">
+ To generate an RSA key pair for version 2 of the SSH protocol, follow these steps:
+ </div><a id="id642712"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Generate an RSA key pair by typing the following at a shell prompt:
+ </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">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location (that is, <code
class="filename">~/.ssh/id_rsa</code>) for the newly created key.
+ </div></li><li class="step"><div
class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so.
For security reasons, avoid using the same password as you use to log in to your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </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(a)penguin.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| E. |
+| . . |
+| o . |
+| . .|
+| S . . |
+| + o o ..|
+| * * +oo|
+| O +..=|
+| o* o.|
++-----------------+</pre></li><li class="step"><div
class="para">
+ Change the permissions of the <code
class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code
class="command">chmod 755 ~/.ssh</code></pre></li><li
class="step"><div class="para">
+ Copy the content of <code
class="filename">~/.ssh/id_rsa.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> on the machine to which
you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step"><div
class="para">
+ Change the permissions of the <code
class="filename">~/.ssh/authorized_keys</code> file using the following
command:
+ </div><pre class="screen">~]$ <code
class="command">chmod 644
~/.ssh/authorized_keys</code></pre></li></ol></div><a
id="id840600" class="indexterm"></a><a
id="id840612" class="indexterm"></a><div
class="para">
+ To generate a DSA key pair for version 2 of the SSH protocol, follow these steps:
+ </div><a id="id893250"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Generate a DSA key pair by typing the following at a shell prompt:
+ </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">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location (that is, <code
class="filename">~/.ssh/id_dsa</code>) for the newly created key.
+ </div></li><li class="step"><div
class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so.
For security reasons, avoid using the same password as you use to log in to your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </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(a)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">
+ Change the permissions of the <code
class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code
class="command">chmod 775 ~/.ssh</code></pre></li><li
class="step"><div class="para">
+ Copy the content of <code
class="filename">~/.ssh/id_dsa.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> on the machine to which
you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step"><div
class="para">
+ Change the permissions of the <code
class="filename">~/.ssh/authorized_keys</code> file using the following
command:
+ </div><pre class="screen">~]$ <code
class="command">chmod 644
~/.ssh/authorized_keys</code></pre></li></ol></div><a
id="id482518" class="indexterm"></a><a
id="id482530" class="indexterm"></a><div
class="para">
+ To generate an RSA key pair for version 1 of the SSH protocol, follow these steps:
+ </div><a id="id568303"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Generate an RSA key pair by typing the following at a shell prompt:
+ </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">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location (that is, <code
class="filename">~/.ssh/identity</code>) for the newly created key.
+ </div></li><li class="step"><div
class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so.
For security reasons, avoid using the same password as you use to log into your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </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(a)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">
+ Change the permissions of the <code
class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code
class="command">chmod 755 ~/.ssh</code></pre></li><li
class="step"><div class="para">
+ Copy the content of <code
class="filename">~/.ssh/identity.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> on the machine to which
you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step"><div
class="para">
+ Change the permissions of the <code
class="filename">~/.ssh/authorized_keys</code> file using the following
command:
+ </div><pre class="screen">~]$ <code
class="command">chmod 644
~/.ssh/authorized_keys</code></pre></li></ol></div><div
class="para">
+ Refer to <a class="xref"
href="#s3-ssh-configuration-keypairs-agent">Section 9.2.4.2, “Configuring
ssh-agent”</a> for information on how to set up your system to remember the
passphrase.
+ </div><div class="important"><div
class="admonition_header"><h2>Never share your private
key</h2></div><div class="admonition"><div
class="para">
+ The private key is for your personal use only, and it is important that you never
give it to anyone.
+ </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"
id="s3-ssh-configuration-keypairs-agent">9.2.4.2. Configuring
ssh-agent</h4></div></div></div><a id="id678474"
class="indexterm"></a><a id="id902617"
class="indexterm"></a><a id="id902629"
class="indexterm"></a><a id="id902645"
class="indexterm"></a><div class="para">
+ To store your passphrase so that you do not have to enter it each time you initiate
a connection with a remote machine, you can use the <code
class="command">ssh-agent</code> authentication agent. To save your
passphrase for a certain shell prompt, use the following command:
+ </div><pre class="screen">~]$ <code
class="command">ssh-add</code>
+Enter passphrase for /home/john/.ssh/id_rsa:</pre><div
class="para">
+ Note that when you log out, your passphrase will be forgotten. You must execute the
command each time you log in to a virtual console or a terminal window.
+ </div></div></div></div><div class="section"
id="s1-ssh-clients"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-ssh-clients">9.3. OpenSSH
Clients</h2></div></div></div><a id="id831395"
class="indexterm"></a><div class="note"><div
class="admonition_header"><h2>Make sure you have relevant packages
installed</h2></div><div class="admonition"><div
class="para">
+ To connect to an OpenSSH server from a client machine, you must have the <span
class="package">openssh-clients</span> and <span
class="package">openssh</span> packages installed. Refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><div class="section"
id="s2-ssh-clients-ssh"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-clients-ssh">9.3.1. Using the ssh
Utility</h3></div></div></div><a id="id654759"
class="indexterm"></a><a id="id654775"
class="indexterm"></a><div class="para">
+ <code class="command">ssh</code> allows you to log in to a
remote machine and execute commands there. It is a secure replacement for the <code
class="command">rlogin</code>, <code
class="command">rsh</code>, and <code
class="command">telnet</code> programs.
+ </div><div class="para">
+ Similarly to <code class="command">telnet</code>, to log in to
a remote machine named <code
class="systemitem">penguin.example.com</code>, type the following
command at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">ssh penguin.example.com</code></pre><div
class="para">
+ This will log you in with the same username you are using on a local machine. If you
want to specify a different one, use a command in the <code
class="command">ssh <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code>
form. For example, to log in as <code
class="systemitem">john</code>, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh john(a)penguin.example.com</code></pre><div
class="para">
+ The first time you initiate a connection, you will be presented with a message
similar to this:
+ </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">
+ Type <strong
class="userinput"><code>yes</code></strong> to confirm. You
will see a notice that the server has been added to the list of known hosts, and a prompt
asking for your password:
+ </div><pre class="screen">Warning: Permanently added
'penguin.example.com' (RSA) to the list of known hosts.
+john(a)penguin.example.com's password:</pre><div
class="important"><div
class="admonition_header"><h2>Updating the host key of an SSH
server</h2></div><div class="admonition"><div
class="para">
+ If the SSH server's host key changes, the client notifies the user that the
connection cannot proceed until the server's host key is deleted from the <code
class="filename">~/.ssh/known_hosts</code> file. To do so, open the
file in a text editor, and remove a line containing the remote machine name at the
beginning. Before doing this, however, contact the system administrator of the SSH server
to verify the server is not compromised.
+ </div></div></div><div class="para">
+ After entering the password, you will be provided with a shell prompt for the remote
machine.
+ </div><div class="para">
+ Alternatively, the <code class="command">ssh</code> program can
be used to execute a command on the remote machine without logging in to a shell prompt.
The syntax for that is <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>.
For example, if you want to execute the <code
class="command">whoami</code> command on <code
class="systemitem">penguin.example.com</code>, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh john(a)penguin.example.com whoami</code>
+john(a)penguin.example.com's password:
+john</pre><div class="para">
+ After you enter the correct password, the username will be displayed, and you will
return to your local shell prompt.
+ </div></div><div class="section"
id="s2-ssh-clients-scp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-clients-scp">9.3.2. Using the <code
class="command">scp</code>
Utility</h3></div></div></div><a id="id429251"
class="indexterm"></a><a id="id410476"
class="indexterm"></a><a id="id410496"
class="indexterm"></a><div class="para">
+ <code class="command">scp</code> can be used to transfer files
between machines over a secure, encrypted connection. In its design, it is very similar to
<code class="command">rcp</code>.
+ </div><div class="para">
+ To transfer a local file to a remote system, use a command in the following form:
+ </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">
+ For example, if you want to transfer <code
class="filename">taglist.vim</code> to a remote machine named <code
class="systemitem">penguin.example.com</code>, type the following at a
shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">scp taglist.vim
john@penguin.example.com:.vim/plugin/taglist.vim</code>
+john(a)penguin.example.com's password:
+taglist.vim 100% 144KB 144.5KB/s
00:00</pre><div class="para">
+ Multiple files can be specified at once. To transfer the contents of <code
class="filename">.vim/plugin/</code> to the same directory on the
remote machine <code class="systemitem">penguin.example.com</code>,
type the following command:
+ </div><pre class="screen">~]$ <code
class="command">scp .vim/plugin/*
john@penguin.example.com:.vim/plugin/</code>
+john(a)penguin.example.com's password:
+closetag.vim 100% 13KB 12.6KB/s 00:00
+snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
+taglist.vim 100% 144KB 144.5KB/s
00:00</pre><div class="para">
+ To transfer a remote file to the local system, use the following syntax:
+ </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">
+ For instance, to download the <code
class="filename">.vimrc</code> configuration file from the remote
machine, type:
+ </div><pre class="screen">~]$ <code
class="command">scp john@penguin.example.com:.vimrc .vimrc</code>
+john(a)penguin.example.com's password:
+.vimrc 100% 2233 2.2KB/s
00:00</pre></div><div class="section"
id="s2-ssh-clients-sftp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-clients-sftp">9.3.3. Using the <code
class="command">sftp</code>
Utility</h3></div></div></div><a id="id769735"
class="indexterm"></a><a id="id583135"
class="indexterm"></a><div class="para">
+ The <code class="command">sftp</code> utility can be used to
open a secure, interactive FTP session. In its design, it is similar to <code
class="command">ftp</code> except that it uses a secure, encrypted
connection.
+ </div><div class="para">
+ To connect to a remote system, use a command in the following form:
+ </div><pre class="screen"><code
class="command">sftp <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code> with <code
class="systemitem">john</code> as a username, type:
+ </div><pre class="screen">~]$ <code
class="command">sftp john(a)penguin.example.com</code>
+john(a)penguin.example.com's password:
+Connected to
penguin.example.com.
+sftp></pre><div class="para">
+ After you enter the correct password, you will be presented with a prompt. The
<code class="command">sftp</code> utility accepts a set of commands
similar to those used by <code class="command">ftp</code> (see <a
class="xref" href="#table-ssh-clients-sftp">Table 9.3, “A selection
of available sftp commands”</a>).
+ </div><div class="table"
id="table-ssh-clients-sftp"><h6>Table 9.3. A selection of available
sftp commands</h6><div class="table-contents"><table
summary="A selection of available sftp commands"
border="1"><colgroup><col width="38%"
class="command" /><col width="63%" class="description"
/></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">ls</code> [<em
class="replaceable"><code>directory</code></em>]
+ </td><td>
+ List the content of a remote <em
class="replaceable"><code>directory</code></em>. If none is
supplied, a current working directory is used by default.
+ </td></tr><tr><td>
+ <code class="command">cd</code> <em
class="replaceable"><code>directory</code></em>
+ </td><td>
+ Change the remote working directory to <em
class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">mkdir</code> <em
class="replaceable"><code>directory</code></em>
+ </td><td>
+ Create a remote <em
class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">rmdir</code> <em
class="replaceable"><code>path</code></em>
+ </td><td>
+ Remove a remote <em
class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">put</code> <em
class="replaceable"><code>localfile</code></em> [<em
class="replaceable"><code>remotefile</code></em>]
+ </td><td>
+ Transfer <em
class="replaceable"><code>localfile</code></em> to a remote
machine.
+ </td></tr><tr><td>
+ <code class="command">get</code> <em
class="replaceable"><code>remotefile</code></em> [<em
class="replaceable"><code>localfile</code></em>]
+ </td><td>
+ Transfer <em
class="replaceable"><code>remotefile</code></em> from a
remote machine.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For a complete list of available commands, refer to the <code
class="command">sftp</code> man page.
+ </div></div></div><div class="section"
id="s1-ssh-beyondshell"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-ssh-beyondshell">9.4. More Than a Secure
Shell</h2></div></div></div><div class="para">
+ A secure command line interface is just the beginning of the many ways SSH can be
used. Given the proper amount of bandwidth, X11 sessions can be directed over an SSH
channel. Or, by using TCP/IP forwarding, previously insecure port connections between
systems can be mapped to specific SSH channels.
+ </div><div class="section"
id="s2-ssh-beyondshell-x11"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-beyondshell-x11">9.4.1. X11
Forwarding</h3></div></div></div><a id="id453899"
class="indexterm"></a><div class="para">
+ To open an X11 session over an SSH connection, use a command in the following form:
+ </div><pre class="screen"><code
class="command">ssh -Y <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code> with <code
class="systemitem">john</code> as a username, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh -Y john(a)penguin.example.com</code>
+john(a)penguin.example.com's password:</pre><div class="para">
+ When an X program is run from the secure shell prompt, the SSH client and server
create a new secure channel, and the X program data is sent over that channel to the
client machine transparently.
+ </div><div class="para">
+ X11 forwarding can be very useful. For example, X11 forwarding can be used to create
a secure, interactive session of the <span
class="application"><strong>Printer
Configuration</strong></span> utility. To do this, connect to the server using
<span class="application"><strong>ssh</strong></span>
and type:
+ </div><pre class="screen">~]$ <code
class="command">system-config-printer
&</code></pre><div class="para">
+ The <span class="application"><strong>Printer Configuration
Tool</strong></span> will appear, allowing the remote user to safely configure
printing on the remote system.
+ </div></div><div class="section"
id="s2-ssh-beyondshell-tcpip"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-beyondshell-tcpip">9.4.2. Port
Forwarding</h3></div></div></div><a id="id942456"
class="indexterm"></a><div class="para">
+ SSH can secure otherwise insecure <code
class="systemitem">TCP/IP</code> protocols via port forwarding. When
using this technique, the SSH server becomes an encrypted conduit to the SSH client.
+ </div><div class="para">
+ Port forwarding works by mapping a local port on the client to a remote port on the
server. SSH can map any port from the server to any port on the client. Port numbers do
not need to match for this technique to work.
+ </div><div class="note"><div
class="admonition_header"><h2>Using reserved port
numbers</h2></div><div class="admonition"><div
class="para">
+ Setting up port forwarding to listen on ports below 1024 requires root level
access.
+ </div></div></div><div class="para">
+ To create a TCP/IP port forwarding channel which listens for connections on the
<code class="systemitem">localhost</code>, use a command in the
following form:
+ </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">
+ For example, to check email on a server called <code
class="systemitem">mail.example.com</code> using <code
class="systemitem">POP3</code> through an encrypted connection, use the
following command:
+ </div><pre class="screen">~]$ <code
class="command">ssh -L 1100:mail.example.com:110
mail.example.com</code></pre><div class="para">
+ Once the port forwarding channel is in place between the client machine and the mail
server, direct a POP3 mail client to use port <code
class="literal">1100</code> on the <code
class="systemitem">localhost</code> to check for new email. Any
requests sent to port <code class="literal">1100</code> on the
client system will be directed securely to the <code
class="systemitem">mail.example.com</code> server.
+ </div><div class="para">
+ If <code class="systemitem">mail.example.com</code> is not
running an SSH server, but another machine on the same network is, SSH can still be used
to secure part of the connection. However, a slightly different command is necessary:
+ </div><pre class="screen">~]$ <code
class="command">ssh -L 1100:mail.example.com:110
other.example.com</code></pre><div class="para">
+ In this example, POP3 requests from port <code
class="literal">1100</code> on the client machine are forwarded through
the SSH connection on port <code class="literal">22</code> to the
SSH server, <code class="systemitem">other.example.com</code>. Then,
<code class="systemitem">other.example.com</code> connects to port
<code class="literal">110</code> on <code
class="systemitem">mail.example.com</code> to check for new email. Note
that when using this technique, only the connection between the client system and <code
class="systemitem">other.example.com</code> SSH server is secure.
+ </div><div class="para">
+ Port forwarding can also be used to get information securely through network
firewalls. If the firewall is configured to allow SSH traffic via its standard port (that
is, port 22) but blocks access to other ports, a connection between two hosts using the
blocked ports is still possible by redirecting their communication over an established SSH
connection.
+ </div><div class="important"><div
class="admonition_header"><h2>A connection is only as secure as a
client system</h2></div><div class="admonition"><div
class="para">
+ Using port forwarding to forward connections in this manner allows any user on the
client system to connect to that service. If the client system becomes compromised, the
attacker also has access to forwarded services.
+ </div><div class="para">
+ System administrators concerned about port forwarding can disable this functionality
on the server by specifying a <code class="option">No</code>
parameter for the <code class="option">AllowTcpForwarding</code>
line in <code class="filename">/etc/ssh/sshd_config</code> and
restarting the <code class="command">sshd</code> service.
+ </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"
id="s1-openssh-additional-resources">9.5. Additional
Resources</h2></div></div></div><a id="id617347"
class="indexterm"></a><a id="id528959"
class="indexterm"></a><div class="para">
+ The OpenSSH and OpenSSL projects are in constant development, and the most up-to-date
information for them is available from their websites. The man pages for OpenSSH and
OpenSSL tools are also good sources of detailed information.
+ </div><div class="section"
id="s2-openssh-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-openssh-installed-docs">9.5.1. Installed
Documentation</h3></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><code
class="command">man ssh</code></span></dt><dd><div
class="para">
+ The manual page for <span
class="application"><strong>ssh</strong></span> containing
the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
scp</code></span></dt><dd><div class="para">
+ The manual page for <span
class="application"><strong>scp</strong></span> containing
the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
sftp</code></span></dt><dd><div class="para">
+ The manual page for <span
class="application"><strong>sftp</strong></span> containing
the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
sshd</code></span></dt><dd><div class="para">
+ The manual page for <span
class="application"><strong>sshd</strong></span> containing
the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
ssh-keygen</code></span></dt><dd><div
class="para">
+ The manual page for <span
class="application"><strong>ssh-keygen</strong></span>
containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
ssh_config</code></span></dt><dd><div
class="para">
+ The manual page with full description of available SSH client configuration
options.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
sshd_config</code></span></dt><dd><div
class="para">
+ The manual page with full description of available SSH daemon configuration
options.
+ </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"
id="s2-openssh-useful-websites">9.5.2. Useful
Websites</h3></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://www.openssh.com/">http://www.openssh.com/</a...
class="para">
+ The OpenSSH home page containing further documentation, frequently asked
questions, links to the mailing lists, bug reports, and other useful resources.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.openssl.org/">http://www.openssl.org/</a...
class="para">
+ The OpenSSL home page containing further documentation, frequently asked
questions, links to the mailing lists, and other useful resources.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.freesshd.com/">http://www.freesshd.com/<...
class="para">
+ Another implementation of an SSH server.
+ </div></dd></dl></div></div></div><div
class="footnotes"><br /><hr width="100"
align="left" /><div class="footnote"><div
class="para"><sup>[<a id="ftn.id764450"
href="#id764450" class="para">2</a>] </sup>
+ A multiplexed connection consists of several signals being sent over a shared,
common medium. With SSH, different channels are sent over a common secure connection.
+ </div></div></div></div></div><div
class="part" id="part-Servers"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part V. Servers</h1></div></div></div><div
class="partintro" id="id393170"><div></div><div
class="para">
+ This part discusses various topics related to servers such as how to set up a Web
server or share files and directories over the network.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a href="#ch-DHCP_Servers">10. DHCP
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-dhcp-why">10.1. Why Use
DHCP?</a></span></dt><dt><span
class="section"><a href="#s1-dhcp-configuring-server">10.2.
Configuring a DHCP
Server</a></span></dt><dd><dl><dt><span
class="section"><a href="#config-file">10.2.1. Configuration
File</a></span></dt><dt><span
class="section"><a href="#lease-database">10.2.2. Lease
Database</a></span></dt><dt><span
class="section"><a href="#id619308">10.2.3. Starting and
Stopping the Server</a></span></dt><dt><span
class="section"><a href="#dhcp-relay-agent">10.2.4. DHCP
Relay Agent</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-dhcp-configuring-client">10.3.
Configuring a DHCP Client</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_a_Multihomed_DHCP_Server">10.4. Configuring a
Multihomed DHCP Server</a
</span></dt><dd><dl><dt><span
class="section"><a
href="#sect-dns_Host_Configuration">10.4.1. Host
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">10.5. DHCP
for IPv6 (DHCPv6)</a></span></dt><dt><span
class="section"><a href="#s1-dhcp-additional-resources">10.6.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-dhcp-installed-docs">10.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-DNS_Servers">11. DNS
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Introduction_to_DNS">11.1.
Introduction to
DNS</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-dns-introduction-zones">11.1.1.
Nameserver Zones</a></span></dt><dt><span
class="section"><a
href="#s2-dns-introduction-nameservers">11.1.2. Nameserver
Types</a></span></dt><dt><span
class="section"><a href="#s2-dns-introduction-bind">11.1.3.
BIND as a Nameserver<
/a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-BIND">11.2.
BIND</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-bind-namedconf">11.2.1.
Configuring the named Service</a></span></dt><dt><span
class="section"><a href="#s2-bind-zone">11.2.2. Editing Zone
Files</a></span></dt><dt><span
class="section"><a href="#s2-bind-rndc">11.2.3. Using the
rndc Utility</a></span></dt><dt><span
class="section"><a href="#s2-bind-dig">11.2.4. Using the dig
Utility</a></span></dt><dt><span
class="section"><a href="#s2-bind-features">11.2.5. Advanced
Features of BIND</a></span></dt><dt><span
class="section"><a href="#s2-bind-mistakes">11.2.6. Common
Mistakes to Avoid</a></span></dt><dt><span
class="section"><a
href="#s2-bind-additional-resources">11.2.7. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Web_Servers">12. Web
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-The_Apache_HTTP_Server">12.1.
The Apache HTTP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-apache-version2-features">12.1.1. New
Features</a></span></dt><dt><span
class="section"><a href="#s2-apache-version2-changes">12.1.2.
Notable Changes</a></span></dt><dt><span
class="section"><a
href="#s2-apache-version2-migrating">12.1.3. Updating the
Configuration</a></span></dt><dt><span
class="section"><a href="#s2-apache-running">12.1.4. Running
the httpd Service</a></span></dt><dt><span
class="section"><a href="#s2-apache-editing">12.1.5. Editing
the Configuration Files</a></span></dt><dt><span
class="section"><a href="#s2-apache-dso">12.1.6. Working with
Modules</a></span></dt><dt><span
class="section"><a href="#s2-apache-virtualhosts">12.1.7.
Setting Up Virtual Hosts</a></span></dt><dt><span
class="section"><a href="#s2-apache-mod_ssl">12.1.8. Setting
Up an SSL Server</a></span></dt><dt><span
class="section"><a href="#s2-apache-resources">12.1.9.
Additional Resources</a></span></dt></
dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Mail_Servers">13. Mail
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-email-protocols">13.1. Email
Protocols</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-protocols-send">13.1.1.
Mail Transport Protocols</a></span></dt><dt><span
class="section"><a href="#s2-email-protocols-client">13.1.2.
Mail Access
Protocols</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-types">13.2. Email Program
Classifications</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-types-mta">13.2.1. Mail
Transport Agent</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mda">13.2.2. Mail
Delivery Agent</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mua">13.2.3. Mail
User Agent</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mta">13.3. Mail Transport
Agents</a></span></dt><dd><dl><dt><span
class="section"><a href=
"#s2-email-mta-postfix">13.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-sendmail">13.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-fetchmail">13.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="#s2-email-switchmail">13.3.4. Mail
Transport Agent (MTA)
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mda">13.4. Mail Delivery
Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-email-procmail-configuration">13.4.1. Procmail
Configuration</a></span></dt><dt><span
class="section"><a href="#s2-email-procmail-recipes">13.4.2.
Procmail Recipes</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mua">13.5. Mail User
Agents</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-security">13.5.1. Securing
Communication</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-email-additional-resources">13.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-installed-docs">13.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-email-useful-websites">13.6.2.
Useful Websites</a></span></dt><dt><span
class="section"><a href="#s2-email-related-books">13.6.3.
Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Directory_Servers">14. Directory
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-OpenLDAP">14.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ldap-introduction">14.1.1.
Introduction to LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-installation">14.1.2.
Installing the OpenLDAP Suite</a></span></dt><dt><span
class="section"><a href="#s2-ldap-configuration">14.1.3.
Configuring an OpenLDAP Server</a></span></dt><dt><span
class="section"><a href="#s2-ldap-running">14.1.4. Running an
OpenLDAP Server</a></span></dt><dt><span c
lass="section"><a href="#s2-ldap-pam">14.1.5. Configuring a
System to Authenticate Using OpenLDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-resources">14.1.6.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-File_and_Print_Servers">15. File
Servers</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-Samba">15.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a href="#samba-rgs-overview">15.1.1.
Introduction to Samba</a></span></dt><dt><span
class="section"><a href="#s2-samba-daemons">15.1.2. Samba
Daemons and Related Services</a></span></dt><dt><span
class="section"><a href="#s2-samba-connect-share">15.1.3.
Connecting to a Samba Share</a></span></dt><dt><span
class="section"><a href="#s2-samba-configuring">15.1.4.
Configuring a Samba Server</a></span></dt><dt><span
class="section"><a href="#s2-samba-startstop">15.1.5.
Starting and Stopping Samba</a></span></dt><dt><span
class="section"><a href=
"#s2-samba-servers">15.1.6. Samba Server Types and the <code
class="filename">smb.conf</code>
File</a></span></dt><dt><span
class="section"><a href="#s2-samba-security-modes">15.1.7.
Samba Security Modes</a></span></dt><dt><span
class="section"><a href="#s2-samba-account-info-dbs">15.1.8.
Samba Account Information Databases</a></span></dt><dt><span
class="section"><a href="#s2-samba-network-browsing">15.1.9.
Samba Network Browsing</a></span></dt><dt><span
class="section"><a href="#s2-samba-cups">15.1.10. Samba with
CUPS Printing Support</a></span></dt><dt><span
class="section"><a href="#s2-samba-programs">15.1.11. Samba
Distribution Programs</a></span></dt><dt><span
class="section"><a href="#s2-samba-resources">15.1.12.
Additional
Resources</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-FTP">15.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ftp-protocol">15.2.1. The File
Transfer Protocol</a></span></dt><dt><span
class="section"><a href
="#s2-ftp-servers">15.2.2. FTP
Servers</a></span></dt><dt><span
class="section"><a href="#s3-ftp-vsftpd-conf">15.2.3. Files
Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-start">15.2.4. Starting and Stopping <code
class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-conf">15.2.5. <code
class="command">vsftpd</code> Configuration
Options</a></span></dt><dt><span
class="section"><a href="#s2-ftp-resources">15.2.6.
Additional
Resources</a></span></dt></dl></dd></dl></dd></dl></div></div><div
xml:lang="en-US" class="chapter" id="ch-DHCP_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 10. DHCP
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-dhcp-why">10.1. Why Use
DHCP?</a></span></dt><dt><span
class="section"><a href="#s1-dhcp-configuring-server">10.2.
Configuring a DHCP Server</a></span></d
t><dd><dl><dt><span class="section"><a
href="#config-file">10.2.1. Configuration
File</a></span></dt><dt><span
class="section"><a href="#lease-database">10.2.2. Lease
Database</a></span></dt><dt><span
class="section"><a href="#id619308">10.2.3. Starting and
Stopping the Server</a></span></dt><dt><span
class="section"><a href="#dhcp-relay-agent">10.2.4. DHCP
Relay Agent</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-dhcp-configuring-client">10.3.
Configuring a DHCP Client</a></span></dt><dt><span
class="section"><a
href="#sect-Configuring_a_Multihomed_DHCP_Server">10.4. Configuring a
Multihomed DHCP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sect-dns_Host_Configuration">10.4.1. Host
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">10.5. DHCP
for IPv6 (DHCPv6)</a></span></dt><dt><span
class="section"><a href="#s1-dhcp-additional-resources">10.6.
Additional Resources</a></span></dt><dd><d
l><dt><span class="section"><a
href="#s2-dhcp-installed-docs">10.6.1. Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id800604" class="indexterm"></a><a
id="id415066" class="indexterm"></a><div
class="para">
+ Dynamic Host Configuration Protocol (<acronym
class="acronym">DHCP</acronym>) is a network protocol that
automatically assigns TCP/IP information to client machines. Each DHCP client connects to
the centrally located DHCP server, which returns that client's network configuration
(including the IP address, gateway, and DNS servers).
+ </div><div class="section" id="s1-dhcp-why"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-dhcp-why">10.1. Why Use
DHCP?</h2></div></div></div><a id="id505839"
class="indexterm"></a><div class="para">
+ DHCP is useful for automatic configuration of client network interfaces. When
configuring the client system, the administrator chooses DHCP instead of specifying an IP
address, netmask, gateway, or DNS servers. The client retrieves this information from the
DHCP server. DHCP is also useful if an administrator wants to change the IP addresses of a
large number of systems. Instead of reconfiguring all the systems, he can just edit one
DHCP configuration file on the server for the new set of IP addresses. If the DNS servers
for an organization changes, the changes are made on the DHCP server, not on the DHCP
clients. When the administrator restarts the network or reboots the clients, the changes
will go into effect.
+ </div><div class="para">
+ If an organization has a functional DHCP server properly connected to a network,
laptops and other mobile computer users can move these devices from office to office.
+ </div></div><div class="section"
id="s1-dhcp-configuring-server"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-dhcp-configuring-server">10.2. Configuring a DHCP
Server</h2></div></div></div><a id="id1278580"
class="indexterm"></a><div class="para">
+ The <code class="filename">dhcp</code> package contains an ISC
DHCP server. First, install the package as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">yum install dhcp</code></pre><div
class="para">
+ Installing the <code class="filename">dhcp</code> package
creates a file, <code class="filename">/etc/dhcp/dhcpd.conf</code>,
which is merely an empty configuration file:
+ </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">
+ The sample configuration file can be found at <code
class="filename">/usr/share/doc/dhcp-<em
class="replaceable"><code>version</code></em>/dhcpd.conf.sample</code>.
You should use this file to help you configure <code
class="filename">/etc/dhcp/dhcpd.conf</code>, which is explained in
detail below.
+ </div><div class="para">
+ DHCP also uses the file <code
class="filename">/var/lib/dhcpd/dhcpd.leases</code> to store the client
lease database. Refer to <a class="xref"
href="#lease-database">Section 10.2.2, “Lease Database”</a> for more
information.
+ </div><div class="section" id="config-file"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="config-file">10.2.1. Configuration
File</h3></div></div></div><a id="id707215"
class="indexterm"></a><a id="id707228"
class="indexterm"></a><div class="para">
+ The first step in configuring a DHCP server is to create the configuration file that
stores the network information for the clients. Use this file to declare options and
global options for client systems.
+ </div><div class="para">
+ The configuration file can contain extra tabs or blank lines for easier formatting.
Keywords are case-insensitive and lines beginning with a hash sign (#) are considered
comments.
+ </div><div class="para">
+ There are two types of statements in the configuration file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Parameters — State how to perform a task, whether to perform a task, or what
network configuration options to send to the client.
+ </div></li><li class="listitem"><div
class="para">
+ Declarations — Describe the topology of the network, describe the clients, provide
addresses for the clients, or apply a group of parameters to a group of declarations.
+ </div></li></ul></div><a id="id479034"
class="indexterm"></a><div class="para">
+ The parameters that start with the keyword option are referred to as <em
class="firstterm">options</em>. These options control DHCP options;
whereas, parameters configure values that are not optional or control how the DHCP server
behaves.
+ </div><a id="id479056"
class="indexterm"></a><div class="para">
+ Parameters (including options) declared before a section enclosed in curly brackets
({ }) are considered global parameters. Global parameters apply to all the sections below
it.
+ </div><div class="important"><div
class="admonition_header"><h2>Restart the DHCP daemon for the changes
to take effect</h2></div><div class="admonition"><div
class="para">
+ If the configuration file is changed, the changes do not take effect until the DHCP
daemon is restarted. To do so, type the following at a shell prompt as <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>Use the
omshell command</h2></div><div class="admonition"><div
class="para">
+ Instead of changing a DHCP configuration file and restarting the service each time,
using the <code class="command">omshell</code> command provides an
interactive way to connect to, query, and change the configuration of a DHCP server. By
using <code class="command">omshell</code>, all changes can be made
while the server is running. For more information on <code
class="command">omshell</code>, refer to the <code
class="command">omshell</code> man page.
+ </div></div></div><div class="para">
+ In <a class="xref" href="#subnet">Example 10.1, “Subnet
declaration”</a>, the <code class="filename">routers</code>,
<code class="filename">subnet-mask</code>, <code
class="filename">domain-search</code>, <code
class="filename">domain-name-servers</code>, and <code
class="filename">time-offset</code> options are used for any <code
class="filename">host</code> statements declared below it.
+ </div><a id="id642370"
class="indexterm"></a><div class="para">
+ Additionally, a <code class="filename">subnet</code> can be
declared, a <code class="filename">subnet</code> declaration must be
included for every subnet in the network. If it is not, the DHCP server fails to start.
+ </div><div class="para">
+ In this example, there are global options for every DHCP client in the subnet and a
<code class="filename">range</code> declared. Clients are assigned
an IP address within the <code class="filename">range</code>.
+ </div><div class="example"
id="subnet"><h6>Example 10.1. Subnet declaration</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">
+ To configure a DHCP server that leases a dynamic IP address to a system within a
subnet, modify <a class="xref" href="#dynamic-ip">Example 10.2,
“Range parameter”</a> with your values. It declares a default lease time, maximum
lease time, and network configuration values for the clients. This example assigns IP
addresses in the <code class="filename">range</code> 192.168.1.10
and 192.168.1.100 to client systems.
+ </div><div class="example"
id="dynamic-ip"><h6>Example 10.2. Range parameter</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">Example 10.3, “Static IP address using DHCP”</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">
+ Note that the optional parameter <code
class="filename">host-name</code> can also be used to assign a host
name to the client.
+ </div><div class="example"
id="static-ip"><h6>Example 10.3. Static IP address using
DHCP</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="id442114" 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">Example 10.4, “Shared-network
declaration”</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>Example 10.4. Shared-network
declaration</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="id722455" class="indexterm"></a><div
class="para">
+ As demonstrated in <a class="xref"
href="#group">Example 10.5, “Group declaration”</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>Example 10.5. Group declaration</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>Using
the sample configuration file</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">
+ ... where <em
class="replaceable"><code>version-number</code></em> is the
DHCP version number.
+ </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"
id="lease-database">10.2.2. Lease
Database</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">
+ All times in the lease database are in Coordinated Universal Time (UTC), not local
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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id619308">10.2.3. Starting and Stopping the
Server</h3></div></div></div><a id="id420664"
class="indexterm"></a><a id="id420677"
class="indexterm"></a><a id="id420691"
class="indexterm"></a><a id="id1451046"
class="indexterm"></a><div class="important"><div
class="admonition_header"><h2>Starting the DHCP server for the first
time</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">
+ To start the DHCP service, use the following command:
+ </div><pre class="screen"><code
class="command">systemctl start dhcpd.service</code></pre><div
class="para">
+ To stop the DHCP server, type:
+ </div><pre class="screen"><code
class="command">systemctl stop dhcpd.service</code></pre><div
class="para">
+ By default, the DHCP service does not start at boot time. To configure the daemon to
start automatically at boot time, run:
+ </div><pre class="screen"><code
class="command">systemctl enable
dhcpcd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div><a id="id465185"
class="indexterm"></a><a id="id465199"
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">
+ This is useful for a firewall machine with two network cards. One network card can be
configured as a DHCP client to retrieve an IP address to the Internet. The other network
card can be used as a DHCP server for the internal network behind the firewall. Specifying
only the network card connected to the internal network makes the system more secure
because users can not connect to the daemon via the Internet.
+ </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">Section 10.2.4, “DHCP Relay Agent”</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> — Do not print the entire
copyright message when starting the daemon.
+ </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"
id="dhcp-relay-agent">10.2.4. DHCP Relay
Agent</h3></div></div></div><a id="id657876"
class="indexterm"></a><a id="id657890"
class="indexterm"></a><a id="id942460"
class="indexterm"></a><div class="para">
+ The DHCP Relay Agent (<code class="command">dhcrelay</code>)
allows for the relay of DHCP and BOOTP requests from a subnet with no DHCP server on it to
one or more DHCP servers on other subnets.
+ </div><div class="para">
+ When a DHCP client requests information, the DHCP Relay Agent forwards the request to
the list of DHCP servers specified when the DHCP Relay Agent is started. When a DHCP
server returns a reply, the reply is broadcast or unicast on the network that sent the
original request.
+ </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">
+ To start the DHCP Relay Agent, use the following command:
+ </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"
id="s1-dhcp-configuring-client">10.3. Configuring a DHCP
Client</h2></div></div></div><a id="id596217"
class="indexterm"></a><a id="id596231"
class="indexterm"></a><div class="para">
+ To configure a DHCP client manually, modify the <code
class="filename">/etc/sysconfig/network</code> file to enable
networking and the configuration file for each network device in the <code
class="filename">/etc/sysconfig/network-scripts</code> directory. In
this directory, each device should have a configuration file named <code
class="filename">ifcfg-eth0</code>, where <code
class="filename">eth0</code> is the network device name.
+ </div><div class="para">
+ The <code
class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code> file
should contain the following lines:
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ A configuration file is needed for each device to be configured to use DHCP.
+ </div><div class="para">
+ Other options for the network script includes:
+ </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>,
where <code class="literal"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — Modify <code
class="filename">/etc/resolv.conf</code> with information from the
server. If using DHCP, then <code class="command">yes</code> is the
default.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — Do not modify <code
class="filename">/etc/resolv.conf</code>.
+ </div></li></ul></div></li></ul></div><div
class="note"><div
class="admonition_header"><h2>Advanced
configurations</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"
id="sect-Configuring_a_Multihomed_DHCP_Server">10.4. Configuring a Multihomed
DHCP Server</h2></div></div></div><a id="id625550"
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><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">
+ The <code class="computeroutput">option subnet-mask</code>
option defines a subnet mask, and overrides the <code
class="computeroutput">netmask</code> value in the <code
class="computeroutput">subnet</code> declaration. In simple cases, the
subnet and netmask values are the same.
+ </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">
+ The <code class="computeroutput">range</code> option
specifies the pool of available IP addresses. Systems are assigned an address from the
range of specified IP addresses.
+ </div></dd></dl></div><div class="para">
+ For further information, refer to the <code
class="computeroutput">dhcpd.conf(5)</code> man page.
+ </div><div class="warning"><div
class="admonition_header"><h2>Do not use alias
interfaces</h2></div><div class="admonition"><div
class="para">
+ Alias interfaces are not supported by DHCP. If an alias interface is the only
interface, in the only subnet specified in <code
class="filename">/etc/dhcp/dhcpd.conf</code>, the DHCP daemon fails to
start.
+ </div></div></div><div class="section"
id="sect-dns_Host_Configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sect-dns_Host_Configuration">10.4.1. Host
Configuration</h3></div></div></div><a id="id462087"
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="id462112">Configuring a single system for
multiple networks</h5>
+ The following <code
class="filename">/etc/dhcp/dhcpd.conf</code> example creates two
subnets, and configures an IP address for the same system, depending on which network it
connects to:
+ </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><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="id1287074">Configuring systems with multiple network
interfaces</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"
id="s1-dhcp_for_ipv6_dhcpv6">10.5. DHCP for IPv6
(DHCPv6)</h2></div></div></div><a id="id898888"
class="indexterm"></a><a id="id898900"
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">
+ The DHCPv6 server configuration file can be found at <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">
+ To start the DHCPv6 service, use the following command:
+ </div><pre class="screen"><code
class="command">systemctl start
dhcpd6.service</code></pre><div class="para">
+ A simple DHCPv6 server configuration file can look like this:
+ </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"
id="s1-dhcp-additional-resources">10.6. Additional
Resources</h2></div></div></div><a id="id411480"
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"
id="s2-dhcp-installed-docs">10.6.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">dhcpd</code> man page — Describes how
the DHCP daemon works.
+ </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> man page —
Describes a persistent database of leases.
+ </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> man page — Explains
the DHCP Relay Agent and its configuration options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/dhcp-<em
class="replaceable"><code>version</code></em>/</code>
— Contains sample files, README files, and release notes for current versions of the DHCP
service.
+ </div></li></ul></div></div></div></div><div
xml:lang="en-US" class="chapter" id="ch-DNS_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 11. DNS
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-Introduction_to_DNS">11.1. Introduction to
DNS</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-dns-introduction-zones">11.1.1.
Nameserver Zones</a></span></dt><dt><span
class="section"><a
href="#s2-dns-introduction-nameservers">11.1.2. Nameserver
Types</a></span></dt><dt><span
class="section"><a href="#s2-dns-introduction-bind">11.1.3.
BIND as a
Nameserver</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-BIND">11.2.
BIND</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-bind-namedconf">11.2.1.
Configuring the named Service</a></span></dt><dt><span
class="section"><a href="#s2-bind-zone">11.2.2. Editing Zone
Files</a></span></dt><dt><span
class="section"><a href="#s
2-bind-rndc">11.2.3. Using the rndc
Utility</a></span></dt><dt><span
class="section"><a href="#s2-bind-dig">11.2.4. Using the dig
Utility</a></span></dt><dt><span
class="section"><a href="#s2-bind-features">11.2.5. Advanced
Features of BIND</a></span></dt><dt><span
class="section"><a href="#s2-bind-mistakes">11.2.6. Common
Mistakes to Avoid</a></span></dt><dt><span
class="section"><a
href="#s2-bind-additional-resources">11.2.7. Additional
Resources</a></span></dt></dl></dd></dl></div><a
id="id471493" class="indexterm"></a><a
id="id503699" class="indexterm"></a><div
class="para">
+ <code class="systemitem">DNS</code> (Domain Name System), also
known as a <em class="firstterm">nameserver</em>, is a network
system that associates hostnames with their respective IP addresses. For users, this has
the advantage that they can refer to machines on the network by names that are usually
easier to remember than the numerical network addresses. For system administrators, using
the nameserver allows them to change the IP address for a host without ever affecting the
name-based queries, or to decide which machines handle these queries.
+ </div><div class="section"
id="s1-Introduction_to_DNS"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-Introduction_to_DNS">11.1. Introduction to
DNS</h2></div></div></div><a id="id503664"
class="indexterm"></a><div class="para">
+ DNS is usually implemented using one or more centralized servers that are
authoritative for certain domains. When a client host requests information from a
nameserver, it usually connects to port 53. The nameserver then attempts to resolve the
name requested. If it does not have an authoritative answer, or does not already have the
answer cached from an earlier query, it queries other nameservers, called <em
class="firstterm">root nameservers</em>, to determine which nameservers
are authoritative for the name in question, and then queries them to get the requested
name.
+ </div><div class="section"
id="s2-dns-introduction-zones"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-dns-introduction-zones">11.1.1. Nameserver
Zones</h3></div></div></div><a id="id471487"
class="indexterm"></a><a id="id471471"
class="indexterm"></a><a id="id471458"
class="indexterm"></a><a id="id471450"
class="indexterm"></a><div class="para">
+ In a DNS server such as BIND, all information is stored in basic data elements called
<em class="firstterm">resource records</em> (RR). The resource
record is usually a <em class="firstterm">fully qualified domain
name</em> (FQDN) of a host, and is broken down into multiple sections organized into
a tree-like hierarchy. This hierarchy consists of a main trunk, primary branches,
secondary branches, and so on. The following is an example of a resource record:
+ </div><pre
class="programlisting">bob.sales.example.com</pre><a
id="id562602" class="indexterm"></a><div
class="para">
+ Each level of the hierarchy is divided by a period (that is, <code
class="literal">.</code>). In the example above, <code
class="literal">com</code> defines the <em
class="firstterm">top-level domain</em>, <code
class="literal">example</code> its subdomain, and <code
class="literal">sales</code> the subdomain of <code
class="literal">example</code>. In this case, <code
class="literal">bob</code> identifies a resource record that is part of
the <code class="systemitem">sales.example.com</code> domain. With
the exception of the part furthest to the left (that is, <code
class="literal">bob</code>), each of these sections is called a <em
class="firstterm">zone</em> and defines a specific <em
class="firstterm">namespace</em>.
+ </div><a id="id562535"
class="indexterm"></a><a id="id562521"
class="indexterm"></a><div class="para">
+ Zones are defined on authoritative nameservers through the use of <em
class="firstterm">zone files</em>, which contain definitions of the
resource records in each zone. Zone files are stored on <em
class="firstterm">primary nameservers</em> (also called <em
class="firstterm">master nameservers</em>), where changes are made to
the files, and <em class="firstterm">secondary nameservers</em>
(also called <em class="firstterm">slave nameservers</em>), which
receive zone definitions from the primary nameservers. Both primary and secondary
nameservers are authoritative for the zone and look the same to clients. Depending on the
configuration, any nameserver can also serve as a primary or secondary server for multiple
zones at the same time.
+ </div></div><div class="section"
id="s2-dns-introduction-nameservers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-dns-introduction-nameservers">11.1.2. Nameserver
Types</h3></div></div></div><div class="para">
+ There are two nameserver configuration types:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id393779" class="indexterm"></a>
+ <a id="id393766" class="indexterm"></a>
+ <a id="id393749" class="indexterm"></a>
+ <a id="id583367" class="indexterm"></a>
+ <a id="id583352" class="indexterm"></a>
+ <a id="id583329" class="indexterm"></a>
+ authoritative </span></dt><dd><div class="para">
+ Authoritative nameservers answer to resource records that are part of their zones
only. This category includes both primary (master) and secondary (slave) nameservers.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id583303"
class="indexterm"></a>
+ <a id="id1070412" class="indexterm"></a>
+ recursive </span></dt><dd><div class="para">
+ Recursive nameservers offer resolution services, but they are not authoritative
for any zone. Answers for all resolutions are cached in a memory for a fixed period of
time, which is specified by the retrieved resource record.
+ </div></dd></dl></div><div class="para">
+ Although a nameserver can be both authoritative and recursive at the same time, it is
recommended not to combine the configuration types. To be able to perform their work,
authoritative servers should be available to all clients all the time. On the other hand,
since the recursive lookup takes far more time than authoritative responses, recursive
servers should be available to a restricted number of clients only, otherwise they are
prone to distributed denial of service (DDoS) attacks.
+ </div></div><div class="section"
id="s2-dns-introduction-bind"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-dns-introduction-bind">11.1.3. BIND as a
Nameserver</h3></div></div></div><a id="id1070373"
class="indexterm"></a><a id="id1070344"
class="indexterm"></a><a id="id1070328"
class="indexterm"></a><a id="id897759"
class="indexterm"></a><a id="id897741"
class="indexterm"></a><a id="id897733"
class="indexterm"></a><div class="para">
+ BIND consists of a set of DNS-related programs. It contains a monolithic nameserver
called <code class="systemitem">named</code>, an administration
utility called <code class="command">rndc</code>, and a debugging
tool called <code class="command">dig</code>. Refer to <a
class="xref" href="#ch-Services_and_Daemons">Chapter 7,
<em>Services and Daemons</em></a> for more information on how to
configure services in Fedora.
+ </div></div></div><div xml:lang="en-US"
class="section" id="s1-BIND" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-BIND">11.2. BIND</h2></div></div></div><a
id="id718362" class="indexterm"></a><div
class="para">
+ This chapter covers <code class="systemitem">BIND</code>
(Berkeley Internet Name Domain), the DNS server included in Fedora. It focuses on the
structure of its configuration files, and describes how to administer it both locally and
remotely.
+ </div><div class="section"
id="s2-bind-namedconf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-namedconf">11.2.1. Configuring the named
Service</h3></div></div></div><a id="id718334"
class="indexterm"></a><div class="para">
+ When the <code class="systemitem">named</code> service is
started, it reads the configuration from the files as described in <a
class="xref" href="#table-bind-namedconf-files">Table 11.1, “The
named service configuration files”</a>.
+ </div><a id="id718296"
class="indexterm"></a><a id="id718282"
class="indexterm"></a><a id="id685599"
class="indexterm"></a><div class="table"
id="table-bind-namedconf-files"><h6>Table 11.1. The named service
configuration files</h6><div class="table-contents"><table
summary="The named service configuration files"
border="1"><colgroup><col width="38%"
class="path" /><col width="63%" class="description"
/></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc/named.conf</code>
+ </td><td>
+ The main configuration file.
+ </td></tr><tr><td>
+ <code class="filename">/etc/named/</code>
+ </td><td>
+ An auxiliary directory for configuration files that are included in the main
configuration file.
+ </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>Running BIND in a chroot
environment</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"
id="s3-bind-namedconf-state">11.2.1.1. Common Statement
Types</h4></div></div></div><div class="para">
+ The following types of statements are commonly used in <code
class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id877254" class="indexterm"></a>
+ <code class="option">acl</code>
</span></dt><dd><div class="para">
+ The <code class="option">acl</code> (Access Control List)
statement allows you to define groups of hosts, so that they can be permitted or denied
access to the nameserver. It takes the following form:
+ </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">Table 11.2, “Predefined access
control lists”</a>.
+ </div><div class="table"
id="table-bind-namedconf-common-acl"><h6>Table 11.2. Predefined access
control lists</h6><div class="table-contents"><table
summary="Predefined access control lists"
border="1"><colgroup><col width="25%"
class="keyword" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Keyword
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">any</code>
+ </td><td>
+ Matches every IP address.
+ </td></tr><tr><td>
+ <code class="option">localhost</code>
+ </td><td>
+ Matches any IP address that is in use by the local system.
+ </td></tr><tr><td>
+ <code class="option">localnets</code>
+ </td><td>
+ Matches any IP address on any network to which the local system is connected.
+ </td></tr><tr><td>
+ <code class="option">none</code>
+ </td><td>
+ Does not match any IP address.
+ </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">Example 11.1, “Using acl in
conjunction with options”</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>Example 11.1. Using acl in
conjunction with options</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="id623822"
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>Example 11.2. Including
a file to /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="id977072" 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">Table 11.3, “Commonly used
options”</a> below.
+ </div><div class="table"
id="table-bind-namedconf-common-options"><h6>Table 11.3. Commonly used
options</h6><div class="table-contents"><table
summary="Commonly used options" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow-query</code>
+ </td><td>
+ Specifies which hosts are allowed to query the nameserver for authoritative
resource records. It accepts an access control lists, a collection of IP addresses, or
networks in the CIDR notation. All hosts are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">allow-query-cache</code>
+ </td><td>
+ Specifies which hosts are allowed to query the nameserver for
non-authoritative data such as recursive queries. Only <code
class="literal">localhost</code> and <code
class="literal">localnets</code> are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">blackhole</code>
+ </td><td>
+ Specifies which hosts are <span
class="emphasis"><em>not</em></span> allowed to query the
nameserver. This option should be used when particular host or network floods the server
with requests. The default option is <code
class="literal">none</code>.
+ </td></tr><tr><td>
+ <code class="option">directory</code>
+ </td><td>
+ Specifies a working directory for the <code
class="systemitem">named</code> service. The default option is <code
class="literal">/var/named/</code>.
+ </td></tr><tr><td>
+ <code class="option">dnssec-enable</code>
+ </td><td>
+ Specifies whether to return DNSSEC related resource records. The default
option is <code class="literal">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">dnssec-validation</code>
+ </td><td>
+ Specifies whether to prove that resource records are authentic via DNSSEC. The
default option is <code class="option">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">forwarders</code>
+ </td><td>
+ Specifies a list of valid IP addresses for nameservers to which the requests
should be forwarded for resolution.
+ </td></tr><tr><td>
+ <code class="option">forward</code>
+ </td><td>
+ <div class="para">
+ Specifies the behavior of the <code
class="option">forwarders</code> directive. It accepts the following
options:
+ </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>
+ <code class="option">listen-on</code>
+ </td><td>
+ Specifies the IPv4 network interface on which to listen for queries. On a DNS
server that also acts as a gateway, you can use this option to answer queries originating
from a single network only. All IPv4 interfaces are used by default.
+ </td></tr><tr><td>
+ <code class="option">listen-on-v6</code>
+ </td><td>
+ Specifies the IPv6 network interface on which to listen for queries. On a DNS
server that also acts as a gateway, you can use this option to answer queries originating
from a single network only. All IPv6 interfaces are used by default.
+ </td></tr><tr><td>
+ <code class="option">max-cache-size</code>
+ </td><td>
+ Specifies the maximum amount of memory to be used for server caches. When the
limit is reached, the server causes records to expire prematurely so that the limit is not
exceeded. In a server with multiple views, the limit applies separately to the cache of
each view. The default option is <code class="literal">32M</code>.
+ </td></tr><tr><td>
+ <code class="option">notify</code>
+ </td><td>
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated.
It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will
notify all secondary nameservers.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">no</code> — The server will
<span class="emphasis"><em>not</em></span> notify any
secondary nameserver.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">master-only</code> — The server
will notify primary server for the zone only.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">explicit</code> — The server
will notify only the secondary servers that are specified in the <code
class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">pid-file</code>
+ </td><td>
+ Specifies the location of the process ID file created by the <code
class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="option">recursion</code>
+ </td><td>
+ Specifies whether to act as a recursive server. The default option is <code
class="literal">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">statistics-file</code>
+ </td><td>
+ Specifies an alternate location for statistics files. The <code
class="filename">/var/named/named.stats</code> file is used by
default.
+ </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">Section 11.2.7.1, “Installed
Documentation”</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>Example 11.3. Using the
options statement</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="id761416"
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">Table 11.4,
“Commonly used options”</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">Section 11.2.2, “Editing Zone Files”</a>.
+ </div><div class="table"
id="table-bind-namedconf-common-zone"><h6>Table 11.4. Commonly used
options</h6><div class="table-contents"><table
summary="Commonly used options" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow-query</code>
+ </td><td>
+ 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>
+ <code class="option">allow-transfer</code>
+ </td><td>
+ 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>
+ <code class="option">allow-update</code>
+ </td><td>
+ <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">Section 11.2.5.3, “Transaction SIGnatures
(TSIG)”</a>.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="option">file</code>
+ </td><td>
+ 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>
+ <code class="option">masters</code>
+ </td><td>
+ 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>
+ <code class="option">notify</code>
+ </td><td>
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated.
It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will
notify all secondary nameservers.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">no</code> — The server will
<span class="emphasis"><em>not</em></span> notify any
secondary nameserver.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">master-only</code> — The server
will notify primary server for the zone only.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">explicit</code> — The server
will notify only the secondary servers that are specified in the <code
class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">type</code>
+ </td><td>
+ <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">Example 11.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>Example 11.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">Example 11.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>Example 11.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"
id="s3-bind-namedconf-state-other">11.2.1.2. Other Statement
Types</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><dt
class="varlistentry"><span class="term"> <a
id="id1250479" 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">
+ Refer to <a class="xref"
href="#s2-bind-rndc">Section 11.2.3, “Using the rndc Utility”</a> for
more information on the <code class="command">rndc</code> utility
and its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id489897"
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>
— The type of algorithm to be used (for example, <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>
— The encrypted key.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref"
href="#s2-bind-rndc">Section 11.2.3, “Using the rndc Utility”</a> for
more information on the <code class="command">rndc</code> utility
and its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id997959"
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">Section 11.2.7.1, “Installed
Documentation”</a>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id680722"
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="id590070"
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">Section 11.2.5.4, “DNS
Security Extensions (DNSSEC)”</a> for more information on this topic.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id590013"
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">Section 11.2.5.1, “Multiple 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"
id="s3-bind-namedconf-comm">11.2.1.3. Comment
Tags</h4></div></div></div><a id="id1061440"
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><dt
class="varlistentry"><span class="term"><code
class="literal">//</code></span></dt><dd><div
class="para">
+ Any text after the <code class="literal">//</code>
characters to the end of the line is considered a comment. For example:
+ </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">
+ Any text after the <code class="literal">#</code> character
to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting">notify yes; # notify all
secondary nameservers</pre></dd><dt
class="varlistentry"><span class="term"><code
class="literal">/*</code> and <code
class="literal">*/</code></span></dt><dd><div
class="para">
+ Any block of text enclosed in <code
class="literal">/*</code> and <code
class="literal">*/</code> is considered a comment. For example:
+ </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"
id="s2-bind-zone">11.2.2. Editing Zone
Files</h3></div></div></div><a id="id548174"
class="indexterm"></a><a id="id548155"
class="indexterm"></a><a id="id548137"
class="indexterm"></a><a id="id548111"
class="indexterm"></a><div class="para">
+ As outlined in <a class="xref"
href="#s2-dns-introduction-zones">Section 11.1.1, “Nameserver
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>Table 11.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>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/var/named/</code>
+ </td><td>
+ The working directory for the <code
class="systemitem">named</code> service. The nameserver is <span
class="emphasis"><em>not</em></span> allowed to write to
this directory.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/slaves/</code>
+ </td><td>
+ The directory for secondary zones. This directory is writable by the <code
class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/dynamic/</code>
+ </td><td>
+ 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>
+ <code class="filename">/var/named/data/</code>
+ </td><td>
+ 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">
+ All directives and resource records should be entered on individual lines.
+ </div><div class="section"
id="s3-bind-zone-directives"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-zone-directives">11.2.2.1. Common
Directives</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><dt
class="varlistentry"><span class="term"> <a
id="id1450190" 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>Example 11.6. Using the
$INCLUDE directive</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="id918666" 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">Example 11.7, “Using the $ORIGIN
directive”</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>Example 11.7. Using the
$ORIGIN directive</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="id568261"
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">
+ Increasing this value allows remote nameservers to cache the zone information for
a longer period of time, reducing the number of queries for the zone and lengthening the
amount of time required to proliferate resource record changes.
+ </div><div class="example"
id="example-bind-zone-directive-ttl"><h6>Example 11.8. Using the $TTL
directive</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"
id="s4-bind-zone-rr">11.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><dt
class="varlistentry"><span class="term"> <a
id="id446530" 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">Example 11.9, “Using the A resource
record”</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>Example 11.9. Using the A resource
record</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="id1059600" 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">Example 11.10, “Using the CNAME resource
record”</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>Example 11.10. Using the CNAME
resource record</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="id845983" 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">Example 11.11, “Using the MX resource
record”</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>Example 11.11. Using the MX resource
record</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="id903862" class="indexterm"></a>
+ <code class="command">NS</code>
</span></dt><dd><div class="para">
+ The <em class="firstterm">Nameserver</em> record announces
authoritative nameservers for a particular zone. It takes the following form:
+ </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>Example 11.12. Using the NS resource
record</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="id903788" class="indexterm"></a>
+ <code class="command">PTR</code>
</span></dt><dd><div class="para">
+ The <em class="firstterm">Pointer</em> record points to
another part of the namespace. It takes the following form:
+ </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">Section 11.2.2.4.2, “A Reverse
Name Resolution Zone File”</a> for more examples of <code
class="command">PTR</code> records in use.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id1290214"
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">
+ The directives are as follows:
+ </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">Table 11.6, “Seconds compared to other time
units”</a> shows an amount of time in seconds and the equivalent time in another
format.
+ </div><div class="table"
id="tb-bind-seconds"><h6>Table 11.6. Seconds compared to other time
units</h6><div class="table-contents"><table
summary="Seconds compared to other time units"
border="1"><colgroup><col width="50%"
class="seconds" /><col width="50%" class="other"
/></colgroup><thead><tr><th>
+ Seconds
+ </th><th>
+ Other Time Units
+ </th></tr></thead><tbody><tr><td>
+ 60
+ </td><td>
+ <code class="literal">1M</code>
+ </td></tr><tr><td>
+ 1800
+ </td><td>
+ <code class="literal">30M</code>
+ </td></tr><tr><td>
+ 3600
+ </td><td>
+ <code class="literal">1H</code>
+ </td></tr><tr><td>
+ 10800
+ </td><td>
+ <code class="literal">3H</code>
+ </td></tr><tr><td>
+ 21600
+ </td><td>
+ <code class="literal">6H</code>
+ </td></tr><tr><td>
+ 43200
+ </td><td>
+ <code class="literal">12H</code>
+ </td></tr><tr><td>
+ 86400
+ </td><td>
+ <code class="literal">1D</code>
+ </td></tr><tr><td>
+ 259200
+ </td><td>
+ <code class="literal">3D</code>
+ </td></tr><tr><td>
+ 604800
+ </td><td>
+ <code class="literal">1W</code>
+ </td></tr><tr><td>
+ 31536000
+ </td><td>
+ <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>Example 11.13. Using the SOA resource
record</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"
id="s3-bind-zone-comm">11.2.2.3. Comment
Tags</h4></div></div></div><a id="id568776"
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 ; expire after 1
week</pre></div><div class="section"
id="s3-bind-zone-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-zone-examples">11.2.2.4. Example
Usage</h4></div></div></div><div class="para">
+ The following examples show the basic usage of zone files.
+ </div><div class="section"
id="s4-bind-zone-examples-basic"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s4-bind-zone-examples-basic">11.2.2.4.1. A Simple Zone
File</h5></div></div></div><a id="id568716"
class="indexterm"></a><div class="para">
+ <a class="xref"
href="#example-bind-zone-examples-basic">Example 11.14, “A simple zone
file”</a> demonstrates the use of standard directives and <code
class="command">SOA</code> values.
+ </div><div class="example"
id="example-bind-zone-examples-basic"><h6>Example 11.14. A simple zone
file</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">
+ This zone file would be called into service with a <code
class="command">zone</code> statement in the <code
class="filename">/etc/named.conf</code> similar to the following:
+ </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"
id="s3-bind-configuration-zone-reverse">11.2.2.4.2. A Reverse Name Resolution
Zone File</h5></div></div></div><a id="id503685"
class="indexterm"></a><div class="para">
+ A reverse name resolution zone file is used to translate an IP address in a
particular namespace into an fully qualified domain name (FQDN). It looks very similar to
a standard zone file, except that the <code
class="command">PTR</code> resource records are used to link the IP
addresses to a fully qualified domain name as shown in <a class="xref"
href="#example-bind-zone-examples-reverse">Example 11.15, “A reverse name
resolution zone file”</a>.
+ </div><div class="example"
id="example-bind-zone-examples-reverse"><h6>Example 11.15. A reverse
name resolution zone file</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">
+ In this example, IP addresses <code
class="systemitem">10.0.1.1</code> through <code
class="systemitem">10.0.1.6</code> are pointed to the corresponding
fully qualified domain name.
+ </div><div class="para">
+ This zone file would be called into service with a <code
class="option">zone</code> statement in the <code
class="filename">/etc/named.conf</code> file similar to the following:
+ </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"
id="s2-bind-rndc">11.2.3. Using the rndc
Utility</h3></div></div></div><a id="id622019"
class="indexterm"></a><div class="para">
+ The <code class="command">rndc</code> utility is a command line
tool that allows you to administer the <code
class="systemitem">named</code> service, both locally and from a remote
machine. Its usage is as follows:
+ </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"
id="s3-bind-rndc-configuration">11.2.3.1. Configuring the
Utility</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>Table 11.7. Relevant
files</h6><div class="table-contents"><table
summary="Relevant files" border="1"><colgroup><col
width="38%" class="path" /><col width="63%"
class="description" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id1451483" class="indexterm"></a>
+ <code class="filename">/etc/named.conf</code>
+ </td><td>
+ The default configuration file for the <code
class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <a id="id685537" class="indexterm"></a>
+ <code class="filename">/etc/rndc.conf</code>
+ </td><td>
+ The default configuration file for the <code
class="command">rndc</code> utility.
+ </td></tr><tr><td>
+ <a id="id642093" class="indexterm"></a>
+ <code class="filename">/etc/rndc.key</code>
+ </td><td>
+ The default key location.
+ </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">Section 11.2.1.2, “Other Statement
Types”</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">Section 11.2.7, “Additional
Resources”</a>.
+ </div><div class="important"><div
class="admonition_header"><h2>Set the correct
permissions</h2></div><div class="admonition"><div
class="para">
+ To prevent unprivileged users from sending control commands to the service, make
sure only root is allowed to read the <code
class="filename">/etc/rndc.key</code> file:
+ </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"
id="s3-bind-rndc-status">11.2.3.2. Checking the Service
Status</h4></div></div></div><div class="para">
+ To check the current status of the <code
class="systemitem">named</code> service, use the following command:
+ </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"
id="s3-bind-rndc-reload">11.2.3.3. Reloading the Configuration and
Zones</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">
+ Finally, to reload the configuration file and newly added zones only, type:
+ </div><pre class="screen">~]# <code
class="command">rndc reconfig</code></pre><div
class="note"><div
class="admonition_header"><h2>Modifying zones with dynamic
DNS</h2></div><div class="admonition"><div
class="para">
+ If you intend to manually modify a zone that uses Dynamic DNS (DDNS), make sure you
run the <code class="command">freeze</code> command first:
+ </div><pre class="screen">~]# <code
class="command">rndc freeze localhost</code></pre><div
class="para">
+ Once you are finished, run the <code
class="command">thaw</code> command to allow the DDNS again and reload
the zone:
+ </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"
id="s3-bind-rndc-sign">11.2.3.4. Updating Zone
Keys</h4></div></div></div><div class="para">
+ To update the DNSSEC keys and sign the zone, use the <code
class="command">sign</code> command. For example:
+ </div><pre class="screen">~]# <code
class="command">rndc sign localhost</code></pre><div
class="para">
+ Note that to sign a zone with the above command, the <code
class="option">auto-dnssec</code> option has to be set to <code
class="literal">maintain</code> in the zone statement. For instance:
+ </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"
id="s3-bind-rndc-validation">11.2.3.5. Enabling the DNSSEC
Validation</h4></div></div></div><div
class="para">
+ To enable the DNSSEC validation, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">rndc validation on</code></pre><div
class="para">
+ Similarly, to disable this option, type:
+ </div><pre class="screen">~]# <code
class="command">rndc validation off</code></pre><div
class="para">
+ Refer to the <code class="option">options</code> statement
described in <a class="xref"
href="#s3-bind-namedconf-state">Section 11.2.1.1, “Common Statement
Types”</a> for information on how configure this option in <code
class="filename">/etc/named.conf</code>.
+ </div></div><div class="section"
id="s3-bind-rndc-querylog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-rndc-querylog">11.2.3.6. Enabling the Query
Logging</h4></div></div></div><div class="para">
+ To enable (or disable in case it is currently enabled) the query logging, run the
following command:
+ </div><pre class="screen">~]# <code
class="command">rndc querylog</code></pre><div
class="para">
+ To check the current setting, use the <code
class="command">status</code> command as described in <a
class="xref" href="#s3-bind-rndc-status">Section 11.2.3.2,
“Checking the Service Status”</a>.
+ </div></div></div><div class="section"
id="s2-bind-dig"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-dig">11.2.4. Using the dig
Utility</h3></div></div></div><a id="id905780"
class="indexterm"></a><div class="para">
+ The <code class="command">dig</code> utility is a command line
tool that allows you to perform DNS lookups and debug a nameserver configuration. Its
typical usage is as follows:
+ </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">
+ Refer to <a class="xref"
href="#s4-bind-zone-rr">Section 11.2.2.2, “Common Resource Records”</a>
for a list of common <em
class="replaceable"><code>type</code></em>s.
+ </div><div class="section" id="s3-bind-dig-ns"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-dig-ns">11.2.4.1. Looking Up a
Nameserver</h4></div></div></div><div
class="para">
+ To look up a nameserver for a particular domain, use the command in the following
form:
+ </div><pre class="screen"><code
class="command">dig</code> <em
class="replaceable"><code>name</code></em>
NS</pre><div class="para">
+ In <a class="xref"
href="#example-bind-dig-ns">Example 11.16, “A sample nameserver
lookup”</a>, the <code class="command">dig</code> utility is
used to display nameservers for <code
class="systemitem">example.com</code>.
+ </div><div class="example"
id="example-bind-dig-ns"><h6>Example 11.16. A sample nameserver
lookup</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"
id="s3-bind-dig-a">11.2.4.2. Looking Up an IP
Address</h4></div></div></div><div class="para">
+ To look up an IP address assigned to a particular domain, use the command in the
following form:
+ </div><pre class="screen"><code
class="command">dig</code> <em
class="replaceable"><code>name</code></em>
A</pre><div class="para">
+ In <a class="xref"
href="#example-bind-dig-a">Example 11.17, “A sample IP address
lookup”</a>, the <code class="command">dig</code> utility is
used to display the IP address of <code
class="systemitem">example.com</code>.
+ </div><div class="example"
id="example-bind-dig-a"><h6>Example 11.17. A sample IP address
lookup</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"
id="s3-bind-dig-x">11.2.4.3. Looking Up a
Hostname</h4></div></div></div><div class="para">
+ To look up a hostname for a particular IP address, use the command in the following
form:
+ </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">
+ In <a class="xref"
href="#example-bind-dig-x">Example 11.18, “A sample hostname
lookup”</a>, the <code class="command">dig</code> utility is
used to display the hostname assigned to <code
class="systemitem">192.0.32.10</code>.
+ </div><div class="example"
id="example-bind-dig-x"><h6>Example 11.18. A sample hostname
lookup</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"
id="s2-bind-features">11.2.5. Advanced Features of
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>Make sure the feature is
supported</h2></div><div class="admonition"><div
class="para">
+ Before attempting to use advanced features like DNSSEC, TSIG, or IXFR, make sure that
the particular feature is supported by all nameservers in the network environment,
especially when you use older versions of BIND or non-BIND servers.
+ </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">Section 11.2.7.1, “Installed
Documentation”</a>.
+ </div><div class="section"
id="s3-bind-features-views"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-features-views">11.2.5.1. Multiple
Views</h4></div></div></div><a id="id437036"
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"
id="s3-bind-features-ixfr">11.2.5.2. Incremental Zone Transfers
(IXFR)</h4></div></div></div><a id="id702391"
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="id833108"
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"
id="s3-bind-features-tsig">11.2.5.3. Transaction SIGnatures
(TSIG)</h4></div></div></div><a id="id571595"
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"
id="s3-bind-features-dnssec">11.2.5.4. DNS Security Extensions
(DNSSEC)</h4></div></div></div><a id="id698003"
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="id702383"
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">Section 11.2.4, “Using the dig
Utility”</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"
id="s3-bind-features-ipv6">11.2.5.5. Internet Protocol version 6
(IPv6)</h4></div></div></div><a id="id532707"
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">Table 11.3, “Commonly used
options”</a>.
+ </div></div></div><div class="section"
id="s2-bind-mistakes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-mistakes">11.2.6. Common Mistakes to
Avoid</h3></div></div></div><a id="id611739"
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><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">Configure the firewall</span></dt><dd><div
class="para">
+ If a firewall is blocking connections from the <code
class="systemitem">named</code> service to other nameservers, the
recommended best practice is to change the firewall settings whenever possible.
+ </div><div class="warning"
id="warning-Warning-Avoid_Using_Fixed_UDP_Source_Ports"><div
class="admonition_header"><h2>Avoid using fixed UDP source
ports</h2></div><div class="admonition"><div
class="para">
+ According to the recent research in DNS security, using a fixed UDP source port
for DNS queries is a potential security vulnerability that could allow an attacker to
conduct cache-poisoning attacks more easily. To prevent this, configure your firewall to
allow queries from a random UDP source port.
+ </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"
id="s2-bind-additional-resources">11.2.7. Additional
Resources</h3></div></div></div><div
class="para">
+ The following sources of information provide additional resources regarding BIND.
+ </div><div class="section"
id="s3-bind-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-installed-docs">11.2.7.1. Installed
Documentation</h4></div></div></div><a id="id933608"
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><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">
+ The main directory containing the most recent documentation.
+ </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">
+ The directory providing every RFC document related to BIND.
+ </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><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"
id="s3-bind-useful-websites">11.2.7.2. Useful
Websites</h4></div></div></div><a id="id390012"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://www.isc.org/software/bind">http://www.isc.org/s...
class="para">
+ The home page of the BIND project containing information about current releases as
well as a PDF version of the <em class="citetitle">BIND 9 Administrator
Reference Manual</em>.
+ </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"
id="s3-bind-related-books">11.2.7.3. Related
Books</h4></div></div></div><a id="id567506"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><em
class="citetitle">DNS and BIND</em> by Paul Albitz and Cricket Liu;
O'Reilly & Associates</span></dt><dd><div
class="para">
+ A popular reference that explains both common and esoteric BIND configuration
options, and provides strategies for securing a DNS server.
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">The Concise Guide to DNS
and BIND</em> by 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="en-US" class="chapter" id="ch-Web_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 12. Web
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-The_Apache_HTTP_Server">12.1. The Apache HTTP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-apache-version2-features">12.1.1. New
Features</a></span></dt><dt><span
class="section"><a href="#s2-apache-version2-changes">12.1.2.
Notable Changes</a></span></dt><dt><span
class="section"><a
href="#s2-apache-version2-migrating">12.1.3. Updating the
Configuration</a></span></dt><dt><span
class="section"><a href="#s2-apache-running">12.1.4. Running
the httpd Service</a></span></dt><dt><span
class="section"><a href="#s2-apache-editing">12.1.5. Editing
the Configuration Files</a></span></dt><dt><span
class="section"><a href="#s2-apache-dso">12.1.6. Working with
Modules</a></span></dt><d
t><span class="section"><a
href="#s2-apache-virtualhosts">12.1.7. Setting Up Virtual
Hosts</a></span></dt><dt><span
class="section"><a href="#s2-apache-mod_ssl">12.1.8. Setting
Up an SSL Server</a></span></dt><dt><span
class="section"><a href="#s2-apache-resources">12.1.9.
Additional
Resources</a></span></dt></dl></dd></dl></div><a
id="id851625" class="indexterm"></a><a
id="id849589" class="indexterm"></a><div
class="para">
+ <code class="systemitem">HTTP</code> (Hypertext Transfer
Protocol) server, or a <em class="firstterm">web server</em>, is a
network service that serves content to a client over the web. This typically means web
pages, but any other documents can be served as well.
+ </div><div xml:lang="en-US" class="section"
id="s1-The_Apache_HTTP_Server" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-The_Apache_HTTP_Server">12.1. The Apache HTTP
Server</h2></div></div></div><a id="id849547"
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 15. 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">
+ There are important differences between the Apache HTTP Server 2.2 and version 2.0, and
if you are upgrading from a previous release of Fedora, you will need to update the
<code class="systemitem">httpd</code> service configuration
accordingly. This section reviews some of the newly added features, outlines important
changes, and guides you through the update of older configuration files.
+ </div><div class="section"
id="s2-apache-version2-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-apache-version2-features">12.1.1. New
Features</h3></div></div></div><a id="id851613"
class="indexterm"></a><div class="para">
+ The Apache HTTP Server version 2.2 introduces the following enhancements:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a id="id851582" class="indexterm"></a>
+ <a id="id851556" class="indexterm"></a>
+ Improved caching modules, that is, <code
class="systemitem">mod_cache</code> and <code
class="systemitem">mod_disk_cache</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="id606606" class="indexterm"></a>
+ Support for proxy load balancing, that is, the <code
class="systemitem">mod_proxy_balancer</code> module.
+ </div></li><li class="listitem"><div
class="para">
+ Support for large files on 32-bit architectures, allowing the web server to handle
files greater than 2GB.
+ </div></li><li class="listitem"><div
class="para">
+ A new structure for authentication and authorization support, replacing the
authentication modules provided in previous versions.
+ </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"
id="s2-apache-version2-changes">12.1.2. Notable
Changes</h3></div></div></div><a id="id704729"
class="indexterm"></a><div class="para">
+ Since version 2.0, few changes have been made to the default <code
class="systemitem">httpd</code> service configuration:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a id="id704718" class="indexterm"></a>
+ <a id="id704664" class="indexterm"></a>
+ The following modules are no longer loaded by default: <code
class="systemitem">mod_cern_meta</code> and <code
class="systemitem">mod_asis</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="id704655" class="indexterm"></a>
+ The following module is newly loaded by default: <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"
id="s2-apache-version2-migrating">12.1.3. Updating the
Configuration</h3></div></div></div><a id="id1299508"
class="indexterm"></a><div class="para">
+ To update the configuration files from the Apache HTTP Server version 2.0, take the
following steps:
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ Make sure all module names are correct, since they may have changed. Adjust the
<code class="option">LoadModule</code> directive for each module
that has been renamed.
+ </div></li><li class="step"><div
class="para">
+ Recompile all third party modules before attempting to load them. This typically
means authentication and authorization modules.
+ </div></li><li class="step"><div
class="para">
+ <a id="id596194" class="indexterm"></a>
+ If you use the <code class="systemitem">mod_userdir</code>
module, make sure the <code class="option">UserDir</code> directive
indicating a directory name (typically <code
class="literal">public_html</code>) is provided.
+ </div></li><li class="step"><div
class="para">
+ If you use the Apache HTTP Secure Server, edit the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> to enable the Secure
Sockets Layer (SSL) protocol.
+ </div></li></ol></div><div class="para">
+ Note that you can check the configuration for possible errors by using the following
command:
+ </div><pre class="screen"><code
class="command">service httpd configtest</code></pre><div
class="para">
+ For more information on upgrading the Apache HTTP Server configuration from version
2.0 to 2.2, refer to <a
href="http://httpd.apache.org/docs/2.2/upgrading.html">http:...;.
+ </div></div><div class="section"
id="s2-apache-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-apache-running">12.1.4. Running the httpd
Service</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">Chapter 7, <em>Services and
Daemons</em></a>.
+ </div><div class="section"
id="s3-apache-running-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-running-starting">12.1.4.1. Starting the
Service</h4></div></div></div><a id="id977221"
class="indexterm"></a><div class="para">
+ To run the <code class="systemitem">httpd</code> service, type
the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl start httpd.service</code></pre><div
class="para">
+ If you want the service to start automatically at the boot time, use the following
command:
+ </div><pre class="screen"><code
class="command">systemctl enable
httpd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div><div class="note"><div
class="admonition_header"><h2>Using the secure
server</h2></div><div class="admonition"><div
class="para">
+ If running the Apache HTTP Server as a secure server, a password may be required
after the machine boots if using an encrypted private SSL key.
+ </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"
id="s3-apache-running-stopping">12.1.4.2. Stopping the
Service</h4></div></div></div><a id="id977142"
class="indexterm"></a><div class="para">
+ To stop the running <code class="systemitem">httpd</code>
service, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl stop httpd.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at the boot time, type:
+ </div><pre class="screen"><code
class="command">systemctl disable
httpd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-apache-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-running-restarting">12.1.4.3. Restarting the
Service</h4></div></div></div><a id="id964857"
class="indexterm"></a><div class="para">
+ There are two different ways to restart the running <code
class="systemitem">httpd</code> service:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ To restart the service completely, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl restart
httpd.service</code></pre><div class="para">
+ This will stop the running <code
class="systemitem">httpd</code> service, and then start it again. Use
this command after installing or removing a dynamically loaded module such as PHP.
+ </div></li><li class="listitem"><div
class="para">
+ To only reload the configuration, as <code
class="systemitem">root</code>, type:
+ </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">
+ To reload the configuration without affecting active requests, run the following
command as <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">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-apache-running-status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-running-status">12.1.4.4. Checking the Service
Status</h4></div></div></div><a id="id660189"
class="indexterm"></a><div class="para">
+ To check whether the service is running, type the following at a shell prompt:
+ </div><pre class="screen"><code
class="command">systemctl is-active
httpd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div></div><div class="section"
id="s2-apache-editing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-apache-editing">12.1.5. Editing the Configuration
Files</h3></div></div></div><div class="para">
+ When the <code class="systemitem">httpd</code> service is
started, by default, it reads the configuration from locations that are listed in <a
class="xref" href="#table-apache-editing-files">Table 12.1, “The
httpd service configuration files”</a>.
+ </div><div class="table"
id="table-apache-editing-files"><h6>Table 12.1. The httpd service
configuration files</h6><div class="table-contents"><table
summary="The httpd service configuration files"
border="1"><colgroup><col width="33%"
class="option" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id964624" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf/httpd.conf</code>
+ </td><td>
+ The main configuration file.
+ </td></tr><tr><td>
+ <a id="id964583" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf.d/</code>
+ </td><td>
+ An auxiliary directory for configuration files that are included in the main
configuration file.
+ </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">Section 12.1.4.3, “Restarting the
Service”</a> for more information on how to restart the <code
class="systemitem">httpd</code> service.
+ </div><a id="id613570"
class="indexterm"></a><div class="para">
+ To check the configuration for possible errors, type the following at a shell prompt:
+ </div><pre class="screen"><code
class="command">service httpd configtest</code></pre><div
class="para">
+ To make the recovery from mistakes easier, it is recommended that you make a copy of
the original file before editing it.
+ </div><div class="section"
id="s3-apache-httpdconf-directives"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-httpdconf-directives">12.1.5.1. Common httpd.conf
Directives</h4></div></div></div><a id="id613536"
class="indexterm"></a><div class="para">
+ The following directives are commonly used in the <code
class="filename">/etc/httpd/conf/httpd.conf</code> configuration file:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id430162" class="indexterm"></a>
+ <code class="option"><Directory></code>
</span></dt><dd><div class="para">
+ The <code class="option"><Directory></code>
directive allows you to apply certain directives to a particular directory only. It takes
the following form:
+ </div><pre class="programlisting"><Directory <em
class="replaceable"><code>directory</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Directory></pre><div class="para">
+ The <em
class="replaceable"><code>directory</code></em> can be
either a full path to an existing directory in the local file system, or a wildcard
expression.
+ </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>Example 12.1. Using the
<Directory> directive</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="id1451583" class="indexterm"></a>
+ <code class="option"><IfDefine></code>
</span></dt><dd><div class="para">
+ The <code class="option">IfDefine</code> directive allows
you to use certain directives only when a particular parameter is supplied on the command
line. It takes the following form:
+ </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>Example 12.2. Using the
<IfDefine> directive</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="id755992" class="indexterm"></a>
+ <code class="option"><IfModule></code>
</span></dt><dd><div class="para">
+ The <code class="option"><IfModule></code>
directive allows you to use certain directive only when a particular module is loaded. It
takes the following form:
+ </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>Example 12.3. Using the
<IfModule> directive</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="id671008" class="indexterm"></a>
+ <code class="option"><Location></code>
</span></dt><dd><div class="para">
+ The <code class="option"><Location></code>
directive allows you to apply certain directives to a particular URL only. It takes the
following form:
+ </div><pre class="programlisting"><Location <em
class="replaceable"><code>url</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Location></pre><div class="para">
+ The <em
class="replaceable"><code>url</code></em> can be either a
path relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/server-info</code>), or an external URL such as
<code
class="literal">http://example.com/server-info</code>.
+ </div><div class="example"
id="example-apache-httpdconf-location"><h6>Example 12.4. Using the
<Location> directive</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="id662393" class="indexterm"></a>
+ <code class="option"><Proxy></code>
</span></dt><dd><div class="para">
+ The <code class="option"><Proxy></code>
directive allows you to apply certain directives to the proxy server only. It takes the
following form:
+ </div><pre class="programlisting"><Proxy <em
class="replaceable"><code>pattern</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Proxy></pre><div class="para">
+ The <em
class="replaceable"><code>pattern</code></em> can be an
external URL, or a wildcard expression (for example, <code
class="literal">http://example.com/*</code>).
+ </div><div class="example"
id="example-apache-httpdconf-proxy"><h6>Example 12.5. Using the
<Proxy> directive</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="id606578" class="indexterm"></a>
+ <code class="option"><VirtualHost></code>
</span></dt><dd><div class="para">
+ The <code class="option"><VirtualHost></code>
directive allows you apply certain directives to particular virtual hosts only. It takes
the following form:
+ </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">
+ The <em
class="replaceable"><code>address</code></em> can be an IP
address, a fully qualified domain name, or a special form as described in <a
class="xref" href="#table-apache-httpdconf-virtualhost">Table 12.2,
“Available <VirtualHost> options”</a>.
+ </div><div class="table"
id="table-apache-httpdconf-virtualhost"><h6>Table 12.2. Available
<VirtualHost> options</h6><div
class="table-contents"><table summary="Available
<VirtualHost> options" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">*</code>
+ </td><td>
+ Represents all IP addresses.
+ </td></tr><tr><td>
+ <code class="option">_default_</code>
+ </td><td>
+ Represents unmatched IP addresses.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-virtualhost"><h6>Example 12.6. Using the
<VirtualHost> directive</h6><div
class="example-contents"><pre
class="programlisting"><VirtualHost *:80>
+ ServerAdmin webmaster(a)penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName
penguin.example.com
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.example.com-access_log common
+</VirtualHost></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="id638908" 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="id638864" class="indexterm"></a><a
id="id464542" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>filename</code></em> is a name of
the file to look for in the requested directory. By default, the server looks for <code
class="filename">.htaccess</code>.
+ </div><a id="id464508"
class="indexterm"></a><a id="id464491"
class="indexterm"></a><div class="para">
+ For security reasons, the directive is typically followed by the <code
class="literal">Files</code> tag to prevent the files beginning with
<code class="filename">.ht</code> from being accessed by web
clients. This includes the <code class="filename">.htaccess</code>
and <code class="filename">.htpasswd</code> files.
+ </div><div class="example"
id="example-apache-httpdconf-accessfilename"><h6>Example 12.7. Using
the AccessFileName directive</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="id657984" class="indexterm"></a>
+ <code class="option">Action</code>
</span></dt><dd><div class="para">
+ The <code class="option">Action</code> directive allows you
to specify a CGI script to be executed when a certain media type is requested. It takes
the following form:
+ </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>Example 12.8. Using the Action
directive</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="id942159" 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>Example 12.9. Using
the AddDescription directive</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="id996082"
class="indexterm"></a>
+ <code class="option">AddEncoding</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddEncoding</code> directive allows
you to specify an encoding type for a particular file extension. It takes the following
form:
+ </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>Example 12.10. Using the
AddEncoding directive</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="id838828"
class="indexterm"></a>
+ <code class="option">AddHandler</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddHandler</code> directive allows
you to map certain file extensions to a selected handler. It takes the following form:
+ </div><pre class="programlisting">AddHandler <em
class="replaceable"><code>handler</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>handler</code></em> has to be a
name of previously defined handler. 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">.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>Example 12.11. Using the
AddHandler option</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="id829303"
class="indexterm"></a>
+ <code class="option">AddIcon</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddIcon</code> directive allows you
to specify an icon to be displayed for a particular file in server-generated directory
listings. It takes the following form:
+ </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>Table 12.3. Available AddIcon
options</h6><div class="table-contents"><table
summary="Available AddIcon options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">^^DIRECTORY^^</code>
+ </td><td>
+ Represents a directory.
+ </td></tr><tr><td>
+ <code class="option">^^BLANKICON^^</code>
+ </td><td>
+ Represents a blank line.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-addicon"><h6>Example 12.12. Using the
AddIcon directive</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="id580116"
class="indexterm"></a>
+ <code class="option">AddIconByEncoding</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddIconByEncoding</code> directive
allows you to specify an icon to be displayed for a particular encoding type in
server-generated directory listings. It takes the following form:
+ </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>Example 12.13. Using
the AddIconByEncoding directive</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="id580066"
class="indexterm"></a>
+ <code class="option">AddIconByType</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddIconByType</code> directive
allows you to specify an icon to be displayed for a particular media type in
server-generated directory listings. It takes the following form:
+ </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>Example 12.14. Using
the AddIconByType directive</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="id642193"
class="indexterm"></a>
+ <code class="option">AddLanguage</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddLanguage</code> directive allows
you to associate a file extension with a specific language. It takes the following form:
+ </div><pre class="programlisting">AddLanguage <em
class="replaceable"><code>language</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>language</code></em> has to be a
valid MIME language such as <code class="literal">cs</code>,
<code class="literal">en</code>, or <code
class="literal">fr</code>. 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="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>Example 12.15. Using the
AddLanguage directive</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="id564672"
class="indexterm"></a>
+ <code class="option">AddType</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddType</code> directive allows you
to define or override the media type for a particular file extension. It takes the
following form:
+ </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>Example 12.16. Using the
AddType directive</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="id943183"
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="id774325"
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>Example 12.17. Using the Alias
directive</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="id774265" 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>Example 12.18. Using the Allow
directive</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="id849409" class="indexterm"></a>
+ <code class="option">AllowOverride</code>
</span></dt><dd><a id="id849369"
class="indexterm"></a><a id="id1271673"
class="indexterm"></a><div class="para">
+ The <code class="option">AllowOverride</code> directive
allows you to specify which directives in a <code
class="filename">.htaccess</code> file can override the default
configuration. It takes the following form:
+ </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">Table 12.4, “Available
AllowOverride options”</a>.
+ </div><div class="table"
id="table-apache-httpdconf-allowoverride"><h6>Table 12.4. Available
AllowOverride options</h6><div class="table-contents"><table
summary="Available AllowOverride options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">All</code>
+ </td><td>
+ All directives in <code
class="filename">.htaccess</code> are allowed to override earlier
configuration settings.
+ </td></tr><tr><td>
+ <code class="option">None</code>
+ </td><td>
+ No directive in <code class="filename">.htaccess</code>
is allowed to override earlier configuration settings.
+ </td></tr><tr><td>
+ <code class="option">AuthConfig</code>
+ </td><td>
+ Allows the use of authorization directives such as <code
class="option">AuthName</code>, <code
class="option">AuthType</code>, or <code
class="option">Require</code>.
+ </td></tr><tr><td>
+ <code class="option">FileInfo</code>
+ </td><td>
+ 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>
+ <code class="option">Indexes</code>
+ </td><td>
+ Allows the use of directory indexing directives such as <code
class="option">AddDescription</code>, <code
class="option">AddIcon</code>, or <code
class="option">FancyIndexing</code>.
+ </td></tr><tr><td>
+ <code class="option">Limit</code>
+ </td><td>
+ Allows the use of host access directives, that is, <code
class="option">Allow</code>, <code
class="option">Deny</code>, and <code
class="option">Order</code>.
+ </td></tr><tr><td>
+ <code class="option">Options</code>[<span
class="optional">=<em
class="replaceable"><code>option</code></em>,…</span>]
+ </td><td>
+ Allows the use of the <code
class="option">Options</code> directive. Additionally, you can provide
a comma-separated list of options to customize which options can be set using this
directive.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-allowoverride"><h6>Example 12.19. Using
the AllowOverride directive</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="id622517"
class="indexterm"></a>
+ <code class="option">BrowserMatch</code>
</span></dt><dd><div class="para">
+ The <code class="option">BrowserMatch</code> directive
allows you to modify the server behavior based on the client's web browser type. It
takes the following form:
+ </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>Example 12.20. Using the
BrowserMatch directive</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="id908288"
class="indexterm"></a>
+ <code class="option">CacheDefaultExpire</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheDefaultExpire</code> option
allows you to set how long to cache a document that does not have any expiration date or
the date of its last modification specified. It takes the following form:
+ </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>Example 12.21. Using
the CacheDefaultExpire directive</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="id1009772"
class="indexterm"></a>
+ <code class="option">CacheDisable</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheDisable</code> directive
allows you to disable caching of certain URLs. It takes the following form:
+ </div><pre class="programlisting">CacheDisable <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> must be relative
to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/files/</code>).
+ </div><div class="example"
id="example-apache-httpdconf-cachedisable"><h6>Example 12.22. Using the
CacheDisable directive</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="id904483"
class="indexterm"></a>
+ <code class="option">CacheEnable</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheEnable</code> directive allows
you to specify a cache type to be used for certain URLs. It takes the following form:
+ </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">Table 12.5, “Available cache
types”</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>Table 12.5. Available cache
types</h6><div class="table-contents"><table
summary="Available cache types" border="1"><colgroup><col
width="25%" class="type" /><col width="75%"
class="description" /></colgroup><thead><tr><th>
+ Type
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">mem</code>
+ </td><td>
+ The memory-based storage manager.
+ </td></tr><tr><td>
+ <code class="option">disk</code>
+ </td><td>
+ The disk-based storage manager.
+ </td></tr><tr><td>
+ <code class="option">fd</code>
+ </td><td>
+ The file descriptor cache.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-cacheenable"><h6>Example 12.23. Using the
CacheEnable directive</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="id504868"
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>Example 12.24. Using
the CacheLastModifiedFactor directive</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="id504785"
class="indexterm"></a>
+ <code class="option">CacheMaxExpire</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheMaxExpire</code> directive
allows you to specify the maximum amount of time to cache a document. It takes the
following form:
+ </div><pre class="programlisting">CacheMaxExpire <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">86400</code>
(that is, one day).
+ </div><div class="example"
id="example-apache-httpdconf-cachemaxexpire"><h6>Example 12.25. Using
the CacheMaxExpire directive</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="id737861"
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">Table 12.6, “Available
CacheNegotiatedDocs options”</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>Table 12.6. Available
CacheNegotiatedDocs options</h6><div
class="table-contents"><table summary="Available CacheNegotiatedDocs
options" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables caching the content-negotiated documents.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ 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>Example 12.26. Using
the CacheNegotiatedDocs directive</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="id662169"
class="indexterm"></a>
+ <code class="option">CacheRoot</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheRoot</code> directive allows
you to specify the directory to store cache files in. It takes the following form:
+ </div><pre class="programlisting">CacheRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="id571326" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>directory</code></em> must be a
full path to an existing directory in the local file system. The default option is
<code class="filename">/var/cache/mod_proxy/</code>.
+ </div><div class="example"
id="example-apache-httpdconf-cacheroot"><h6>Example 12.27. Using the
CacheRoot directive</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="id571267" 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="id725624" 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>Example 12.28. Using the
CustomLog directive</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="id725559"
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>Example 12.29. Using the
DefaultIcon directive</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="id806236" class="indexterm"></a>
+ <code class="option">DefaultType</code>
</span></dt><dd><div class="para">
+ The <code class="option">DefaultType</code> directive allows
you to specify a media type to be used in case the proper MIME type cannot be determined
by the server. It takes the following form:
+ </div><pre class="programlisting">DefaultType <em
class="replaceable"><code>content-type</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>, <code
class="literal">application/pdf</code>, etc.
+ </div><div class="example"
id="example-apache-httpdconf-defaulttype"><h6>Example 12.30. Using the
DefaultType directive</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="id692922"
class="indexterm"></a>
+ <code class="option">Deny</code>
</span></dt><dd><div class="para">
+ The <code class="option">Deny</code> directive allows you to
specify which clients are denied access to a given directory. It takes the following
form:
+ </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>Example 12.31. Using the Deny
directive</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="id606081"
class="indexterm"></a>
+ <code class="option">DirectoryIndex</code>
</span></dt><dd><div class="para">
+ The <code class="option">DirectoryIndex</code> directive
allows you to specify a document to be served to a client when a directory is requested
(that is, when the URL ends with the <code class="literal">/</code>
character). It takes the following form:
+ </div><pre class="programlisting">DirectoryIndex <em
class="replaceable"><code>filename</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>filename</code></em> is a name of
the file to look for in the requested directory. By default, the server looks for <code
class="filename">index.html</code>, and <code
class="filename">index.html.var</code>.
+ </div><div class="example"
id="example-apache-httpdconf-directoryindex"><h6>Example 12.32. Using
the DirectoryIndex directive</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="id790002"
class="indexterm"></a>
+ <code class="option">DocumentRoot</code>
</span></dt><dd><div class="para">
+ The <code class="option">DocumentRoot</code> directive
allows you to specify the main directory from which the content is served. It takes the
following form:
+ </div><pre class="programlisting">DocumentRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="id789978" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>directory</code></em> must be a
full path to an existing directory in the local file system. The default option is
<code class="filename">/var/www/html/</code>.
+ </div><div class="example"
id="example-apache-httpdconf-documentroot"><h6>Example 12.33. Using the
DocumentRoot directive</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="id912320"
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>Example 12.34. Using
the ErrorDocument directive</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="id447036" 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="id541908" 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>Example 12.35. Using the
ErrorLog directive</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="id846483"
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">Table 12.7, “Available
ExtendedStatus options”</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-extendedstatus"><h6>Table 12.7. Available
ExtendedStatus options</h6><div class="table-contents"><table
summary="Available ExtendedStatus options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables generating the detailed server status.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables generating the detailed server status.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-extendedstatus"><h6>Example 12.36. Using
the ExtendedStatus directive</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="id607047"
class="indexterm"></a>
+ <code class="option">Group</code>
</span></dt><dd><div class="para">
+ The <code class="option">Group</code> directive allows you
to specify the group under which the <code
class="systemitem">httpd</code> service will run. It takes the
following form:
+ </div><pre class="programlisting">Group <em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>group</code></em> has to be an
existing UNIX group. The default option is <code
class="option">apache</code>.
+ </div><div class="para">
+ Note that <code class="option">Group</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-group"><h6>Example 12.37. Using the Group
directive</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="id792992" class="indexterm"></a>
+ <code class="option">HeaderName</code>
</span></dt><dd><div class="para">
+ The <code class="option">HeaderName</code> directive allows
you to specify a file to be prepended to the beginning of the server-generated directory
listing. It takes the following form:
+ </div><pre class="programlisting">HeaderName <em
class="replaceable"><code>filename</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>filename</code></em> is a name of
the file to look for in the requested directory. By default, the server looks for <code
class="filename">HEADER.html</code>.
+ </div><div class="example"
id="example-apache-httpdconf-headername"><h6>Example 12.38. Using the
HeaderName directive</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="id678882"
class="indexterm"></a>
+ <code class="option">HostnameLookups</code>
</span></dt><dd><div class="para">
+ The <code class="option">HostnameLookups</code> directive
allows you to enable automatic resolving of IP addresses. It takes the following form:
+ </div><pre class="programlisting">HostnameLookups <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-hostnamelookup">Table 12.8, “Available
HostnameLookups options”</a>. To conserve resources on the server, the default
option is <code class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-hostnamelookup"><h6>Table 12.8. Available
HostnameLookups options</h6><div class="table-contents"><table
summary="Available HostnameLookups options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables resolving the IP address for each connection so that the hostname can
be logged. However, this also adds a significant processing overhead.
+ </td></tr><tr><td>
+ <code class="option">Double</code>
+ </td><td>
+ Enables performing the double-reverse DNS lookup. In comparison to the above
option, this adds even more processing overhead.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables resolving the IP address for each connection.
+ </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>Example 12.39. Using
the HostnameLookups directive</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="id446588"
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="id446552" 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>Example 12.40. Using the
Include directive</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="id800661"
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">
+ The <em
class="replaceable"><code>filename</code></em> option can
be either a full file name, or a wildcard expression.
+ </div><div class="example"
id="example-apache-httpdconf-indexignore"><h6>Example 12.41. Using the
IndexIgnore directive</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="id539298"
class="indexterm"></a>
+ <code class="option">IndexOptions</code>
</span></dt><dd><div class="para">
+ The <code class="option">IndexOptions</code> directive
allows you to customize the behavior of server-generated directory listings. It takes the
following form:
+ </div><pre class="programlisting">IndexOptions <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-indexoptions">Table 12.9, “Available directory
listing options”</a>. The default options are <code
class="option">Charset=UTF-8</code>, <code
class="option">FancyIndexing</code>, <code
class="option">HTMLTable</code>, <code
class="option">NameWidth=*</code>, and <code
class="option">VersionSort</code>.
+ </div><div class="table"
id="table-apache-httpdconf-indexoptions"><h6>Table 12.9. Available
directory listing options</h6><div class="table-contents"><table
summary="Available directory listing options"
border="1"><colgroup><col width="33%"
class="option" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Charset</code>=<em
class="replaceable"><code>encoding</code></em>
+ </td><td>
+ 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>
+ <code class="option">Type</code>=<em
class="replaceable"><code>content-type</code></em>
+ </td><td>
+ 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>
+ <code class="option">DescriptionWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td>
+ 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>
+ <code class="option">FancyIndexing</code>
+ </td><td>
+ 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>
+ <code class="option">FolderFirst</code>
+ </td><td>
+ Enables listing directories first, always placing them above files.
+ </td></tr><tr><td>
+ <code class="option">HTMLTable</code>
+ </td><td>
+ Enables the use of HTML tables for directory listings.
+ </td></tr><tr><td>
+ <code class="option">IconsAreLinks</code>
+ </td><td>
+ Enables using the icons as links.
+ </td></tr><tr><td>
+ <code class="option">IconHeight</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies an icon height. The <em
class="replaceable"><code>value</code></em> is a number of
pixels.
+ </td></tr><tr><td>
+ <code class="option">IconWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies an icon width. The <em
class="replaceable"><code>value</code></em> is a number of
pixels.
+ </td></tr><tr><td>
+ <code class="option">IgnoreCase</code>
+ </td><td>
+ Enables sorting files and directories in a case-sensitive manner.
+ </td></tr><tr><td>
+ <code class="option">IgnoreClient</code>
+ </td><td>
+ Disables accepting query variables from a client.
+ </td></tr><tr><td>
+ <code class="option">NameWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td>
+ 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>
+ <code class="option">ScanHTMLTitles</code>
+ </td><td>
+ 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>
+ <code class="option">ShowForbidden</code>
+ </td><td>
+ Enables listing the files with otherwise restricted access.
+ </td></tr><tr><td>
+ <code class="option">SuppressColumnSorting</code>
+ </td><td>
+ Disables re-sorting a directory listing by clicking on a column header.
+ </td></tr><tr><td>
+ <code class="option">SuppressDescription</code>
+ </td><td>
+ Disables reserving a space for file descriptions.
+ </td></tr><tr><td>
+ <code class="option">SuppressHTMLPreamble</code>
+ </td><td>
+ 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>
+ <code class="option">SuppressIcon</code>
+ </td><td>
+ Disables the use of icons in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressLastModified</code>
+ </td><td>
+ Disables displaying the date of the last modification field in directory
listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressRules</code>
+ </td><td>
+ Disables the use of horizontal lines in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressSize</code>
+ </td><td>
+ Disables displaying the file size field in directory listings.
+ </td></tr><tr><td>
+ <code class="option">TrackModified</code>
+ </td><td>
+ Enables returning the <code
class="literal">Last-Modified</code> and <code
class="literal">ETag</code> values in the HTTP header.
+ </td></tr><tr><td>
+ <code class="option">VersionSort</code>
+ </td><td>
+ Enables sorting files that contain a version number in the expected manner.
+ </td></tr><tr><td>
+ <code class="option">XHTML</code>
+ </td><td>
+ Enables the use of XHTML 1.0 instead of the default HTML 3.2.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-indexoptions"><h6>Example 12.42. Using the
IndexOptions directive</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="id948023" 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">Table 12.10, “Available KeepAlive
options”</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-keepalive"><h6>Table 12.10. Available
KeepAlive options</h6><div class="table-contents"><table
summary="Available KeepAlive options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables the persistent connections. In this case, the server will accept more
than one request per connection.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables the keep-alive connections.
+ </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>Example 12.43. Using the
KeepAlive directive</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="id567976"
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">
+ The <em
class="replaceable"><code>time</code></em> is specified in
seconds. The default option is <code class="literal">15</code>.
+ </div><div class="example"
id="example-apache-httpdconf-keepalivetimeout"><h6>Example 12.44. Using
the KeepAliveTimeout directive</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="id584498"
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">
+ The <em
class="replaceable"><code>language</code></em> has to be a
valid MIME language such as <code class="literal">cs</code>,
<code class="literal">en</code>, or <code
class="literal">fr</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-languagepriority"><h6>Example 12.45. Using
the LanguagePriority directive</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="id547999"
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">
+ The <em
class="replaceable"><code>ip-address</code></em> is
optional and unless supplied, the server will accept incoming requests on a given <em
class="replaceable"><code>port</code></em> from all IP
addresses. Since the <em
class="replaceable"><code>protocol</code></em> is
determined automatically from the port number, it can be usually omitted. The default
option is to listen to port <code class="literal">80</code>.
+ </div><div class="para">
+ Note that if the server is configured to listen to a port under 1024, only
superuser will be able to start the <code
class="systemitem">httpd</code> service.
+ </div><div class="example"
id="example-apache-httpdconf-listen"><h6>Example 12.46. Using the
Listen directive</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="id562298" 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="id562235" class="indexterm"></a><a
id="id562225" 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">
+ Refer to <a class="xref"
href="#s2-apache-dso">Section 12.1.6, “Working with Modules”</a> for
more information on the Apache HTTP Server's DSO support.
+ </div><div class="example"
id="example-apache-httpdconf-loadmodule"><h6>Example 12.47. Using the
LoadModule directive</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="id833434" 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">Table 12.11, “Common LogFormat
options”</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>Table 12.11. Common LogFormat
options</h6><div class="table-contents"><table
summary="Common LogFormat options"
border="1"><colgroup><col width="13%"
class="option" /><col width="88%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">%b</code>
+ </td><td>
+ Represents the size of the response in bytes.
+ </td></tr><tr><td>
+ <code class="option">%h</code>
+ </td><td>
+ Represents the IP address or hostname of a remote client.
+ </td></tr><tr><td>
+ <code class="option">%l</code>
+ </td><td>
+ Represents the remote log name if supplied. If not, a hyphen (that is,
<code class="literal">-</code>) is used instead.
+ </td></tr><tr><td>
+ <code class="option">%r</code>
+ </td><td>
+ Represents the first line of the request string as it came from the browser or
client.
+ </td></tr><tr><td>
+ <code class="option">%s</code>
+ </td><td>
+ Represents the status code.
+ </td></tr><tr><td>
+ <code class="option">%t</code>
+ </td><td>
+ Represents the date and time of the request.
+ </td></tr><tr><td>
+ <code class="option">%u</code>
+ </td><td>
+ 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>
+ <code class="option">%{<em
class="replaceable"><code>field</code></em>}</code>
+ </td><td>
+ 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>Example 12.48. Using the
LogFormat directive</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="id668756" 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">Table 12.12, “Available LogLevel
options”</a>. The default option is <code
class="option">warn</code>.
+ </div><div class="table"
id="table-apache-httpdconf-loglevel"><h6>Table 12.12. Available
LogLevel options</h6><div class="table-contents"><table
summary="Available LogLevel options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">emerg</code>
+ </td><td>
+ Only the emergency situations when the server cannot perform its work are
logged.
+ </td></tr><tr><td>
+ <code class="option">alert</code>
+ </td><td>
+ All situations when an immediate action is required are logged.
+ </td></tr><tr><td>
+ <code class="option">crit</code>
+ </td><td>
+ All critical conditions are logged.
+ </td></tr><tr><td>
+ <code class="option">error</code>
+ </td><td>
+ All error messages are logged.
+ </td></tr><tr><td>
+ <code class="option">warn</code>
+ </td><td>
+ All warning messages are logged.
+ </td></tr><tr><td>
+ <code class="option">notice</code>
+ </td><td>
+ Even normal, but still significant situations are logged.
+ </td></tr><tr><td>
+ <code class="option">info</code>
+ </td><td>
+ Various informational messages are logged.
+ </td></tr><tr><td>
+ <code class="option">debug</code>
+ </td><td>
+ Various debugging messages are logged.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-loglevel"><h6>Example 12.49. Using the
LogLevel directive</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="id707781"
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>Example 12.50. Using
the MaxKeepAliveRequests option</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="id909289"
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>Using secure HTTP
connections</h2></div><div class="admonition"><div
class="para">
+ Name-based virtual hosts <span
class="emphasis"><em>only</em></span> work with non-secure
HTTP connections. If using virtual hosts with a secure server, use IP address-based
virtual hosts instead.
+ </div></div></div><div class="example"
id="example-apache-httpdconf-namevirtualhost"><h6>Example 12.51. Using
the NameVirtualHost directive</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="id1226458"
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">
+ The <em
class="replaceable"><code>option</code></em> has to be a
valid keyword as described in <a class="xref"
href="#table-apache-httpdconf-options">Table 12.13, “Available server
features”</a>.
+ </div><div class="table"
id="table-apache-httpdconf-options"><h6>Table 12.13. Available server
features</h6><div class="table-contents"><table
summary="Available server features"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">ExecCGI</code>
+ </td><td>
+ Enables the execution of CGI scripts.
+ </td></tr><tr><td>
+ <code class="option">FollowSymLinks</code>
+ </td><td>
+ Enables following symbolic links in the directory.
+ </td></tr><tr><td>
+ <code class="option">Includes</code>
+ </td><td>
+ Enables server-side includes.
+ </td></tr><tr><td>
+ <code class="option">IncludesNOEXEC</code>
+ </td><td>
+ Enables server-side includes, but does not allow the execution of commands.
+ </td></tr><tr><td>
+ <code class="option">Indexes</code>
+ </td><td>
+ Enables server-generated directory listings.
+ </td></tr><tr><td>
+ <code class="option">MultiViews</code>
+ </td><td>
+ Enables content-negotiated <span class="quote">“<span
class="quote">MultiViews</span>”</span>.
+ </td></tr><tr><td>
+ <code class="option">SymLinksIfOwnerMatch</code>
+ </td><td>
+ Enables following symbolic links in the directory when both the link and the
target file have the same owner.
+ </td></tr><tr><td>
+ <code class="option">All</code>
+ </td><td>
+ Enables all of the features above with the exception of <code
class="option">MultiViews</code>.
+ </td></tr><tr><td>
+ <code class="option">None</code>
+ </td><td>
+ Disables all of the features above.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-options"><h6>Example 12.52. Using the
Options directive</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="id798906"
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">Table 12.14, “Available Order
options”</a>. The default option is <code
class="option">allow,deny</code>.
+ </div><div class="table"
id="table-apache-httpdconf-order"><h6>Table 12.14. Available Order
options</h6><div class="table-contents"><table
summary="Available Order options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow,deny</code>
+ </td><td>
+ <code class="option">Allow</code> directives are
evaluated first.
+ </td></tr><tr><td>
+ <code class="option">deny,allow</code>
+ </td><td>
+ <code class="option">Deny</code> directives are
evaluated first.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-order"><h6>Example 12.53. Using the Order
directive</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="id953665"
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="id953615" 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>Example 12.54. Using the
PidFile directive</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="id692058"
class="indexterm"></a>
+ <code class="option">ProxyRequests</code>
</span></dt><dd><div class="para">
+ The <code class="option">ProxyRequests</code> directive
allows you to enable forward proxy requests. It takes the following form:
+ </div><pre class="programlisting">ProxyRequests <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-proxyrequests">Table 12.15, “Available
ProxyRequests options”</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-proxyrequests"><h6>Table 12.15. Available
ProxyRequests options</h6><div class="table-contents"><table
summary="Available ProxyRequests options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables forward proxy requests.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables forward proxy requests.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-proxyrequests"><h6>Example 12.55. Using
the ProxyRequests directive</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="id901130"
class="indexterm"></a>
+ <code class="option">ReadmeName</code>
</span></dt><dd><div class="para">
+ The <code class="option">ReadmeName</code> directive allows
you to specify a file to be appended to the end of the server-generated directory listing.
It takes the following form:
+ </div><pre class="programlisting">ReadmeName <em
class="replaceable"><code>filename</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>filename</code></em> is a name of
the file to look for in the requested directory. By default, the server looks for <code
class="filename">README.html</code>.
+ </div><div class="example"
id="example-apache-httpdconf-readmename"><h6>Example 12.56. Using the
ReadmeName directive</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="id901060"
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">Table 12.16, “Available status
options”</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>Table 12.16. Available status
options</h6><div class="table-contents"><table
summary="Available status options"
border="1"><colgroup><col width="25%"
class="status" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Status
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">permanent</code>
+ </td><td>
+ 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>
+ <code class="option">temp</code>
+ </td><td>
+ Indicates that the requested resource has been moved only temporarily. The
<code class="literal">302</code> (Found) status code is returned to
a client.
+ </td></tr><tr><td>
+ <code class="option">seeother</code>
+ </td><td>
+ Indicates that the requested resource has been replaced. The <code
class="literal">303</code> (See Other) status code is returned to a
client.
+ </td></tr><tr><td>
+ <code class="option">gone</code>
+ </td><td>
+ Indicates that the requested resource has been removed permanently. The
<code class="literal">410</code> (Gone) status is returned to a
client.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="id952856"
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>Example 12.57. Using the
Redirect directive</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="id952801" class="indexterm"></a>
+ <code class="option">ScriptAlias</code>
</span></dt><dd><div class="para">
+ The <code class="option">ScriptAlias</code> directive allows
you to specify the location of CGI scripts. It takes the following form:
+ </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="id664872"
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>Example 12.58. Using the
ScriptAlias directive</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="id635158" 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">
+ The default option is <code
class="literal">root@localhost</code>.
+ </div><div class="para">
+ This directive is commonly set to <code
class="literal">webmaster@<em
class="replaceable"><code>hostname</code></em></code>,
where <em class="replaceable"><code>hostname</code></em>
is the address of the server. Once set, alias <code
class="literal">webmaster</code> to the person responsible for the web
server in <code class="filename">/etc/aliases</code>, and as
superuser, run the <code class="command">newaliases</code> command.
+ </div><div class="example"
id="example-apache-httpdconf-serveradmin"><h6>Example 12.59. Using the
ServerAdmin directive</h6><div class="example-contents"><pre
class="programlisting">ServerAdmin
webmaster(a)penguin.example.com</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="id629313" 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>Example 12.60. Using the
ServerName directive</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="id533022" class="indexterm"></a>
+ <code class="option">ServerRoot</code>
</span></dt><dd><div class="para">
+ The <code class="option">ServerRoot</code> directive allows
you to specify the directory in which the server operates. It takes the following form:
+ </div><pre class="programlisting">ServerRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="id855508" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>directory</code></em> must be a
full path to an existing directory in the local file system. The default option is
<code class="filename">/etc/httpd/</code>.
+ </div><div class="example"
id="example-apache-httpd-serverroot"><h6>Example 12.61. Using the
ServerRoot directive</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="id855451"
class="indexterm"></a>
+ <code class="option">ServerSignature</code>
</span></dt><dd><div class="para">
+ The <code class="option">ServerSignature</code> directive
allows you to enable displaying information about the server on server-generated
documents. It takes the following form:
+ </div><pre class="programlisting">ServerSignature <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-serversignature">Table 12.17, “Available
ServerSignature options”</a>. The default option is <code
class="option">On</code>.
+ </div><div class="table"
id="table-apache-httpdconf-serversignature"><h6>Table 12.17. Available
ServerSignature options</h6><div class="table-contents"><table
summary="Available ServerSignature options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables appending the server name and version to server-generated pages.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables appending the server name and version to server-generated pages.
+ </td></tr><tr><td>
+ <code class="option">EMail</code>
+ </td><td>
+ 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>Example 12.62. Using
the ServerSignature directive</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="id573986"
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">Table 12.18, “Available
ServerTokens options”</a>. The default option is <code
class="option">OS</code>.
+ </div><div class="table"
id="table-apache-httpdconf-servertokens"><h6>Table 12.18. Available
ServerTokens options</h6><div class="table-contents"><table
summary="Available ServerTokens options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Prod</code>
+ </td><td>
+ Includes the product name only (that is, <code
class="literal">Apache</code>).
+ </td></tr><tr><td>
+ <code class="option">Major</code>
+ </td><td>
+ Includes the product name and the major version of the server (for example,
<code class="literal">2</code>).
+ </td></tr><tr><td>
+ <code class="option">Minor</code>
+ </td><td>
+ Includes the product name and the minor version of the server (for example,
<code class="literal">2.2</code>).
+ </td></tr><tr><td>
+ <code class="option">Min</code>
+ </td><td>
+ Includes the product name and the minimal version of the server (for example,
<code class="literal">2.2.15</code>).
+ </td></tr><tr><td>
+ <code class="option">OS</code>
+ </td><td>
+ Includes the product name, the minimal version of the server, and the type of
the operating system it is running on (for example, <code
class="literal">Red Hat</code>).
+ </td></tr><tr><td>
+ <code class="option">Full</code>
+ </td><td>
+ Includes all the information above along with the list of loaded modules.
+ </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>Example 12.63. Using the
ServerTokens directive</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="id509074"
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>Example 12.64. Using
the SuexecUserGroup directive</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="id626022"
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">
+ The <em
class="replaceable"><code>time</code></em> is specified in
seconds. The default option is <code class="literal">60</code>.
+ </div><div class="example"
id="example-apache-httpdconf-timeout"><h6>Example 12.65. Using the
Timeout directive</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="id677660" class="indexterm"></a>
+ <code class="option">TypesConfig</code>
</span></dt><dd><div class="para">
+ The <code class="option">TypesConfig</code> allows you to
specify the location of the MIME types configuration file. It takes the following form:
+ </div><pre class="programlisting">TypesConfig <em
class="replaceable"><code>path</code></em></pre><a
id="id677618" 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>Example 12.66. Using the
TypesConfig directive</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="id590194"
class="indexterm"></a>
+ <code class="option">UseCanonicalName</code>
</span></dt><dd><div class="para">
+ The <code class="option">UseCanonicalName</code> allows you
to specify the way the server refers to itself. It takes the following form:
+ </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">Table 12.19, “Available
UseCanonicalName options”</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-usecanonicalname"><h6>Table 12.19. Available
UseCanonicalName options</h6><div class="table-contents"><table
summary="Available UseCanonicalName options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables the use of the name that is specified by the <code
class="option">ServerName</code> directive.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ 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>
+ <code class="option">DNS</code>
+ </td><td>
+ 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>Example 12.67. Using
the UseCanonicalName directive</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="id603184"
class="indexterm"></a>
+ <code class="option">User</code>
</span></dt><dd><div class="para">
+ The <code class="option">User</code> directive allows you to
specify the user under which the <code
class="systemitem">httpd</code> service will run. It takes the
following form:
+ </div><pre class="programlisting">User <em
class="replaceable"><code>user</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>user</code></em> has to be an
existing UNIX user. The default option is <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>Example 12.68. Using the User
directive</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="id472554" class="indexterm"></a>
+ <code class="option">UserDir</code>
</span></dt><dd><div class="para">
+ The <code class="option">UserDir</code> directive allows you
to enable serving content from users' home directories. It takes the following form:
+ </div><pre class="programlisting">UserDir <em
class="replaceable"><code>option</code></em></pre><a
id="id493144" 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">Table 12.20, “Available UserDir
options”</a>. The default option is <code
class="option">disabled</code>.
+ </div><div class="table"
id="table-apache-httpdconf-userdir"><h6>Table 12.20. Available UserDir
options</h6><div class="table-contents"><table
summary="Available UserDir options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">enabled</code> <em
class="replaceable"><code>user</code></em>…
+ </td><td>
+ Enables serving content from home directories of given <em
class="replaceable"><code>user</code></em>s.
+ </td></tr><tr><td>
+ <code class="option">disabled</code> [<span
class="optional"><em
class="replaceable"><code>user</code></em>…</span>]
+ </td><td>
+ 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>Set the correct
permissions</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>Example 12.69. Using the
UserDir directive</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"
id="s3-apache-sslconf-common">12.1.5.2. Common ssl.conf
Directives</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="id1249871"
class="indexterm"></a><div class="para">
+ The following directive is commonly used in <code
class="filename">/etc/httpd/conf.d/ssl.conf</code>:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id1249836" 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">Table 12.21, “Available SetEnvIf
options”</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>Table 12.21. Available SetEnvIf
options</h6><div class="table-contents"><table
summary="Available SetEnvIf options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Remote_Host</code>
+ </td><td>
+ Refers to the client's hostname.
+ </td></tr><tr><td>
+ <code class="option">Remote_Addr</code>
+ </td><td>
+ Refers to the client's IP address.
+ </td></tr><tr><td>
+ <code class="option">Server_Addr</code>
+ </td><td>
+ Refers to the server's IP address.
+ </td></tr><tr><td>
+ <code class="option">Request_Method</code>
+ </td><td>
+ Refers to the request method (for example, <code
class="literal">GET</code>).
+ </td></tr><tr><td>
+ <code class="option">Request_Protocol</code>
+ </td><td>
+ Refers to the protocol name and version (for example, <code
class="literal">HTTP/1.1</code>).
+ </td></tr><tr><td>
+ <code class="option">Request_URI</code>
+ </td><td>
+ Refers to the requested resource.
+ </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>Example 12.70. Using the
SetEnvIf directive</h6><div class="example-contents"><pre
class="programlisting">SetEnvIf User-Agent ".*MSIE.*" \
+ nokeepalive ssl-unclean-shutdown \
+ downgrade-1.0 force-response-1.0</pre></div></div><br
class="example-break" /></dd></dl></div><div
class="para">
+ Note that for the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> file to be present,
the <span class="package">mod_ssl</span> needs to be installed.
Refer to <a class="xref"
href="#s2-apache-mod_ssl">Section 12.1.8, “Setting Up an SSL
Server”</a> for more information on how to install and configure an SSL server.
+ </div></div><div class="section"
id="s3-apache-mpm-common"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-mpm-common">12.1.5.3. Common Multi-Processing Module
Directives</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="id1249681"
class="indexterm"></a><div class="para">
+ The following MPM directives are commonly used in <code
class="filename">/etc/httpd/conf/httpd.conf</code>:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id1249648" 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>Example 12.71. Using the
MaxClients directive</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="id891314"
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>Example 12.72. Using
the MaxRequestsPerChild directive</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="id1293750"
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">
+ This directive is used by the <code
class="systemitem">prefork</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-maxspareservers"><h6>Example 12.73. Using the
MaxSpareServers directive</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="id611563"
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>Example 12.74. Using the
MaxSpareThreads directive</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="id997081"
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>Example 12.75. Using the
MinSpareServers directive</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="id996997"
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">
+ This directive is used by the <code
class="systemitem">worker</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-minsparethreads"><h6>Example 12.76. Using the
MinSpareThreads directive</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="id586886"
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>Example 12.77. Using the
StartServers directive</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="id637048"
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">
+ This directive is used by the <code
class="systemitem">worker</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-threadsperchild"><h6>Example 12.78. Using the
ThreadsPerChild directive</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"
id="s2-apache-dso">12.1.6. Working with
Modules</h3></div></div></div><a id="id1280311"
class="indexterm"></a><a id="id1280288"
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"
id="s3-apache-dso-loading">12.1.6.1. Loading a
Module</h4></div></div></div><a id="id926124"
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">Section 12.1.5.1, “Common httpd.conf
Directives”</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>Example 12.79. Loading the 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">Section 12.1.4.3, “Restarting the
Service”</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"
id="s3-apache-dso-writing">12.1.6.2. Writing a
Module</h4></div></div></div><a id="id555383"
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"
id="s2-apache-virtualhosts">12.1.7. Setting Up Virtual
Hosts</h3></div></div></div><a id="id555308"
class="indexterm"></a><a id="id799425"
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">Example 12.80, “Sample virtual
host configuration”</a>.
+ </div><div class="example"
id="example-apache-virtualhosts-config"><h6>Example 12.80. Sample
virtual host configuration</h6><div class="example-contents"><pre
class="programlisting">NameVirtualHost penguin.example.com:80
+
+<VirtualHost penguin.example.com:80>
+ ServerAdmin webmaster(a)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>Changing the port
number</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">Section 12.1.4.3, “Restarting the
Service”</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"
id="s2-apache-mod_ssl">12.1.8. Setting Up an SSL
Server</h3></div></div></div><a id="id893345"
class="indexterm"></a><a id="id543972"
class="indexterm"></a><a id="id893312"
class="indexterm"></a><a id="id543948"
class="indexterm"></a><a id="id543940"
class="indexterm"></a><a id="id543922"
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"
id="s3-apache-mod_ssl-certificates">12.1.8.1. An Overview of Certificates and
Security</h4></div></div></div><a id="id826183"
class="indexterm"></a><a id="id826180"
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="id826141"
class="indexterm"></a><a id="id1058502"
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">Table 12.22, “CA lists
for most common web browsers”</a>.
+ </div><div class="table"
id="table-apache-mod_ssl-certificates-authorities"><h6>Table 12.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>
+ Web Browser
+ </th><th>
+ Link
+ </th></tr></thead><tbody><tr><td>
+ <span class="application"><strong>Mozilla
Firefox</strong></span>
+ </td><td>
+ <a
href="http://www.mozilla.org/projects/security/certs/included/"... root
CA list</a>.
+ </td></tr><tr><td>
+ <span
class="application"><strong>Opera</strong></span>
+ </td><td>
+ <a
href="http://my.opera.com/rootstore/blog/">The Opera
Rootstore</a>.
+ </td></tr><tr><td>
+ <span class="application"><strong>Internet
Explorer</strong></span>
+ </td><td>
+ <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"
id="s3-apache-mod_ssl-enabling">12.1.8.2. Enabling the mod_ssl
Module</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="id696569" 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">Section 12.1.4.3, “Restarting the
Service”</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"
id="s3-apache-mod_ssl-keypair">12.1.8.3. Using an Existing Key and
Certificate</h4></div></div></div><a id="id462739"
class="indexterm"></a><a id="id462722"
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">
+ Certificates are issued for a particular IP address and domain name pair. If one of
these values changes, the certificate becomes invalid.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>You have a certificate from
VeriSign, and you are changing the server software.</em></span>
+ </div><div class="para">
+ VeriSign, a widely used certificate authority, issues certificates for a particular
software product, IP address, and domain name. Changing the software product renders the
certificate invalid.
+ </div></li></ol></div><div class="para">
+ In either of the above cases, you will need to obtain a new certificate. For more
information on this topic, refer to <a class="xref"
href="#s3-apache-mod_ssl-genkey">Section 12.1.8.4, “Generating a New Key and
Certificate”</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">
+ Then add the following lines to the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> configuration file:
+ </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">
+ To load the updated configuration, restart the <code
class="systemitem">httpd</code> service as described in <a
class="xref" href="#s3-apache-running-restarting">Section 12.1.4.3,
“Restarting the Service”</a>.
+ </div><div class="example"
id="example-apache-mod_ssl-keypair"><h6>Example 12.81. Using a key and
certificate from the Red Hat Secure Web Server</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">mv /etc/httpd/conf/httpsd.key
/etc/pki/tls/private/penguin.example.com.key</code>
+~]# <code class="command">mv /etc/httpd/conf/httpsd.crt
/etc/pki/tls/certs/penguin.example.com.crt</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="s3-apache-mod_ssl-genkey"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-mod_ssl-genkey">12.1.8.4. Generating a New Key and
Certificate</h4></div></div></div><a id="id426631"
class="indexterm"></a><a id="id485871"
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>Replacing an existing
certificate</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>Remove
a previously created key</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">
+ To run the utility, as <code class="systemitem">root</code>,
run the <code class="command">genkey</code> command followed by the
appropriate hostname (for example, <code
class="systemitem">penguin.example.com</code>):
+ </div><pre class="screen"><code
class="command">genkey</code> <em
class="replaceable"><code>hostname</code></em></pre><div
class="para">
+ To complete the key and certificate creation, take the following steps:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Review the target locations in which the key and certificate will be stored.
+ </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="Running the genkey
utility" /><div class="longdesc"><div
class="para">
+ Running the <span
class="application"><strong>genkey</strong></span> utility
+ </div></div></div></div><h6>Figure 12.1. Running
the genkey utility</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 proceed to
the next screen.
+ </div></li><li class="step"><div
class="para">
+ Using the <span
class="keycap"><strong>Up</strong></span> and <span
class="keycap"><strong>down</strong></span> arrow keys,
select the suitable key size. Note that while the large key increases the security, it
also increases the response time of your server. Because of this, the recommended option
is <code class="literal">1024 bits</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="Selecting the key size"
/><div class="longdesc"><div class="para">
+ Selecting the key size
+ </div></div></div></div><h6>Figure 12.2. Selecting
the key size</h6></div><br class="figure-break" /><div
class="para">
+ Once finished, 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 initiate
the random bits generation process. Depending on the selected key size, this may take some
time.
+ </div></li><li class="step"><div
class="para">
+ Decide whether you wish to send a certificate request to a certificate authority.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-03"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-03.png" alt="Generating a certificate
request" /><div class="longdesc"><div
class="para">
+ Generating a certificate request
+ </div></div></div></div><h6>Figure 12.3. Generating
a certificate request</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>Figure 12.4. Encrypting
the private key</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 proceed to
the next screen.
+ </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>Figure 12.5. Entering a
passphrase</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 proceed to
the next screen.
+ </div><div class="important"><div
class="admonition_header"><h2>Do not forget the
passphrase</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="Specifying certificate
information" /><div class="longdesc"><div
class="para">
+ Specifying certificate information
+ </div></div></div></div><h6>Figure 12.6. Specifying
certificate information</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>Figure 12.7. Instructions
on how to send a certificate request</h6></div><br
class="figure-break" /><div class="para">
+ Press <span
class="keycap"><strong>Enter</strong></span> to return to a
shell prompt.
+ </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">
+ Finally, restart the <code class="systemitem">httpd</code>
service as described in <a class="xref"
href="#s3-apache-running-restarting">Section 12.1.4.3, “Restarting the
Service”</a>, so that the updated configuration is loaded.
+ </div></div></div><div class="section"
id="s2-apache-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-apache-resources">12.1.9. Additional
Resources</h3></div></div></div><div
class="para">
+ To learn more about the Apache HTTP Server, refer to the following resources.
+ </div><div class="section"
id="s3-apache-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-resources-installed">12.1.9.1. Installed
Documentation</h4></div></div></div><a id="id701046"
class="indexterm"></a><div
class="variablelist"><dl><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">
+ The manual page for the <code
class="systemitem">httpd</code> service containing the complete list of
its command line options.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
genkey</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">genkey</code>
containing the full documentation on its usage.
+ </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"
id="s3-apache-resources-web">12.1.9.2. Useful
Websites</h4></div></div></div><a id="id719659"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://httpd.apache.org/">http://httpd.apache.org/<...
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&g...
class="para">
+ The official website for the <span
class="application"><strong>mod_ssl</strong></span>
module.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.openssl.org/">http://www.openssl.org/</a...
class="para">
+ The OpenSSL home page containing further documentation, frequently asked
questions, links to the mailing lists, and other useful resources.
+ </div></dd></dl></div></div></div></div></div><div
xml:lang="en-US" class="chapter" id="ch-Mail_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 13. Mail
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-email-protocols">13.1. Email
Protocols</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-protocols-send">13.1.1.
Mail Transport Protocols</a></span></dt><dt><span
class="section"><a href="#s2-email-protocols-client">13.1.2.
Mail Access
Protocols</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-types">13.2. Email Program
Classifications</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-types-mta">13.2.1. Mail
Transport Agent</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mda">13.2.2. Mail
Delivery Agent</a></span></dt><dt><span
class="section"><a href="#s2-email-types-mua">13.2.3. Mail
User Agent</a></span></dt></dl></dd><
dt><span class="section"><a href="#s1-email-mta">13.3.
Mail Transport
Agents</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-mta-postfix">13.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-sendmail">13.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="#s2-email-mta-fetchmail">13.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="#s2-email-switchmail">13.3.4. Mail
Transport Agent (MTA)
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mda">13.4. Mail Delivery
Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-email-procmail-configuration">13.4.1. Procmail
Configuration</a></span></dt><dt><span
class="section"><a href="#s2-email-procmail-recipes">13.4.2.
Procmail Recipes</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-email-mua">13.5. Mail User
Agents</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-security">13.5.1
. Securing
Communication</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-email-additional-resources">13.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-installed-docs">13.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="#s2-email-useful-websites">13.6.2.
Useful Websites</a></span></dt><dt><span
class="section"><a href="#s2-email-related-books">13.6.3.
Related
Books</a></span></dt></dl></dd></dl></div><a
id="id912199" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Email</em> was born in the 1960s. The
mailbox was a file in a user's home directory that was readable only by that user.
Primitive mail applications appended new text messages to the bottom of the file, making
the user wade through the constantly growing file to find any particular message. This
system was only capable of sending messages to users on the same system.
+ </div><div class="para">
+ The first network transfer of an electronic mail message file took place in 1971 when a
computer engineer named Ray Tomlinson sent a test message between two machines via
ARPANET—the precursor to the Internet. Communication via email soon became very popular,
comprising 75 percent of ARPANET's traffic in less than two years.
+ </div><div class="para">
+ Today, email systems based on standardized network protocols have evolved into some of
the most widely used services on the Internet. Fedora offers many advanced applications to
serve and access email.
+ </div><div class="para">
+ This chapter reviews modern email protocols in use today, and some of the programs
designed to send and receive email.
+ </div><div class="section"
id="s1-email-protocols"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-email-protocols">13.1. Email
Protocols</h2></div></div></div><a id="id812217"
class="indexterm"></a><div class="para">
+ Today, email is delivered using a client/server architecture. An email message is
created using a mail client program. This program then sends the message to a server. The
server then forwards the message to the recipient's email server, where the message is
then supplied to the recipient's email client.
+ </div><div class="para">
+ To enable this process, a variety of standard network protocols allow different
machines, often running different operating systems and using different email programs, to
send and receive email.
+ </div><div class="para">
+ The following protocols discussed are the most commonly used in the transfer of
email.
+ </div><div class="section"
id="s2-email-protocols-send"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-protocols-send">13.1.1. Mail Transport
Protocols</h3></div></div></div><div
class="para">
+ Mail delivery from a client application to the server, and from an originating server
to the destination server, is handled by the <em class="firstterm">Simple
Mail Transfer Protocol</em> (<em
class="firstterm">SMTP</em>).
+ </div><div class="section"
id="s3-email-protocols-smtp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-protocols-smtp">13.1.1.1. SMTP</h4></div></div></div><a
id="id467988" class="indexterm"></a><div
class="para">
+ The primary purpose of SMTP is to transfer email between mail servers. However, it
is critical for email clients as well. To send email, the client sends the message to an
outgoing mail server, which in turn contacts the destination mail server for delivery. For
this reason, it is necessary to specify an SMTP server when configuring an email client.
+ </div><div class="para">
+ Under Fedora, a user can configure an SMTP server on the local machine to handle
mail delivery. However, it is also possible to configure remote SMTP servers for outgoing
mail.
+ </div><div class="para">
+ One important point to make about the SMTP protocol is that it does not require
authentication. This allows anyone on the Internet to send email to anyone else or even to
large groups of people. It is this characteristic of SMTP that makes junk email or <em
class="firstterm">spam</em> possible. Imposing relay restrictions
limits random users on the Internet from sending email through your SMTP server, to other
servers on the internet. Servers that do not impose such restrictions are called <em
class="firstterm">open relay</em> servers.
+ </div><div class="para">
+ Fedora provides the Postfix and Sendmail SMTP programs.
+ </div></div></div><div class="section"
id="s2-email-protocols-client"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-protocols-client">13.1.2. Mail Access
Protocols</h3></div></div></div><div
class="para">
+ There are two primary protocols used by email client applications to retrieve email
from mail servers: the <em class="firstterm">Post Office
Protocol</em> (<em class="firstterm">POP</em>) and the <em
class="firstterm">Internet Message Access Protocol</em> (<em
class="firstterm">IMAP</em>).
+ </div><div class="section"
id="s3-email-protocols-pop"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-protocols-pop">13.1.2.1. POP</h4></div></div></div><a
id="id977244" class="indexterm"></a><div
class="para">
+ The default POP server under Fedora is <span
class="application"><strong>Dovecot</strong></span> and is
provided by the <span class="package">dovecot</span> package.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the dovecot
package</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>Dovecot</strong></span>, first
ensure the <code class="command">dovecot</code> package is installed
on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">yum install dovecot</code></pre><div
class="para">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ When using a <code class="systemitem">POP</code> server, email
messages are downloaded by email client applications. By default, most <code
class="systemitem">POP</code> email clients are automatically
configured to delete the message on the email server after it has been successfully
transferred, however this setting usually can be changed.
+ </div><div class="para">
+ <code class="systemitem">POP</code> is fully compatible with
important Internet messaging standards, such as <em
class="firstterm">Multipurpose Internet Mail Extensions</em> (<em
class="firstterm">MIME</em>), which allow for email attachments.
+ </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">
+ The most current version of the standard <code
class="systemitem">POP</code> protocol is <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> with Kerberos authentication.
+ </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">Section 13.5.1, “Securing
Communication”</a>.
+ </div></div><div class="section"
id="s3-email-protocols-imap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-protocols-imap">13.1.2.2. IMAP</h4></div></div></div><a
id="id911271" class="indexterm"></a><div
class="para">
+ The default <code class="systemitem">IMAP</code> server under
Fedora is <span
class="application"><strong>Dovecot</strong></span> and is
provided by the <span class="package">dovecot</span> package. Refer
to <a class="xref"
href="#s3-email-protocols-pop">Section 13.1.2.1, “POP”</a> for
information on how to install <span
class="application"><strong>Dovecot</strong></span>.
+ </div><div class="para">
+ When using an <code class="systemitem">IMAP</code> mail
server, email messages remain on the server where users can read or delete them. <code
class="systemitem">IMAP</code> also allows client applications to
create, rename, or delete mail directories on the server to organize and store email.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code> is particularly useful
for users who access their email using multiple machines. The protocol is also convenient
for users connecting to the mail server via a slow connection, because only the email
header information is downloaded for messages until opened, saving bandwidth. The user
also has the ability to delete messages without viewing or downloading them.
+ </div><div class="para">
+ For convenience, <code class="systemitem">IMAP</code> client
applications are capable of caching copies of messages locally, so the user can browse
previously read messages when not directly connected to the <code
class="systemitem">IMAP</code> server.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code>, like <code
class="systemitem">POP</code>, is fully compatible with important
Internet messaging standards, such as MIME, which allow for email attachments.
+ </div><div class="para">
+ For added security, it is possible to use <code
class="systemitem">SSL</code> encryption for client authentication and
data transfer sessions. This can be enabled by using the <code
class="command">imaps</code> service, or by using the <code
class="command">/usr/sbin/stunnel</code> program. For more information
on securing email communication, refer to <a class="xref"
href="#s2-email-security">Section 13.5.1, “Securing
Communication”</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"
id="s3-mail-server-dovecot">13.1.2.3. Dovecot</h4></div></div></div><a
id="id441055" 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">
+ Make that change operational after the next reboot by running the command:
+ </div><pre class="screen"><code
class="command">systemctl enable
dovecot.service</code></pre><div class="note"><div
class="admonition_header"><h2>The dovecot service starts the POP3
server</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"
id="s1-email-types">13.2. Email Program
Classifications</h2></div></div></div><a
id="id619782" class="indexterm"></a><div
class="para">
+ In general, all email applications fall into at least one of three classifications.
Each classification plays a specific role in the process of moving and managing email
messages. While most users are only aware of the specific email program they use to
receive and send messages, each one is important for ensuring that email arrives at the
correct destination.
+ </div><div class="section"
id="s2-email-types-mta"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-types-mta">13.2.1. Mail Transport
Agent</h3></div></div></div><a id="id475465"
class="indexterm"></a><a id="id1304397"
class="indexterm"></a><a id="id1304412"
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">
+ While the delivery of messages between machines may seem rather straightforward, the
entire process of deciding if a particular MTA can or should accept a message for delivery
is quite complicated. In addition, due to problems from spam, use of a particular MTA is
usually restricted by the MTA's configuration or the access configuration for the
network on which the MTA resides.
+ </div><div class="para">
+ Many modern email client programs can act as an MTA when sending email. However, this
action should not be confused with the role of a true MTA. The sole reason email client
programs are capable of sending email like an MTA is because the host running the
application does not have its own MTA. This is particularly true for email client programs
on non-UNIX-based operating systems. However, these client programs only send outbound
messages to an MTA they are authorized to use and do not directly deliver the message to
the intended recipient's email server.
+ </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">Section 13.3, “Mail Transport
Agents”</a>.
+ </div></div><div class="section"
id="s2-email-types-mda"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-types-mda">13.2.2. Mail Delivery
Agent</h3></div></div></div><a id="id463635"
class="indexterm"></a><a id="id410656"
class="indexterm"></a><a id="id410671"
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">
+ Any program that actually handles a message for delivery to the point where it can be
read by an email client application can be considered an MDA. For this reason, some MTAs
(such as Sendmail and Postfix) can fill the role of an MDA when they append new email
messages to a local user's mail spool file. In general, MDAs do not transport messages
between systems nor do they provide a user interface; MDAs distribute and sort messages on
the local machine for an email client application to access.
+ </div></div><div class="section"
id="s2-email-types-mua"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-types-mua">13.2.3. Mail User
Agent</h3></div></div></div><a id="id573272"
class="indexterm"></a><a id="id573291"
class="indexterm"></a><a id="id571344"
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"
id="s1-email-mta">13.3. Mail Transport
Agents</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"
id="s2-email-mta-postfix">13.3.1. Postfix</h3></div></div></div><a
id="id604101" class="indexterm"></a><a
id="id620919" class="indexterm"></a><div
class="para">
+ Originally developed at IBM by security expert and programmer Wietse Venema, Postfix
is a Sendmail-compatible MTA that is designed to be secure, fast, and easy to configure.
+ </div><div class="para">
+ To improve security, Postfix uses a modular design, where small processes with
limited privileges are launched by a <em
class="firstterm">master</em> daemon. The smaller, less privileged
processes perform very specific tasks related to the various stages of mail delivery and
run in a change rooted environment to limit the effects of attacks.
+ </div><div class="para">
+ Configuring Postfix to accept network connections from hosts other than the local
computer takes only a few minor changes in its configuration file. Yet for those with more
complex needs, Postfix provides a variety of configuration options, as well as third party
add-ons that make it a very versatile and full-featured MTA.
+ </div><div class="para">
+ The configuration files for Postfix are human readable and support upward of 250
directives. Unlike Sendmail, no macro processing is required for changes to take effect
and the majority of the most commonly used options are described in the heavily commented
files.
+ </div><div class="section"
id="s3-email-mta-postfix-default"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-mta-postfix-default">13.3.1.1. The Default Postfix
Installation</h4></div></div></div><a id="id636683"
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> — Maps email
addresses to relay hosts.
+ </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">Section 13.3.1.2,
“Basic Postfix Configuration”</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"
id="s3-email-mta-postfix-conf">13.3.1.2. Basic Postfix
Configuration</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">
+ Edit the <code class="filename">/etc/postfix/main.cf</code>
file with a text editor, such as <code class="command">vi</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">
+ Uncomment the <code class="command">myorigin =
$mydomain</code> line.
+ </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">
+ Uncomment the <code class="command">mydestination = $myhostname,
localhost.$mydomain</code> line.
+ </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">
+ Uncomment the <code class="command">inet_interfaces =
all</code> line.
+ </div></li><li class="listitem"><div
class="para">
+ Comment the <code class="command">inet_interfaces =
localhost</code> line.
+ </div></li><li class="listitem"><div
class="para">
+ Restart the <code class="command">postfix</code> service.
+ </div></li></ul></div><div class="para">
+ Once these steps are complete, the host accepts outside emails for delivery.
+ </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"
id="using-postfix-with-ldap">13.3.1.3. Using Postfix with
LDAP</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"
id="aliases-example">13.3.1.3.1. The /etc/aliases lookup
example</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">
+ where <em
class="parameter"><code>ldap.example.com</code></em>,
<em class="parameter"><code>example</code></em>, and
<em class="parameter"><code>com</code></em> are
parameters that need to be replaced with specification of an existing available <code
class="systemitem">LDAP</code> server.
+ </div><div class="note"><div
class="admonition_header"><h2>The /etc/postfix/ldap-aliases.cf
file</h2></div><div class="admonition"><div
class="para">
+ The <code
class="filename">/etc/postfix/ldap-aliases.cf</code> file can specify
various parameters, including parameters that enable <code
class="systemitem">LDAP</code> <code
class="systemitem">SSL</code> and <code
class="systemitem">STARTTLS</code>. For more information, refer to the
<code class="command">ldap_table(5)</code> man page.
+ </div></div></div><div class="para">
+ For more information on <code class="systemitem">LDAP</code>,
refer to <a class="xref" href="#s1-OpenLDAP">Section 14.1,
“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"
id="s2-email-mta-sendmail">13.3.2. Sendmail</h3></div></div></div><a
id="id1012448" class="indexterm"></a><a
id="id1012463" 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"
id="s3-email-mta-sendmail-purpose">13.3.2.1. Purpose and
Limitations</h4></div></div></div><a id="id1292639"
class="indexterm"></a><a id="id1292654"
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">Section 13.6, “Additional
Resources”</a> for a list of Sendmail resources.
+ </div><div class="para">
+ This section reviews the files installed with Sendmail by default and reviews basic
configuration changes, including how to stop unwanted email (spam) and how to extend
Sendmail with the <em class="firstterm">Lightweight Directory Access
Protocol (LDAP)</em>.
+ </div></div><div class="section"
id="s3-email-mta-sendmail-default"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-mta-sendmail-default">13.3.2.2. The Default Sendmail
Installation</h4></div></div></div><a id="id1277531"
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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div><div class="para">
+ Before using Sendmail, the default MTA has to be switched from Postfix. For more
information how to switch the default MTA refer to <a class="xref"
href="#s1-email-mta">Section 13.3, “Mail Transport Agents”</a>.
+ </div><div class="para">
+ The Sendmail executable is <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">Section 13.3.2.3, “Common Sendmail
Configuration Changes”</a>.
+ </div><div class="para">
+ Various Sendmail configuration files are installed in the <code
class="filename">/etc/mail/</code> directory including:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">access</code> — Specifies which
systems can use Sendmail for outbound email.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">domaintable</code> — Specifies domain
name mapping.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">local-host-names</code> — Specifies
aliases for the host.
+ </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@other-example.com">bob@other-example.com</a></code>
+ , add the following line to the <code
class="filename">virtusertable</code> file:
+ </div><pre class="programlisting"><code
class="command">(a)example.com
bob(a)other-example.com</code></pre><div class="para">
+ To finalize the change, the <code
class="filename">virtusertable.db</code> file must be updated:
+ </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"
id="s3-email-mta-sendmail-changes">13.3.2.3. Common Sendmail Configuration
Changes</h4></div></div></div><a id="id948668"
class="indexterm"></a><a id="id481895"
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>Backup the sendmail.cf file before
changing its content</h2></div><div class="admonition"><div
class="para">
+ Before changing the <code class="filename">sendmail.cf</code>
file, it is a good idea to create a backup copy.
+ </div></div></div><div class="para">
+ To add the desired functionality to Sendmail, edit the <code
class="filename">/etc/mail/sendmail.mc</code> file as <code
class="systemitem">root</code>. Once you are finished, restart the
<code class="systemitem">sendmail</code> service and, if the
<span class="package">m4</span> package is installed, the <code
class="command">m4</code> macro processor will automatically generate a
new <code class="filename">sendmail.cf</code> configuration file:
+ </div><pre class="screen"><code
class="command">systemctl restart
sendmail.service</code></pre><div class="important"><div
class="admonition_header"><h2>Configuring Sendmail as a server for
other clients</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"
id="s3-email-sendmail-changes-masquerading">13.3.2.4. Masquerading</h4></div></div></div><a
id="id412654" class="indexterm"></a><a
id="id412669" 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(a)example.com</code> instead of <code
class="computeroutput">user(a)host.example.com</code>.
+ </div><div class="para">
+ To do this, add the following lines to <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"
id="s3-email-sendmail-stopping-spam">13.3.2.5. Stopping
Spam</h4></div></div></div><a id="id446663"
class="indexterm"></a><div class="para">
+ Email spam can be defined as unnecessary and unwanted email received by a user who
never requested the communication. It is a disruptive, costly, and widespread abuse of
Internet communication standards.
+ </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">Section 13.4.2.6, “Spam Filters”</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"
id="s3-email-mta-sendmail-ldap">13.3.2.6. Using Sendmail with
LDAP</h4></div></div></div><a id="id684560"
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>Advanced
configuration</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">Section 13.3.2.3, “Common Sendmail
Configuration Changes”</a> for instructions.
+ </div><div class="para">
+ For more information on <code class="systemitem">LDAP</code>,
refer to <a class="xref" href="#s1-OpenLDAP">Section 14.1,
“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"
id="s2-email-mta-fetchmail">13.3.3. Fetchmail</h3></div></div></div><a
id="id896048" class="indexterm"></a><a
id="id896062" 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>Installing the fetchmail
package</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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ Fetchmail is configured for each user through the use of a <code
class="filename">.fetchmailrc</code> file in the user's home
directory. If it does not already exist, create the <code
class="filename">.fetchmailrc</code> file in your home directory
+ </div><div class="para">
+ Using preferences in the <code
class="filename">.fetchmailrc</code> file, Fetchmail checks for email
on a remote server and downloads it. It then delivers it to port <code
class="constant">25</code> on the local machine, using the local MTA to
place the email in the correct user's spool file. If Procmail is available, it is
launched to filter the email and place it in a mailbox so that it can be read by an MUA.
+ </div><div class="section"
id="s3-email-mda-fetchmail-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-mda-fetchmail-configuration">13.3.3.1. Fetchmail Configuration
Options</h4></div></div></div><a id="id585173"
class="indexterm"></a><a id="id585187"
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">
+ A user's <code class="filename">.fetchmailrc</code> file
contains three classes of configuration options:
+ </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">
+ The following is a sample example of a <code
class="filename">.fetchmailrc</code> file:
+ </div><pre class="programlisting">set postmaster
"user1"
+set bouncemail
+
+poll
pop.domain.com proto pop3
+ user 'user1' there with password 'secret' is user1 here
+
+poll
mail.domain2.com
+ user 'user5' there with password 'secret2' is user1 here
+ user 'user7' there with password 'secret3' is user1
here</pre><div class="para">
+ In this example, the global options specify that the user is sent email as a last
resort (<code class="command">postmaster</code> option) and all
email errors are sent to the postmaster instead of the sender (<code
class="command">bouncemail</code> option). The <code
class="command">set</code> action tells Fetchmail that this line
contains a global option. Then, two email servers are specified, one set to check using
<code class="systemitem">POP3</code>, the other for trying various
protocols to find one that works. Two users are checked using the second server option,
but all email found for any user is sent to <code
class="command">user1</code>'s mail spool. This allows multiple
mailboxes to be checked on multiple servers, while appearing in a single MUA inbox. Each
user's specific information begins with the <code
class="command">user</code> action.
+ </div><div class="note"><div
class="admonition_header"><h2>Omitting the password from the
configuration</h2></div><div class="admonition"><div
class="para">
+ Users are not required to place their password in the <code
class="filename">.fetchmailrc</code> file. Omitting the <code
class="command">with password '<em
class="replaceable"><code>password</code></em>'</code>
section causes Fetchmail to ask for a password when it is launched.
+ </div></div></div><div class="para">
+ Fetchmail has numerous global, server, and local options. Many of these options are
rarely used or only apply to very specific situations. The <code
class="filename">fetchmail</code> man page explains each option in
detail, but the most common ones are listed in the following three sections.
+ </div></div><div class="section"
id="s3-email-mda-fetchmail-configuration-global"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-mda-fetchmail-configuration-global">13.3.3.2. Global
Options</h4></div></div></div><a id="id625674"
class="indexterm"></a><a id="id625693"
class="indexterm"></a><div class="para">
+ Each global option should be placed on a single line after a <code
class="command">set</code> action.
+ </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> — Specifies a local
user to send mail to in case of delivery problems.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">syslog</code> — Specifies the log file
for errors and status messages. By default, this is <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"
id="s3-email-mda-fetchmail-configuration-server">13.3.3.3. Server
Options</h4></div></div></div><a id="id639322"
class="indexterm"></a><a id="id639340"
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"
id="s3-email-fetchmail-configuration-user">13.3.3.4. User
Options</h4></div></div></div><a id="id676440"
class="indexterm"></a><a id="id676459"
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> — Activates SSL
encryption.
+ </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"
id="s3-email-mda-fetchmail-commands">13.3.3.5. Fetchmail Command
Options</h4></div></div></div><a id="id893224"
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"
id="s3-email-mda-fetchmail-commands-info">13.3.3.6. Informational or
Debugging Options</h4></div></div></div><a
id="id1456165" class="indexterm"></a><div
class="para">
+ Certain options used after the <code
class="command">fetchmail</code> command can supply important
information.
+ </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"
id="s3-email-mda-fetchmail-commands-special">13.3.3.7. Special
Options</h4></div></div></div><a id="id573533"
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> — Quits the Fetchmail
daemon process.
+ </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"
id="s2-email-switchmail">13.3.4. Mail Transport Agent (MTA)
Configuration</h3></div></div></div><a id="id908634"
class="indexterm"></a><a id="id908648"
class="indexterm"></a><a id="id908662"
class="indexterm"></a><a id="id697966"
class="indexterm"></a><a id="id697989"
class="indexterm"></a><a id="id1268792"
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="id694327"
class="indexterm"></a><a id="id694338"
class="indexterm"></a><div class="para">
+ Fedora 15 provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is
the default MTA.
+ </div></div></div><div class="section"
id="s1-email-mda"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-email-mda">13.4. Mail Delivery
Agents</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="id941638"
class="indexterm"></a><a id="id941653"
class="indexterm"></a><div class="para">
+ Procmail delivers and filters email as it is placed in the mail spool file of the
localhost. It is powerful, gentle on system resources, and widely used. Procmail can play
a critical role in delivering email to be read by email client applications.
+ </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"
id="s2-email-procmail-configuration">13.4.1. Procmail
Configuration</h3></div></div></div><a id="id1000944"
class="indexterm"></a><a id="id1000958"
class="indexterm"></a><div class="para">
+ The Procmail configuration file contains important environmental variables. These
variables specify things such as which messages to sort and what to do with the messages
that do not match any recipes.
+ </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">
+ In this example, <code class="command"><em
class="replaceable"><code>env-variable</code></em>
</code> is the name of the variable and <code class="command"><em
class="replaceable"><code>value</code></em> </code>
defines the variable.
+ </div><div class="para">
+ There are many environment variables not used by most Procmail users and many of the
more important environment variables are already defined by a default value. Most of the
time, the following variables are used:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">DEFAULT</code> — Sets the default
mailbox where messages that do not match any recipes are placed.
+ </div><div class="para">
+ The default <code class="command">DEFAULT</code> value is the
same as <code class="command">$ORGMAIL</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">INCLUDERC</code> — Specifies additional
<code class="filename">rc</code> files containing more recipes for
messages to be checked against. This breaks up the Procmail recipe lists into individual
files that fulfill different roles, such as blocking spam and managing email lists, that
can then be turned off or on by using comment characters in the user's <code
class="filename">~/.procmailrc</code> file.
+ </div><div class="para">
+ For example, lines in a user's <code
class="filename">.procmailrc</code> file may look like this:
+ </div><pre class="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> — Sets the current
working directory for Procmail. If set, all other Procmail paths are relative to this
directory.
+ </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">
+ By default, a value of <code
class="command">/var/spool/mail/$LOGNAME</code> is used.
+ </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"
id="s2-email-procmail-recipes">13.4.2. Procmail
Recipes</h3></div></div></div><a id="id442360"
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">Section 13.4.2.5, “Recipe
Examples”</a>.
+ </div><div class="para">
+ Procmail recipes take the following form:
+ </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">Section 13.4.2.4, “Special
Conditions and Actions”</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"
id="s2-email-procmail-recipes-delivering">13.4.2.1. Delivering vs.
Non-Delivering Recipes</h4></div></div></div><a
id="id481031" class="indexterm"></a><a
id="id481049" 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">
+ When messages match a delivering recipe, Procmail performs the specified action and
stops comparing the message against any other recipes. Messages that match non-delivering
recipes continue to be compared against other recipes.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-flags"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-procmail-recipes-flags">13.4.2.2. Flags</h4></div></div></div><a
id="id544474" class="indexterm"></a><div
class="para">
+ Flags are essential to determine how or if a recipe's conditions are compared to
a message. The following flags are commonly used:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">A</code> — Specifies that this recipe
is only used if the previous recipe without an <code
class="command">A</code> or <code
class="command">a</code> flag also matched this message.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">a</code> — Specifies that this recipe
is only used if the previous recipe with an <code
class="command">A</code> or <code
class="command">a</code> flag also matched this message <span
class="emphasis"><em>and</em></span> was successfully
completed.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">B</code> — Parses the body of the
message and looks for matching conditions.
+ </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> — Uses the pipe as a filter.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">H</code> — Parses the header of the
message and looks for matching conditions. This is the default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">h</code> — Uses the header in a
resulting action. This is the default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">w</code> — Tells Procmail to wait for
the specified filter or program to finish, and reports whether or not it was successful
before considering the message filtered.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">W</code> — Is identical to <code
class="command">w</code> except that "Program failure"
messages are suppressed.
+ </div></li></ul></div><div class="para">
+ For a detailed list of additional flags, refer to the <code
class="filename">procmailrc</code> man page.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-lockfile"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-procmail-recipes-lockfile">13.4.2.3. Specifying a Local
Lockfile</h4></div></div></div><a id="id697714"
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">
+ Alternatively, specify the name of the local lockfile to be used with this recipe
after the colon.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-special"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-procmail-recipes-special">13.4.2.4. Special Conditions and
Actions</h4></div></div></div><a id="id665382"
class="indexterm"></a><a id="id665400"
class="indexterm"></a><div class="para">
+ Special characters used before Procmail recipe conditions and actions change the way
they are interpreted.
+ </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> — In the condition line, this
character inverts the condition, causing a match to occur only if the condition does not
match the message.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command"><</code> — Checks if the
message is under a specified number of bytes.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">></code> — Checks if the
message is over a specified number of bytes.
+ </div></li></ul></div><div class="para">
+ The following characters are used to perform special actions:
+ </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> — Starts a specified program
to process the message.
+ </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">
+ If no special character is used at the beginning of the action line, Procmail
assumes that the action line is specifying the mailbox in which to write the message.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-procmail-recipes-examples">13.4.2.5. Recipe
Examples</h4></div></div></div><a id="id675836"
class="indexterm"></a><div class="para">
+ Procmail is an extremely flexible program, but as a result of this flexibility,
composing Procmail recipes from scratch can be difficult for new users.
+ </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">
+ The following simple examples demonstrate the basic structure of Procmail recipes
and can provide the foundation for more intricate constructions.
+ </div><div class="para">
+ A basic recipe may not even contain conditions, as is illustrated in the following
example:
+ </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">
+ The following example matched messages from a specific email address and throws them
away.
+ </div><pre class="programlisting">:0 * ^From:
spammer(a)domain.com /dev/null</pre><div class="para">
+ With this example, any messages sent by <code
class="computeroutput">spammer(a)domain.com</code> are sent to the
<code class="filename">/dev/null</code> device, deleting them.
+ </div><div class="warning"><div
class="admonition_header"><h2>Sending messages to
/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">
+ The following recipe grabs email sent from a particular mailing list and places it
in a specified folder.
+ </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(a)domain.com</code> mailing list are
placed in the <code class="filename">tuxlug</code> mailbox
automatically for the MUA. Note that the condition in this example matches the message if
it has the mailing list's email address on the <code
class="computeroutput">From</code>, <code
class="computeroutput">Cc</code>, or <code
class="computeroutput">To</code> lines.
+ </div><div class="para">
+ Consult the many Procmail online resources available in <a class="xref"
href="#s1-email-additional-resources">Section 13.6, “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"
id="s3-email-mda-spam">13.4.2.6. Spam
Filters</h4></div></div></div><a id="id1012775"
class="indexterm"></a><a id="id1012794"
class="indexterm"></a><a id="id849122"
class="indexterm"></a><div class="para">
+ Because it is called by Sendmail, Postfix, and Fetchmail upon receiving new emails,
Procmail can be used as a powerful tool for combating spam.
+ </div><div class="para">
+ This is particularly true when Procmail is used in conjunction with SpamAssassin.
When used together, these two applications can quickly identify spam emails, and sort or
destroy them.
+ </div><div class="para">
+ SpamAssassin uses header analysis, text analysis, blacklists, a spam-tracking
database, and self-learning Bayesian spam analysis to quickly and accurately identify and
tag spam.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the spamassassin
package</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>SpamAssassin</strong></span>,
first ensure the <span class="package">spamassassin</span> package
is installed on your system by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">yum install spamassassin</code></pre><div
class="para">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ The easiest way for a local user to use SpamAssassin is to place the following line
near the top of the <code class="filename">~/.procmailrc</code>
file:
+ </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">
+ The message body of the email is also prepended with a running tally of what
elements caused it to be diagnosed as spam.
+ </div><div class="para">
+ To file email tagged as spam, a rule similar to the following can be used:
+ </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">
+ To start the <code class="systemitem">spamd</code> daemon,
type the following command:
+ </div><pre class="screen"><code
class="command">systemctl start
spamassassin.service</code></pre><div class="para">
+ To start the SpamAssassin daemon when the system is booted, run:
+ </div><pre class="screen"><code
class="command">systemctl enable
spamassassin.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div><div class="para">
+ To configure Procmail to use the SpamAssassin client application instead of the Perl
script, place the following line near the top of the <code
class="filename">~/.procmailrc</code> file. For a system-wide
configuration, place it in <code
class="filename">/etc/procmailrc</code>:
+ </div><pre
class="programlisting">INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc</pre></div></div></div><div
class="section" id="s1-email-mua"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-email-mua">13.5. Mail User
Agents</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"
id="s2-email-security">13.5.1. Securing
Communication</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="id410108"
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"
id="s3-email-security-clients">13.5.1.1. Secure Email
Clients</h4></div></div></div><a id="id580756"
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"
id="s3-email-security-servers">13.5.1.2. Securing Email Client
Communications</h4></div></div></div><a id="id662750"
class="indexterm"></a><a id="id580434"
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>Avoid using self-signed
certificates</h2></div><div class="admonition"><div
class="para">
+ Self-signed certificates should be used for testing purposes only. Any server used
in a production environment should use an SSL certificate granted by a CA.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate for <code
class="systemitem">IMAP</code> or <code
class="systemitem">POP</code>, change to the <code
class="filename">/etc/pki/dovecot/</code> directory, edit the
certificate parameters in the <code
class="filename">/etc/pki/dovecot/dovecot-openssl.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">
+ Once finished, make sure you have the following configurations in your <code
class="filename">/etc/dovecot/conf.d/10-ssl.conf</code> file:
+ </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>Installing the stunnel
package</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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate, change to the <code
class="filename">/etc/pki/tls/certs/</code> directory, and type the
following command:
+ </div><pre class="screen">certs]# <code
class="command">make stunnel.pem</code></pre><div
class="para">
+ Answer all of the questions to complete the process.
+ </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"
id="s1-email-additional-resources">13.6. Additional
Resources</h2></div></div></div><a id="id464138"
class="indexterm"></a><a id="id669128"
class="indexterm"></a><a id="id669143"
class="indexterm"></a><a id="id669157"
class="indexterm"></a><div class="para">
+ The following is a list of additional documentation about email applications.
+ </div><div class="section"
id="s2-email-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-installed-docs">13.6.1. Installed
Documentation</h3></div></div></div><a id="id549272"
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">
+ When learning how Procmail works and creating new recipes, the following Procmail
man pages are invaluable:
+ </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> — Explains the
<code class="filename">rc</code> file format used to construct
recipes.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailex</code> — Gives a number
of useful, real-world examples of Procmail recipes.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailsc</code> — Explains the
weighted scoring technique used by Procmail to match a particular recipe to a message.
+ </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"
id="s2-email-useful-websites">13.6.2. Useful
Websites</h3></div></div></div><a id="id1279312"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.sendmail.org/">http://www.sendmail.org/<... — Offers a
thorough technical breakdown of Sendmail features, documentation and configuration
examples.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.sendmail.com/">http://www.sendmail.com/<... — Contains
news, interviews and articles concerning Sendmail, including an expanded view of the many
options available.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.postfix.org/">http://www.postfix.org/</a...
— The Postfix project home page contains a wealth of information about Postfix. The
mailing list is a particularly good place to look for information.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://fetchmail.berlios.de/">http://fetchmail.berlios.de/</a> —
The home page for Fetchmail, featuring an online manual, and a thorough FAQ.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.procmail.org/">http://www.procmail.org/<... — The home
page for Procmail with links to assorted mailing lists dedicated to Procmail as well as
various FAQ documents.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://partmaps.org/era/procmail/mini-faq.html">http:/...
— 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.... —
The official site of the SpamAssassin project.
+ </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"
id="s2-email-related-books">13.6.3. Related
Books</h3></div></div></div><a id="id423374"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <em class="citetitle">Sendmail Milters: A Guide for Fighting
Spam</em> by Bryan Costales and Marcia Flynt; Addison-Wesley — A good Sendmail guide
that can help you customize your mail filters.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Sendmail</em> by Bryan Costales with
Eric Allman et al.; O'Reilly & Associates — A good Sendmail reference written
with the assistance of the original creator of Delivermail and Sendmail.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Removing the Spam: Email Processing and
Filtering</em> by Geoff Mulligan; Addison-Wesley Publishing Company — A volume that
looks at various methods used by email administrators using established tools, such as
Sendmail and Procmail, to manage spam problems.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Internet Email Protocols: A Developer's
Guide</em> by Kevin Johnson; Addison-Wesley Publishing Company — Provides a very
thorough review of major email protocols and the security they provide.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Managing IMAP</em> by Dianna Mullet and
Kevin Mullet; O'Reilly & Associates — Details the steps required to configure
an IMAP server.
+ </div></li></ul></div></div></div></div><div
xml:lang="en-US" class="chapter" id="ch-Directory_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 14. Directory
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-OpenLDAP">14.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ldap-introduction">14.1.1.
Introduction to LDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-installation">14.1.2.
Installing the OpenLDAP Suite</a></span></dt><dt><span
class="section"><a href="#s2-ldap-configuration">14.1.3.
Configuring an OpenLDAP Server</a></span></dt><dt><span
class="section"><a href="#s2-ldap-running">14.1.4. Running an
OpenLDAP Server</a></span></dt><dt><span
class="section"><a href="#s2-ldap-pam">14.1.5. Configuring a
System to Authenticate Using OpenLDAP</a></span></dt><dt><span
class="section"><a href="#s2-ldap-resources">14.1.6.
Additional Resources</a></span></dt></
dl></dd></dl></div><div xml:lang="en-US"
class="section" id="s1-OpenLDAP" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-OpenLDAP">14.1. OpenLDAP</h2></div></div></div><a
id="id838047" class="indexterm"></a><a
id="id838011" class="indexterm"></a><a
id="id838015" class="indexterm"></a><a
id="id838003" 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"
id="s2-ldap-introduction">14.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>Using Mozilla
NSS</h2></div><div class="admonition"><div
class="para">
+ The OpenLDAP suite in Fedora 15 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"
id="s3-ldap-terminology">14.1.1.1. LDAP
Terminology</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><dt
class="varlistentry"><span class="term"> <a
id="id641149" class="indexterm"></a>
+ entry </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="id641106"
class="indexterm"></a>
+ attribute </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="id633006"
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"
id="s3-ldap-features">14.1.1.2. OpenLDAP
Features</h4></div></div></div><a id="id829378"
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"
id="s3-ldap-setup">14.1.1.3. OpenLDAP Server
Setup</h4></div></div></div><a id="id970593"
class="indexterm"></a><div class="para">
+ The typical steps to set up an LDAP server on Fedora are as follows:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Install the OpenLDAP suite. Refer to <a class="xref"
href="#s2-ldap-installation">Section 14.1.2, “Installing the OpenLDAP
Suite”</a> for more information on required packages.
+ </div></li><li class="step"><div
class="para">
+ Customize the configuration as described in <a class="xref"
href="#s2-ldap-configuration">Section 14.1.3, “Configuring an OpenLDAP
Server”</a>.
+ </div></li><li class="step"><div
class="para">
+ Start the <code class="systemitem">slapd</code> service as
described in <a class="xref"
href="#s2-ldap-running">Section 14.1.4, “Running an OpenLDAP
Server”</a>.
+ </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"
id="s2-ldap-installation">14.1.2. Installing the OpenLDAP
Suite</h3></div></div></div><a id="id508728"
class="indexterm"></a><a id="id508695"
class="indexterm"></a><div class="para">
+ The suite of OpenLDAP libraries and tools is provided by the following packages:
+ </div><div class="table"
id="table-ldap-packages-openldap"><h6>Table 14.1. List of OpenLDAP
packages</h6><div class="table-contents"><table
summary="List of OpenLDAP packages"
border="1"><colgroup><col width="33%"
class="package" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Package
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="package">openldap</span>
+ </td><td>
+ A package containing the libraries necessary to run the OpenLDAP server and client
applications.
+ </td></tr><tr><td>
+ <span class="package">openldap-clients</span>
+ </td><td>
+ A package containing the command line utilities for viewing and modifying
directories on an LDAP server.
+ </td></tr><tr><td>
+ <span class="package">openldap-servers</span>
+ </td><td>
+ A package containing both the services and utilities to configure and run an LDAP
server. This includes the <em class="firstterm">Standalone LDAP
Daemon</em>, <code class="systemitem">slapd</code>.
+ </td></tr><tr><td>
+ <span class="package">openldap-servers-sql</span>
+ </td><td>
+ A package containing the SQL support module.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Additionally, the following packages are commonly used along with the LDAP server:
+ </div><div class="table"
id="table-ldap-packages-additional"><h6>Table 14.2. List of commonly
installed additional LDAP packages</h6><div
class="table-contents"><table summary="List of commonly installed
additional LDAP packages" border="1"><colgroup><col
width="33%" class="package" /><col width="67%"
class="description" /></colgroup><thead><tr><th>
+ Package
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="package">nss-pam-ldapd</span>
+ </td><td>
+ 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>
+ <span class="package">mod_authz_ldap</span>
+ </td><td>
+ <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">
+ To install these packages, use the <code
class="command">yum</code> command in the following form:
+ </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">
+ For example, to perform the basic LDAP server installation, 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
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">Section 4.2.4, “Installing
Packages”</a>.
+ </div><div class="section"
id="s3-ldap-packages-openldap-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-packages-openldap-servers">14.1.2.1. Overview of OpenLDAP Server
Utilities</h4></div></div></div><a id="id447868"
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>Table 14.3. List of
OpenLDAP server utilities</h6><div class="table-contents"><table
summary="List of OpenLDAP server utilities"
border="1"><colgroup><col width="33%"
class="command" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">slapacl</code>
+ </td><td>
+ Allows you to check the access to a list of attributes.
+ </td></tr><tr><td>
+ <code class="command">slapadd</code>
+ </td><td>
+ Allows you to add entries from an LDIF file to an LDAP directory.
+ </td></tr><tr><td>
+ <code class="command">slapauth</code>
+ </td><td>
+ Allows you to check a list of IDs for authentication and authorization
permissions.
+ </td></tr><tr><td>
+ <code class="command">slapcat</code>
+ </td><td>
+ Allows you to pull entries from an LDAP directory in the default format and save
them in an LDIF file.
+ </td></tr><tr><td>
+ <code class="command">slapdn</code>
+ </td><td>
+ Allows you to check a list of Distinguished Names (DNs) based on available schema
syntax.
+ </td></tr><tr><td>
+ <code class="command">slapindex</code>
+ </td><td>
+ 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>
+ <code class="command">slappasswd</code>
+ </td><td>
+ 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>
+ <code class="command">slapschema</code>
+ </td><td>
+ Allows you to check the compliance of a database with the corresponding schema.
+ </td></tr><tr><td>
+ <code class="command">slaptest</code>
+ </td><td>
+ Allows you to check the LDAP server configuration.
+ </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">Section 14.1.6.1, “Installed
Documentation”</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">slapd</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>Stop
slapd before using these utilities</h2></div><div
class="admonition"><div class="para">
+ To preserve the data integrity, stop the <code
class="systemitem">slapd</code> service before using <code
class="command">slapadd</code>, <code
class="command">slapcat</code>, or <code
class="command">slapindex</code>. You can do so by typing 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">
+ For more information on how to start, stop, restart, and check the current status of
the <code class="systemitem">slapd</code> service, refer to <a
class="xref" href="#s2-ldap-running">Section 14.1.4, “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"
id="s3-ldap-packages-openldap-clients">14.1.2.2. Overview of OpenLDAP Client
Utilities</h4></div></div></div><a id="id531723"
class="indexterm"></a><div class="para">
+ The <span class="package">openldap-clients</span> package
installs the following utilities which can be used to add, modify, and delete entries in
an LDAP directory:
+ </div><div class="table"
id="table-ldap-packages-openldap-clients"><h6>Table 14.4. List of
OpenLDAP client utilities</h6><div class="table-contents"><table
summary="List of OpenLDAP client utilities"
border="1"><colgroup><col width="33%"
class="command" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">ldapadd</code>
+ </td><td>
+ Allows you to add entries to an LDAP directory, either from a file, or from
standard input. It is a symbolic link to <code class="command">ldapmodify
-a</code>.
+ </td></tr><tr><td>
+ <code class="command">ldapcompare</code>
+ </td><td>
+ Allows you to compare given attribute with an LDAP directory entry.
+ </td></tr><tr><td>
+ <code class="command">ldapdelete</code>
+ </td><td>
+ Allows you to delete entries from an LDAP directory.
+ </td></tr><tr><td>
+ <code class="command">ldapexop</code>
+ </td><td>
+ Allows you to perform extended LDAP operations.
+ </td></tr><tr><td>
+ <code class="command">ldapmodify</code>
+ </td><td>
+ Allows you to modify entries in an LDAP directory, either from a file, or from
standard input.
+ </td></tr><tr><td>
+ <code class="command">ldapmodrdn</code>
+ </td><td>
+ Allows you to modify the RDN value of an LDAP directory entry.
+ </td></tr><tr><td>
+ <code class="command">ldappasswd</code>
+ </td><td>
+ Allows you to set or change the password for an LDAP user.
+ </td></tr><tr><td>
+ <code class="command">ldapsearch</code>
+ </td><td>
+ Allows you to search LDAP directory entries.
+ </td></tr><tr><td>
+ <code class="command">ldapurl</code>
+ </td><td>
+ Allows you to compose or decompose LDAP URLs.
+ </td></tr><tr><td>
+ <code class="command">ldapwhoami</code>
+ </td><td>
+ Allows you to perform a <code class="option">whoami</code>
operation on an LDAP server.
+ </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"
id="s3-ldap-packages-applications">14.1.2.3. Overview of Common LDAP Client
Applications</h4></div></div></div><a id="id815172"
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"
id="s2-ldap-configuration">14.1.3. Configuring an OpenLDAP
Server</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>Table 14.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>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id556625" class="indexterm"></a>
+ <code class="filename">/etc/openldap/ldap.conf</code>
+ </td><td>
+ 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>
+ <a id="id556565" class="indexterm"></a>
+ <code class="filename">/etc/openldap/slapd.d/</code>
+ </td><td>
+ 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">Section 14.1.2.1, “Overview of
OpenLDAP Server Utilities”</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"
id="s3-ldap-configuration-global">14.1.3.1. Changing the Global
Configuration</h4></div></div></div><a id="id888800"
class="indexterm"></a><a id="id888785"
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><dt
class="varlistentry"><span class="term"> <a
id="id640297" 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">Table 14.6,
“Available olcAllows options”</a>. The default option is <code
class="option">bind_v2</code>.
+ </div><div class="table"
id="table-ldap-configuration-olcallows"><h6>Table 14.6. Available
olcAllows options</h6><div class="table-contents"><table
summary="Available olcAllows options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">bind_v2</code>
+ </td><td>
+ Enables the acceptance of LDAP version 2 bind requests.
+ </td></tr><tr><td>
+ <code class="option">bind_anon_cred</code>
+ </td><td>
+ Enables an anonymous bind when the Distinguished Name (DN) is empty.
+ </td></tr><tr><td>
+ <code class="option">bind_anon_dn</code>
+ </td><td>
+ Enables an anonymous bind when the Distinguished Name (DN) is <span
class="emphasis"><em>not</em></span> empty.
+ </td></tr><tr><td>
+ <code class="option">update_anon</code>
+ </td><td>
+ Enables processing of anonymous update operations.
+ </td></tr><tr><td>
+ <code class="option">proxy_authz_anon</code>
+ </td><td>
+ 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>Example 14.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="id724617"
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">
+ The default option is <code class="option">100</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcconnmaxpending"><h6>Example 14.2. Using
the olcConnMaxPending directive</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="id547877"
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">
+ The default option is <code class="option">1000</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcconnmaxpendingauth"><h6>Example 14.3. Using
the olcConnMaxPendingAuth directive</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="id547810"
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">Table 14.7, “Available
olcDisallows options”</a>. No features are disabled by default.
+ </div><div class="table"
id="table-ldap-configuration-olcdisallows"><h6>Table 14.7. Available
olcDisallows options</h6><div class="table-contents"><table
summary="Available olcDisallows options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">bind_anon</code>
+ </td><td>
+ Disables the acceptance of anonymous bind requests.
+ </td></tr><tr><td>
+ <code class="option">bind_simple</code>
+ </td><td>
+ Disables the simple bind authentication mechanism.
+ </td></tr><tr><td>
+ <code class="option">tls_2_anon</code>
+ </td><td>
+ Disables the enforcing of an anonymous session when the STARTTLS command is
received.
+ </td></tr><tr><td>
+ <code class="option">tls_authc</code>
+ </td><td>
+ 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>Example 14.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="id629110"
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">
+ This option is disabled by default (that is, set to <code
class="option">0</code>).
+ </div><div class="example"
id="example-ldap-configuration-olcidletimeout"><h6>Example 14.5. Using
the olcIdleTimeout directive</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="id809203"
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>Example 14.6. Using the
olcLogFile directive</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="id829138" 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">
+ This option is disabled by default.
+ </div><div class="example"
id="example-ldap-configuration-olcreferral"><h6>Example 14.7. Using the
olcReferral directive</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="id463549" 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">
+ This option is disabled by default (that is, set to <code
class="option">0</code>).
+ </div><div class="example"
id="example-ldap-configuration-olcwritetimeout"><h6>Example 14.8. Using
the olcWriteTimeout directive</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"
id="s3-ldap-configuration-database">14.1.3.2. Changing the Database-Specific
Configuration</h4></div></div></div><a id="id463463"
class="indexterm"></a><a id="id480213"
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><dt
class="varlistentry"><span class="term"> <a
id="id480178" 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>Example 14.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="id1282339"
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>Example 14.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="id1282253" 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>Example 14.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="id1055040" 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>Example 14.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"
id="s3-ldap-configuration-schema">14.1.3.3. Extending
Schema</h4></div></div></div><a id="id747290"
class="indexterm"></a><a id="id747278"
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://...;.
+ </div></div></div><div class="section"
id="s2-ldap-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ldap-running">14.1.4. Running an OpenLDAP
Server</h3></div></div></div><a id="id605935"
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">Chapter 7, <em>Services and
Daemons</em></a>.
+ </div><div class="section"
id="s3-ldap-running-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-running-starting">14.1.4.1. Starting the
Service</h4></div></div></div><a id="id605901"
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">
+ If you want the service to start automatically at the boot time, use the following
command:
+ </div><pre class="screen"><code
class="command">systemctl enable
slapd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-ldap-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-running-stopping">14.1.4.2. Stopping the
Service</h4></div></div></div><a id="id877493"
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">
+ To prevent the service from starting automatically at the boot time, type:
+ </div><pre class="screen"><code
class="command">systemctl disable
slapd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-ldap-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-running-restarting">14.1.4.3. Restarting the
Service</h4></div></div></div><a id="id546796"
class="indexterm"></a><div class="para">
+ To restart 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 restart
slapd.service</code></pre><div class="para">
+ This stops the service, and then starts it again. Use this command to reload the
configuration.
+ </div></div><div class="section"
id="s3-ldap-running-status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-running-status">14.1.4.4. Checking the Service
Status</h4></div></div></div><a id="id546736"
class="indexterm"></a><div class="para">
+ To check whether the service is running, type the following at a shell prompt:
+ </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"
id="s2-ldap-pam">14.1.5. Configuring a System to Authenticate Using
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">Section 14.1.2,
“Installing the OpenLDAP Suite”</a> and <a class="xref"
href="#s2-ldap-configuration">Section 14.1.3, “Configuring an OpenLDAP
Server”</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">Chapter 8, <em>Configuring
Authentication</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"
id="s3-ldap-migrationtools">14.1.5.1. Migrating Old Authentication
Information to LDAP Format</h4></div></div></div><a
id="id527470" 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">Table 14.8,
“Commonly used LDAP migration scripts”</a>.
+ </div><div class="table"
id="table-ldap-migrationtools"><h6>Table 14.8. Commonly used LDAP
migration scripts</h6><div class="table-contents"><table
summary="Commonly used LDAP migration scripts"
border="1"><colgroup><col width="30%"
class="existing" /><col width="20%" class="running"
/><col width="50%" class="use"
/></colgroup><thead><tr><th>
+ Existing Name Service
+ </th><th>
+ Is LDAP Running?
+ </th><th>
+ Script to Use
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc</code> flat files
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_online.sh</code>
+ </td></tr><tr><td>
+ <code class="filename">/etc</code> flat files
+ </td><td>
+ no
+ </td><td>
+ <code class="filename">migrate_all_offline.sh</code>
+ </td></tr><tr><td>
+ NetInfo
+ </td><td>
+ yes
+ </td><td>
+ <code
class="filename">migrate_all_netinfo_online.sh</code>
+ </td></tr><tr><td>
+ NetInfo
+ </td><td>
+ no
+ </td><td>
+ <code
class="filename">migrate_all_netinfo_offline.sh</code>
+ </td></tr><tr><td>
+ NIS (YP)
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_nis_online.sh</code>
+ </td></tr><tr><td>
+ NIS (YP)
+ </td><td>
+ no
+ </td><td>
+ <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"
id="s2-ldap-resources">14.1.6. Additional
Resources</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"
id="s3-ldap-installed-docs">14.1.6.1. Installed
Documentation</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><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><dt
class="varlistentry"><span class="term">Client
Applications</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">Server
Applications</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">Administrative
Applications</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">Configuration
Files</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"
id="s3-ldap-additional-resources-web">14.1.6.2. Useful
Websites</h4></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://www.openldap.org/doc/admin24/">http://www.openl...
class="para">
+ The current version of the <em class="citetitle">OpenLDAP Software
Administrator's Guide</em>.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.kingsmountain.com/ldapRoadmap.shtml">http:/...
class="para">
+ Jeff Hodges' <em class="citetitle">LDAP Roadmap &
FAQ</em> containing links to several useful resources and emerging news concerning
the LDAP protocol.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.ldapman.org/articles/">http://www.ldapman.o...
class="para">
+ A collection of articles that offer a good introduction to LDAP, including methods
to design a directory tree and customizing directory structures.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.padl.com/">http://www.padl.com/</a>&l...
class="para">
+ A website of developers of several useful LDAP tools.
+ </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"
id="s3-ldap-related-books">14.1.6.3. Related
Books</h4></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><em
class="citetitle">OpenLDAP by Example</em> by John Terpstra and
Benjamin Coles; Prentice Hall.</span></dt><dd><div
class="para">
+ A collection of practical exercises in the OpenLDAP deployment.
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">Implementing
LDAP</em> by Mark Wilcox; Wrox Press, Inc.</span></dt><dd><div
class="para">
+ A book covering LDAP from both the system administrator's and software
developer's perspective.
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">Understanding and
Deploying LDAP Directory Services</em> by Tim Howes et al.; Macmillan Technical
Publishing.</span></dt><dd><div class="para">
+ A book covering LDAP design principles, as well as its deployment in a production
environment.
+ </div></dd></dl></div></div></div></div></div><div
xml:lang="en-US" class="chapter"
id="ch-File_and_Print_Servers" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 15. File
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-Samba">15.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a href="#samba-rgs-overview">15.1.1.
Introduction to Samba</a></span></dt><dt><span
class="section"><a href="#s2-samba-daemons">15.1.2. Samba
Daemons and Related Services</a></span></dt><dt><span
class="section"><a href="#s2-samba-connect-share">15.1.3.
Connecting to a Samba Share</a></span></dt><dt><span
class="section"><a href="#s2-samba-configuring">15.1.4.
Configuring a Samba Server</a></span></dt><dt><span
class="section"><a href="#s2-samba-startstop">15.1.5.
Starting and Stopping Samba</a></span></dt><dt><span
class="section"><a href="#s2-samba-servers">15.1.6. Samba
Server Types and the <code class="filename">sm
b.conf</code> File</a></span></dt><dt><span
class="section"><a href="#s2-samba-security-modes">15.1.7.
Samba Security Modes</a></span></dt><dt><span
class="section"><a href="#s2-samba-account-info-dbs">15.1.8.
Samba Account Information Databases</a></span></dt><dt><span
class="section"><a href="#s2-samba-network-browsing">15.1.9.
Samba Network Browsing</a></span></dt><dt><span
class="section"><a href="#s2-samba-cups">15.1.10. Samba with
CUPS Printing Support</a></span></dt><dt><span
class="section"><a href="#s2-samba-programs">15.1.11. Samba
Distribution Programs</a></span></dt><dt><span
class="section"><a href="#s2-samba-resources">15.1.12.
Additional
Resources</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-FTP">15.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-ftp-protocol">15.2.1. The File
Transfer Protocol</a></span></dt><dt><span
class="section"><a href="#s2-ftp-servers">15.2.2. FTP
Servers</a></span></dt><dt><span class="section">
<a href="#s3-ftp-vsftpd-conf">15.2.3. Files Installed with <code
class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-start">15.2.4. Starting and Stopping <code
class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="#s2-ftp-vsftpd-conf">15.2.5. <code
class="command">vsftpd</code> Configuration
Options</a></span></dt><dt><span
class="section"><a href="#s2-ftp-resources">15.2.6.
Additional
Resources</a></span></dt></dl></dd></dl></div><div
xml:lang="en-US" class="section" id="s1-Samba"
lang="en-US"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-Samba">15.1. Samba</h2></div></div></div><a
id="id433298" class="indexterm"></a><a
id="id433279" 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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="section"
id="samba-rgs-overview"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="samba-rgs-overview">15.1.1. Introduction to
Samba</h3></div></div></div><a id="id1059775"
class="indexterm"></a><div class="para">
+ The third major release of Samba, version 3.0.0, introduced numerous improvements from
prior versions, including:
+ </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">
+ Built in Unicode support for internationalization
+ </div></li><li class="listitem"><div
class="para">
+ Support for all recent Microsoft Windows server and client versions to connect to
Samba servers without needing local registry hacking
+ </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">Section 15.1.12.2, “Related
Books”</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"
id="s3-samba-abilities">15.1.1.1. Samba
Features</h4></div></div></div><a id="id476800"
class="indexterm"></a><div class="para">
+ Samba is a powerful and versatile server application. Even seasoned system
administrators must know its abilities and limitations before attempting installation and
configuration.
+ </div><div class="para">
+ What Samba can do:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Serve directory trees and printers to Linux, UNIX, and Windows clients
+ </div></li><li class="listitem"><div
class="para">
+ Assist in network browsing (with or without NetBIOS)
+ </div></li><li class="listitem"><div
class="para">
+ Authenticate Windows domain logins
+ </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">
+ Act as an Active Directory domain member server
+ </div></li><li class="listitem"><div
class="para">
+ Join a Windows NT/2000/2003/2008 PDC
+ </div></li></ul></div><div class="para">
+ What Samba cannot do:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Act as a BDC for a Windows PDC (and vice versa)
+ </div></li><li class="listitem"><div
class="para">
+ Act as an Active Directory domain controller
+ </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"
id="s2-samba-daemons">15.1.2. Samba Daemons and Related
Services</h3></div></div></div><a id="id911155"
class="indexterm"></a><div class="para">
+ The following is a brief introduction to the individual Samba daemons and services.
+ </div><div class="section"
id="s3-samba-services"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-services">15.1.2.1. Samba
Daemons</h4></div></div></div><a id="id503921"
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> <code class="command">smbd</code>
</h5><a id="id503863" 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">
+ The <code class="command">smbd</code> daemon is controlled by
the <code class="command">smb</code> service.
+ </div><h5> <code class="command">nmbd</code>
</h5><a id="id463197" 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">
+ The <code class="command">nmbd</code> daemon is controlled by
the <code class="command">nmb</code> service.
+ </div><h5> <code class="command">winbindd</code>
</h5><a id="id616343" 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">Section 15.1.11, “Samba Distribution
Programs”</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"
id="s2-samba-connect-share">15.1.3. Connecting to a Samba
Share</h3></div></div></div><a id="id647457"
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>Figure 15.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"
id="s3-samba-connect-share-cmdline">15.1.3.1. Command
Line</h4></div></div></div><a id="id733265"
class="indexterm"></a><a id="id733250"
class="indexterm"></a><a id="id733230"
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="id611895"
class="indexterm"></a><a id="id611875"
class="indexterm"></a><div class="para">
+ To connect to a Samba share from a shell prompt, type the following command:
+ </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"
id="s2-samba-mounting">15.1.3.2. Mounting the
Share</h4></div></div></div><a id="id1284142"
class="indexterm"></a><div class="para">
+ Sometimes it is useful to mount a Samba share to a directory so that the files in the
directory can be treated as if they are part of the local file system.
+ </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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div><div class="para">
+ Note that the <span class="package">cifs-utils</span> package
also contains the <span
class="application"><strong>cifs.upcall</strong></span>
binary called by the kernel in order to perform kerberized CIFS mounts. For more
information on <span
class="application"><strong>cifs.upcall</strong></span>,
refer to <code class="command">man cifs.upcall</code>.
+ </div></div></div><div class="para">
+ For more information about mounting a samba share, refer to <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"
id="s2-samba-configuring">15.1.4. Configuring a Samba
Server</h3></div></div></div><a id="id1455140"
class="indexterm"></a><a id="id1455126"
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"
id="s3-samba-configuring-gui">15.1.4.1. Graphical
Configuration</h4></div></div></div><a id="id1455090"
class="indexterm"></a><div class="para">
+ To configure Samba using a graphical interface, use one of the available Samba
graphical user interfaces. A list of available GUIs can be found at <a
href="http://www.samba.org/samba/GUI/">http://www.samba.org/...;.
+ </div></div><div class="section"
id="s3-samba-configuring-cmdline"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-configuring-cmdline">15.1.4.2. Command Line
Configuration</h4></div></div></div><a id="id804740"
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">
+ Replace <em
class="replaceable"><code>WORKGROUPNAME</code></em> with
the name of the Windows workgroup to which this machine should belong. The <em
class="replaceable"><code>BRIEF COMMENT ABOUT
SERVER</code></em> is optional and is used as the Windows comment about the
Samba system.
+ </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"
id="s3-samba-encrypted-passwords">15.1.4.3. Encrypted
Passwords</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="id438184"
class="indexterm"></a><a id="id531806"
class="indexterm"></a><a id="id469714"
class="indexterm"></a><a id="id611912"
class="indexterm"></a><a id="id410367"
class="indexterm"></a><a id="id822970"
class="indexterm"></a><a id="id623352"
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"
id="s2-samba-startstop">15.1.5. Starting and Stopping
Samba</h3></div></div></div><a id="id1247565"
class="indexterm"></a><a id="id475534"
class="indexterm"></a><a id="id1284116"
class="indexterm"></a><a id="id1293685"
class="indexterm"></a><a id="id786905"
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>Setting up a domain member
server</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">
+ To stop the server, type the following command in a shell prompt, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl stop smb.service</code></pre><div
class="para">
+ The <code class="option">restart</code> option is a quick way of
stopping and then starting Samba. This is the most reliable way to make configuration
changes take effect after editing the configuration file for Samba. Note that the restart
option starts the daemon even if it was not running originally.
+ </div><div class="para">
+ To restart the server, type the following command in a shell prompt, as <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">Chapter 7,
<em>Services and Daemons</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"
id="s2-samba-servers">15.1.6. Samba Server Types and the <code
class="filename">smb.conf</code>
File</h3></div></div></div><a id="id427710"
class="indexterm"></a><a id="id725913"
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"
id="s3-samba-standalone">15.1.6.1. Stand-alone
Server</h4></div></div></div><a id="id822873"
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">Section 15.1.7, “Samba Security
Modes”</a>.
+ </div><div class="section"
id="s4-samba-standalone-anonreadonly"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s4-samba-standalone-anonreadonly">15.1.6.1.1. Anonymous
Read-Only</h5></div></div></div><a id="id471724"
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"
id="s4-samba-standalone-anonreadwrite">15.1.6.1.2. Anonymous
Read/Write</h5></div></div></div><a id="id822974"
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"
id="s4-samba-standalone-anonprint">15.1.6.1.3. Anonymous Print
Server</h5></div></div></div><a id="id1003971"
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"
id="s4-samba-standalone-readwriteall">15.1.6.1.4. Secure Read/Write File and
Print Server</h5></div></div></div><a id="id623357"
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"
id="s3-samba-domain-member">15.1.6.2. Domain Member
Server</h4></div></div></div><a id="id409829"
class="indexterm"></a><div class="para">
+ A domain member, while similar to a stand-alone server, is logged into a domain
controller (either Windows or Samba) and is subject to the domain's security rules. An
example of a domain member server would be a departmental server running Samba that has a
machine account on the Primary Domain Controller (PDC). All of the department's
clients still authenticate with the PDC, and desktop profiles and all network policy files
are included. The difference is that the departmental server has the ability to control
printer and network shares.
+ </div><div class="section"
id="s4-samba-domain-member-ads"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s4-samba-domain-member-ads">15.1.6.2.1. Active Directory Domain Member
Server</h5></div></div></div><a id="id915459"
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">
+ In order to join a member server to an Active Directory domain, the following steps
must be completed:
+ </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">
+ Creation of the machine account on the Active Directory domain server
+ </div></li><li class="listitem"><div
class="para">
+ Association of the member server to the Active Directory domain
+ </div></li></ul></div><div class="para">
+ To create the machine account and join the Windows 2000/2003/2008 Active Directory,
Kerberos must first be initialized for the member server wishing to join the Active
Directory domain. To create an administrative Kerberos ticket, type the following command
as <code class="systemitem">root</code> on the member server:
+ </div><pre class="screen"><code
class="command">kinit
administrator(a)EXAMPLE.COM</code></pre><div class="para">
+ The <code class="command">kinit</code> command is a Kerberos
initialization script that references the Active Directory administrator account and
Kerberos realm. Since Active Directory requires Kerberos tickets, <code
class="command">kinit</code> obtains and caches a Kerberos
ticket-granting ticket for client/server authentication. 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"
id="s4-samba-domain-member-nt4">15.1.6.2.2. Windows NT4-based Domain Member
Server</h5></div></div></div><a id="id600839"
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"
id="s3-samba-domain-controller">15.1.6.3. Domain
Controller</h4></div></div></div><a id="id552097"
class="indexterm"></a><div class="para">
+ A domain controller in Windows NT is functionally similar to a Network Information
Service (NIS) server in a Linux environment. Domain controllers and NIS servers both host
user/group information databases as well as related services. Domain controllers are
mainly used for security, including the authentication of users accessing domain
resources. The service that maintains the user/group database integrity is called the
<em class="firstterm">Security Account Manager</em> (SAM). The SAM
database is stored differently between Windows and Linux Samba-based systems, therefore
SAM replication cannot be achieved and platforms cannot be mixed in a PDC/BDC
environment.
+ </div><div class="para">
+ In a Samba environment, there can be only one PDC and zero or more BDCs.
+ </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 cannot exist in a mixed Samba/Windows domain controller environment (Samba
cannot be a BDC of a Windows PDC or vice versa). Alternatively, Samba PDCs and BDCs
<span class="emphasis"><em>can</em></span> coexist.
+ </div></div></div><div class="section"
id="s4-samba-pdc-tdbsam"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s4-samba-pdc-tdbsam">15.1.6.3.1. Primary Domain Controller (PDC) using
<code class="command">tdbsam</code>
</h5></div></div></div><a id="id438182"
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">Section 15.1.8, “Samba Account Information
Databases”</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"
id="samba-rgs-pdc-ads">15.1.6.3.2. Primary Domain Controller (PDC) with
Active Directory</h5></div></div></div><a
id="id438710" class="indexterm"></a><div
class="para">
+ Although it is possible for Samba to be a member of an Active Directory, it is not
possible for Samba to operate as an Active Directory domain controller.
+ </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"
id="s2-samba-security-modes">15.1.7. Samba Security
Modes</h3></div></div></div><a id="id570858"
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"
id="s3-samba-user-level">15.1.7.1. User-Level
Security</h4></div></div></div><a id="id630706"
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">
+ The following sections describe other implementations of user-level security.
+ </div><div class="section"
id="s3-samba-domain-security-mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s3-samba-domain-security-mode">15.1.7.1.1. Domain Security Mode
(User-Level Security)</h5></div></div></div><a
id="id421162" 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"
id="s3-samba-ads-security-mode">15.1.7.1.2. Active Directory Security Mode
(User-Level Security)</h5></div></div></div><a
id="id664801" class="indexterm"></a><div
class="para">
+ If you have an Active Directory environment, it is possible to join the domain as a
native Active Directory member. Even if a security policy restricts the use of
NT-compatible authentication protocols, the Samba server can join an ADS using Kerberos.
Samba in Active Directory member mode can accept Kerberos tickets.
+ </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"
id="s3-samba-server-security-mode">15.1.7.1.3. Server Security Mode
(User-Level Security)</h5></div></div></div><a
id="id479707" class="indexterm"></a><div
class="para">
+ Server security mode was previously used when Samba was not capable of acting as a
domain member server.
+ </div><div class="note"><div
class="admonition_header"><h2>Avoid using the server security
mode</h2></div><div class="admonition"><div
class="para">
+ It is highly recommended to <span
class="emphasis"><em>not</em></span> use this mode since
there are numerous security drawbacks.
+ </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"
id="s3-samba-share-level">15.1.7.2. Share-Level
Security</h4></div></div></div><a id="id923484"
class="indexterm"></a><div class="para">
+ With share-level security, the server accepts only a password without an explicit
username from the client. The server expects a password for each share, independent of the
username. There have been recent reports that Microsoft Windows clients have compatibility
issues with share-level security servers. Samba developers strongly discourage use of
share-level security.
+ </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"
id="s2-samba-account-info-dbs">15.1.8. Samba Account Information
Databases</h3></div></div></div><a id="id593135"
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="id841454"
class="indexterm"></a><a id="id438194"
class="indexterm"></a><a id="id595449"
class="indexterm"></a><a id="id424390"
class="indexterm"></a><a id="id906476"
class="indexterm"></a><a id="id601456"
class="indexterm"></a><a id="id609638"
class="indexterm"></a><a id="id639730"
class="indexterm"></a><a id="id527394"
class="indexterm"></a><div
class="variablelist"><dl><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">Section 14.1,
“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">Section 14.1.3.3, “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"
id="s2-samba-network-browsing">15.1.9. Samba Network
Browsing</h3></div></div></div><a id="id413301"
class="indexterm"></a><a id="id429748"
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">
+ A domain master browser collates the browse lists from local master browsers on all
subnets so that browsing can occur between workgroups and subnets. Also, the domain master
browser should preferably be the local master browser for its own subnet.
+ </div><div class="section"
id="s3-samba-domain-browsing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-domain-browsing">15.1.9.1. Domain
Browsing</h4></div></div></div><a id="id726120"
class="indexterm"></a><div class="para">
+ By default, a Windows server PDC for a domain is also the domain master browser for
that domain. A Samba server must <span
class="emphasis"><em>not</em></span> be set up as a domain
master server in this type of situation
+ </div><div class="para">
+ For subnets that do not include the Windows server PDC, a Samba server can be
implemented as a local master browser. Configuring the <code
class="filename">/etc/samba/smb.conf</code> file for a local master
browser (or no browsing at all) in a domain controller environment is the same as
workgroup configuration.
+ </div></div><div class="section"
id="s3-samba-wins"><div class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-wins">15.1.9.2. WINS (Windows Internet Name
Server)</h4></div></div></div><a id="id1000229"
class="indexterm"></a><a id="id590100"
class="indexterm"></a><div class="para">
+ Either a Samba server or a Windows NT server can function as a WINS server. When a
WINS server is used with NetBIOS enabled, UDP unicasts can be routed which allows name
resolution across networks. Without a WINS server, the UDP broadcast is limited to the
local subnet and therefore cannot be routed to other subnets, workgroups, or domains. If
WINS replication is necessary, do not use Samba as your primary WINS server, as Samba does
not currently support WINS replication.
+ </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>Using WINS</h2></div><div
class="admonition"><div class="para">
+ All servers (including Samba) should connect to a WINS server to resolve NetBIOS
names. Without WINS, browsing only occurs on the local subnet. Furthermore, even if a
domain-wide list is somehow obtained, hosts cannot be resolved for the client without
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"
id="s2-samba-cups">15.1.10. Samba with CUPS Printing
Support</h3></div></div></div><a id="id535298"
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"
id="s3-samba-cups-smb.conf">15.1.10.1. Simple <code
class="filename">smb.conf</code>
Settings</h4></div></div></div><a id="id771695"
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">
+ Other printing configurations are also possible. To add additional security and
privacy for printing confidential documents, users can have their own print spooler not
located in a public path. If a job fails, other users would not have access to the file.
+ </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"
id="s2-samba-programs">15.1.11. Samba Distribution
Programs</h3></div></div></div><a id="id600979"
class="indexterm"></a><h4> <code
class="filename">findsmb</code> </h4><a
id="id495888" class="indexterm"></a><a
id="id900988" 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> <code
class="filename">net</code> </h4><a id="id708150"
class="indexterm"></a><a id="id409080"
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> <code
class="filename">nmblookup</code> </h4><a
id="id768124" class="indexterm"></a><a
id="id468208" 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">
+ Here is an example:
+ </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> <code
class="filename">pdbedit</code> </h4><a
id="id411339" class="indexterm"></a><a
id="id468187" 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">
+ The following are examples of adding, deleting, and listing users:
+ </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> <code
class="filename">rpcclient</code> </h4><a
id="id1055021" class="indexterm"></a><a
id="id676869" 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> <code class="filename">smbcacls</code>
</h4><a id="id1297753" class="indexterm"></a><a
id="id402092" 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> <code class="filename">smbclient</code>
</h4><a id="id826313" class="indexterm"></a><a
id="id1297759" 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> <code class="filename">smbcontrol</code>
</h4><a id="id758039" class="indexterm"></a><a
id="id525284" 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> <code class="filename">smbpasswd</code>
</h4><a id="id827944" class="indexterm"></a><a
id="id896685" 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> <code class="filename">smbspool</code>
</h4><a id="id418387" class="indexterm"></a><a
id="id424401" 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> <code class="filename">smbstatus</code>
</h4><a id="id793640" class="indexterm"></a><a
id="id431016" 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> <code class="filename">smbtar</code>
</h4><a id="id599592" class="indexterm"></a><a
id="id565752" 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> <code class="filename">testparm</code>
</h4><a id="id1268887" class="indexterm"></a><a
id="id461202" 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">
+ For example:
+ </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> <code
class="filename">wbinfo</code> </h4><a id="id826639"
class="indexterm"></a><a id="id596040"
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"
id="s2-samba-resources">15.1.12. Additional
Resources</h3></div></div></div><a id="id678743"
class="indexterm"></a><div class="para">
+ The following sections give you the means to explore Samba in greater detail.
+ </div><div class="section"
id="s3-samba-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-resources-installed">15.1.12.1. Installed
Documentation</h4></div></div></div><a id="id704809"
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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</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"
id="s3-samba-resources-published">15.1.12.2. Related
Books</h4></div></div></div><a id="id637367"
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"
id="s3-samba-resources-community">15.1.12.3. Useful
Websites</h4></div></div></div><a id="id750668"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.samba.org/">http://www.samba.org/</a> —
Homepage for the Samba distribution and all official documentation created by the Samba
development team. Many resources are available in HTML and PDF formats, while others are
only available for purchase. Although many of these links are not Fedora specific, some
concepts may apply.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://us1.samba.org/samba/archives.html">http://samba...
</a> — Active email lists for the Samba community. Enabling digest mode is
recommended due to high levels of list activity.
+ </div></li><li class="listitem"><div
class="para">
+ Samba newsgroups — Samba threaded newsgroups, such as
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="en-US" class="section" id="s1-FTP"
lang="en-US"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-FTP">15.2. FTP</h2></div></div></div><a
id="id837047" class="indexterm"></a><a
id="id826660" 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"
id="s2-ftp-protocol">15.2.1. The File Transfer
Protocol</h3></div></div></div><a id="id537407"
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"
id="s3-ftp-protocol-multiport">15.2.1.1. Multiple Ports, Multiple
Modes</h4></div></div></div><a id="id495894"
class="indexterm"></a><a id="id592264"
class="indexterm"></a><a id="id437931"
class="indexterm"></a><a id="id912753"
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">
+ The following defines these modes:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">active
mode</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">passive mode</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">Section 15.2.5.8,
“Network Options”</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"
id="s2-ftp-servers">15.2.2. FTP
Servers</h3></div></div></div><a id="id667724"
class="indexterm"></a><a id="id642748"
class="indexterm"></a><a id="id1307283"
class="indexterm"></a><a id="id421360"
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.re...;.
+ </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"
id="s3-ftp-servers-vsftpd">15.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"
id="s3-ftp-vsftpd-conf">15.2.3. Files Installed with <code
class="command">vsftpd</code>
</h3></div></div></div><a id="id921441"
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">Section 15.2.4, “Starting
and Stopping <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 15 <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">Section 15.2.5, “
<code class="command">vsftpd</code> Configuration Options”</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"
id="s2-ftp-vsftpd-start">15.2.4. Starting and Stopping <code
class="command">vsftpd</code>
</h3></div></div></div><a id="id840559"
class="indexterm"></a><a id="id901010"
class="indexterm"></a><a id="id684979"
class="indexterm"></a><a id="id813100"
class="indexterm"></a><a id="id846694"
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">Chapter 7, <em>Services and
Daemons</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"
id="s3-ftp-vsftpd-start-multi">15.2.4.1. Starting Multiple Copies of <code
class="command">vsftpd</code>
</h4></div></div></div><a id="id586979"
class="indexterm"></a><a id="id542045"
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">Chapter 6, <em>Network
Interfaces</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">Section 11.2, “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"
id="s2-ftp-vsftpd-conf">15.2.5. <code
class="command">vsftpd</code> Configuration
Options</h3></div></div></div><a id="id1012585"
class="indexterm"></a><a id="id667737"
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 <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"
id="s3-ftp-vsftpd-conf-opt-daemon">15.2.5.1. Daemon
Options</h4></div></div></div><a id="id423869"
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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-login">15.2.5.2. Log In Options and Access
Controls</h4></div></div></div><a id="id817698"
class="indexterm"></a><a id="id1283992"
class="indexterm"></a><div class="para">
+ The following is a list of directives which control the login behavior and access
control mechanisms.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">anonymous_enable</code> — When enabled,
anonymous users are allowed to log in. The usernames <code
class="computeroutput">anonymous</code> and <code
class="computeroutput">ftp</code> are accepted.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div><div class="para">
+ Refer to <a class="xref"
href="#s3-ftp-vsftpd-conf-opt-anon">Section 15.2.5.3, “Anonymous User
Options”</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">
+ There is no default value for this directive.
+ </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">
+ There is no default value for this directive.
+ </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">
+ The default value is <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">
+ By default <code class="command">vsftpd</code> displays its
standard banner.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_enable</code> — When enabled,
local users are allowed to log into the system.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div><div class="para">
+ Refer to <a class="xref"
href="#s3-ftp-vsftpd-conf-opt-usr">Section 15.2.5.4, “Local User
Options”</a> for a list of directives affecting local users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pam_service_name</code> — Specifies the
PAM service name for <code class="command">vsftpd</code>.
+ </div><div class="para">
+ The default value is <code class="command">ftp</code>. Note,
in Fedora, the value is set to <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-anon">15.2.5.3. Anonymous User
Options</h4></div></div></div><a id="id683611"
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">
+ The default value is <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">
+ There is no default value for this directive.
+ </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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-usr">15.2.5.4. Local User
Options</h4></div></div></div><a id="id702538"
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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ There is no default value for this directive.
+ </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">
+ The default value is <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">
+ The default value is <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">
+ There is no default value for this directive.
+ </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"
id="s3-ftp-vsftpd-conf-opt-dir">15.2.5.5. Directory
Options</h4></div></div></div><a id="id428576"
class="indexterm"></a><div class="para">
+ The following lists directives which affect directories.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">dirlist_enable</code> — When enabled,
users are allowed to view directory lists.
+ </div><div class="para">
+ The default value is <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">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-file">15.2.5.6. File Transfer
Options</h4></div></div></div><a id="id1283966"
class="indexterm"></a><div class="para">
+ The following lists directives which affect directories.
+ </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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-log">15.2.5.7. Logging
Options</h4></div></div></div><a id="id938266"
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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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">
+ The default value is <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">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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"
id="s3-ftp-vsftpd-conf-opt-net">15.2.5.8. Network
Options</h4></div></div></div><a id="id868383"
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">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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">
+ There is no default value for this directive.
+ </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">Section 15.2.4.1, “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">
+ There is no default value for this directive.
+ </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">Section 15.2.4.1, “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">
+ There is no default value for this directive.
+ </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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s2-ftp-resources">15.2.6. Additional
Resources</h3></div></div></div><a id="id439260"
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"
id="s3-ftp-installed-documentation">15.2.6.1. Installed
Documentation</h4></div></div></div><a id="id1286742"
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><dt
class="varlistentry"><span class="term">Server
Applications</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">Configuration
Files</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"
id="s3-ftp-useful-websites">15.2.6.2. Useful
Websites</h4></div></div></div><a id="id561079"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/&l... — The
<code class="command">vsftpd</code> project page is a great place to
locate the latest documentation and to contact the author of the software.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://slacksite.com/other/ftp.html">http://slacksite....
— This website provides a concise explanation of the differences between active and
passive mode <code class="systemitem">FTP</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.ietf.org/rfc/rfc0959.txt">http://www.ietf.o...
— The original <em class="firstterm">Request for Comments</em>
(<em class="firstterm">RFC</em>) of the <code
class="systemitem">FTP</code> protocol from the IETF.
+ </div></li></ul></div></div></div></div></div></div><div
class="part" id="part-Monitoring_and_Automation"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part VI. Monitoring and
Automation</h1></div></div></div><div
class="partintro" id="id742118"><div></div><div
class="para">
+ This part describes various tools that allow system administrators to monitor system
performance, automate system tasks, and report bugs.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a href="#ch-System_Monitoring_Tools">16.
System Monitoring
Tools</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-sysinfo-system-processes">16.1.
System Processes</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-memory-usage">16.2.
Memory Usage</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-filesystems">16.3. File
Systems</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-hardware">16.4.
Hardware</a></span></dt><dt><span
class="section"><a
href="#s1-sysinfo-additional-resources">16.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysinfo-installed-docs">16.5.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="#ch-Viewing_and_Managing_Log_Files">17. Viewing and Managing Log
Files</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-configu
ring-rsyslog">17.1. Configuring
rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-global-directives">17.1.1.
Global Directives</a></span></dt><dt><span
class="section"><a href="#s2-modules">17.1.2.
Modules</a></span></dt><dt><span
class="section"><a href="#s2-rules">17.1.3.
Rules</a></span></dt><dt><span
class="section"><a href="#s2-rsyslog-cmd-options">17.1.4.
<span
class="application"><strong>rsyslog</strong></span> Command
Line
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-logfiles-locating">17.2.
Locating Log Files</a></span></dt><dd><dl><dt><span
class="section"><a href="#configuring-logrotate">17.2.1.
Configuring
logrotate</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-logfiles-viewing">17.3. Viewing
Log Files</a></span></dt><dt><span
class="section"><a href="#s1-logfiles-adding">17.4. Adding a
Log File</a></span></dt><dt><span
class="section"><a href="#s1-logfiles-examining">17.5.
Monitoring Log File
s</a></span></dt><dt><span class="section"><a
href="#s1-log-files-additional-resources">17.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-log-files-installed-docs">17.6.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-log-files-useful-websites">17.6.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-Automating_System_Tasks">18.
Automating System
Tasks</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-autotasks-cron-anacron">18.1.
Cron and Anacron</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-autotasks-cron-service">18.1.1.
Starting and Stopping the Service</a></span></dt><dt><span
class="section"><a
href="#s2-configuring-anacron-jobs">18.1.2. Configuring Anacron
Jobs</a></span></dt><dt><span
class="section"><a href="#s2-configuring-cron-jobs">18.1.3.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a href="#s2-autotasks-c
ron-access">18.1.4. Controlling Access to
Cron</a></span></dt><dt><span
class="section"><a
href="#s2-black-white-listing-of-cron-jobs">18.1.5. Black/White Listing of
Cron Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-autotasks-at-batch">18.2. At and
Batch</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-autotasks-at-configuring">18.2.1. Configuring At
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-batch-configuring">18.2.2. Configuring Batch
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-viewing">18.2.3. Viewing Pending
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-commandline-options">18.2.4. Additional Command Line
Options</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-controlling-access">18.2.5. Controlling Access
to At and Batch</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-service">18.2.6. Starting and Stopp
ing the Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-autotasks-additional-resources">18.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-autotasks-installed-docs">18.3.1. Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-abrt">19. Automatic
Bug-Reporting Tool
(ABRT)</a></span></dt><dd><dl><dt><span
class="section"><a href="#id1226654">19.1.
Overview</a></span></dt><dt><span
class="section"><a href="#id976999">19.2. Installing and
Running ABRT</a></span></dt><dt><span
class="section"><a href="#abrt-plugins">19.3. ABRT
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a href="#analyzer-plugins">19.3.1. Analyzer
Plugins</a></span></dt><dt><span
class="section"><a href="#reporter-plugins">19.3.2. Reporter
Plugins</a></span></dt><dt><span
class="section"><a
href="#configuring-plugins-in-the-gui">19.3.3. Plugin Configuration in the
GUI</a></span></dt></dl></dd><
dt><span class="section"><a
href="#generating-backtrace">19.4. Generating
Backtraces</a></span></dt><dd><dl><dt><span
class="section"><a href="#troubleshooting">19.4.1.
Troubleshooting Backtrace
Generation</a></span></dt></dl></dd><dt><span
class="section"><a href="#id424708">19.5. Using the Command
Line Interface</a></span></dt><dd><dl><dt><span
class="section"><a href="#id424722">19.5.1. Viewing
Crashes</a></span></dt><dt><span
class="section"><a href="#id679552">19.5.2. Reporting
Crashes</a></span></dt><dt><span
class="section"><a href="#id568017">19.5.3. Deleting
Crashes</a></span></dt></dl></dd><dt><span
class="section"><a href="#configuring">19.6. Configuring
ABRT</a></span></dt><dt><span
class="section"><a
href="#configuring-centralized-crash-collection">19.7. Configuring
Centralized Crash
Collection</a></span></dt><dd><dl><dt><span
class="section"><a href="#id583691">19.7.1. Testing
ABRT's Crash Detection</a></span></dt><dt><span
class="section"><a href="#testing-upl
oad-method">19.7.2. Testing the Upload
Method</a></span></dt></dl></dd><dt><span
class="section"><a
href="#configuring-automatic-reporting">19.8. Configuring Automatic
Reporting</a></span></dt></dl></dd></dl></div></div><div
xml:lang="en-US" class="chapter"
id="ch-System_Monitoring_Tools" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 16. System Monitoring
Tools</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-sysinfo-system-processes">16.1. System
Processes</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-memory-usage">16.2.
Memory Usage</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-filesystems">16.3. File
Systems</a></span></dt><dt><span
class="section"><a href="#s1-sysinfo-hardware">16.4.
Hardware</a></span></dt><dt><span
class="section"><a
href="#s1-sysinfo-additional-resources">16.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-sysinfo-installed
-docs">16.5.1. Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id584516" class="indexterm"></a><a
id="id588402" class="indexterm"></a><div
class="para">
+ Before you learn how to configure your system, you should learn how to gather essential
system information. For example, you should know how to find the amount of free memory,
the amount of available hard drive space, how your hard drive is partitioned, and what
processes are running. This chapter discusses how to retrieve this type of information
from your Fedora system using simple commands and a few simple programs.
+ </div><div class="section"
id="s1-sysinfo-system-processes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysinfo-system-processes">16.1. System
Processes</h2></div></div></div><a id="id410698"
class="indexterm"></a><a id="id725696"
class="indexterm"></a><a id="id1457952"
class="indexterm"></a><div class="para">
+ The <code class="command">ps ax</code> command displays a list
of current system processes, including processes owned by other users. To display the
owner alongside each process, use the <code class="command">ps
aux</code> command. This list is a static list; in other words, it is a snapshot of
what was running when you invoked the command. If you want a constantly updated list of
running processes, use <code class="command">top</code> as described
below.
+ </div><div class="para">
+ The <code class="command">ps</code> output can be long. To
prevent it from scrolling off the screen, you can pipe it through less:
+ </div><pre class="screen"><code
class="command">ps aux | less</code></pre><div
class="para">
+ You can use the <code class="command">ps</code> command in
combination with the <code class="command">grep</code> command to
see if a process is running. For example, to determine if <span
class="application"><strong>Emacs</strong></span> is
running, use the following command:
+ </div><pre class="screen"><code
class="command">ps ax | grep emacs</code></pre><a
id="id437662" class="indexterm"></a><a
id="id571193" class="indexterm"></a><div
class="para">
+ The <code class="command">top</code> command displays currently
running processes and important information about them including their memory and CPU
usage. The list is both real-time and interactive. An example of output from the <code
class="command">top</code> command is provided as follows:
+ </div><pre class="screen">top - 18:11:48 up 1 min, 1 user, load
average: 0.68, 0.30, 0.11
+Tasks: 122 total, 1 running, 121 sleeping, 0 stopped, 0 zombie
+Cpu(s): 0.0%us, 0.5%sy, 0.0%ni, 93.4%id, 5.7%wa, 0.2%hi, 0.2%si, 0.0
+Mem: 501924k total, 376496k used, 125428k free, 29664k buffers
+Swap: 1015800k total, 0k used, 1015800k free, 189008k cached
+
+ PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+ 1601 root 40 0 20172 1084 920 S 0.3 0.2 0:00.08 hald-addon-sto
+ 1998 silas 40 0 14984 1160 880 R 0.3 0.2 0:00.13 top
+ 1 root 40 0 19160 1412 1156 S 0.0 0.3 0:00.96 init
+ 2 root 40 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
+ 3 root RT 0 0 0 0 S 0.0 0.0 0:00.05 migration/0
+ 4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
+ 5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
+ 6 root RT 0 0 0 0 S 0.0 0.0 0:00.04 migration/1
+ 7 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
+ 8 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
+ 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0
+ 10 root 20 0 0 0 0 S 0.0 0.0 0:00.01 events/1
+ 11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuset
+ 12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre><div class="para">
+ To exit <code class="command">top</code>, press the <span
class="keycap"><strong>q</strong></span> key.
+ </div><div class="para">
+ <a class="xref" href="#interactive-top-command">Table 16.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 <code class="command">top</code>(1) manual page.
+ </div><div class="table"
id="interactive-top-command"><h6>Table 16.1. Interactive top
commands</h6><div class="table-contents"><table
summary="Interactive top commands"
border="1"><colgroup><col class="command"
width="50%" /><col class="description" width="50%"
/></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span
class="keycap"><strong>Space</strong></span>
+ </td><td>
+ Immediately refresh the display
+ </td></tr><tr><td>
+ <span class="keycap"><strong>h</strong></span>
+ </td><td>
+ Display a help screen
+ </td></tr><tr><td>
+ <span class="keycap"><strong>k</strong></span>
+ </td><td>
+ Kill a process. You are prompted for the process ID and the signal to send to it.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>n</strong></span>
+ </td><td>
+ Change the number of processes displayed. You are prompted to enter the number.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>u</strong></span>
+ </td><td>
+ Sort by user.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>M</strong></span>
+ </td><td>
+ Sort by memory usage.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>P</strong></span>
+ </td><td>
+ Sort by CPU usage.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="id481942"
class="indexterm"></a><a id="id839819"
class="indexterm"></a><div class="para">
+ If you prefer a graphical interface for <code
class="command">top</code>, you can use the <span
class="application"><strong>GNOME System
Monitor</strong></span>. To start it from the desktop, 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
execute <code class="command">gnome-system-monitor</code> at a shell
prompt. Select the <span
class="guilabel"><strong>Processes</strong></span> tab.
+ </div><div class="para">
+ The <span class="application"><strong>GNOME System
Monitor</strong></span> allows you to search for a process in the list of
running processes. Using the <span class="application"><strong>GNOME
System Monitor</strong></span>, you can also view all processes, your
processes, or active processes.
+ </div><div class="para">
+ The <span
class="guimenuitem"><strong>Edit</strong></span> menu item
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 or start a process.
+ </div></li><li class="listitem"><div
class="para">
+ End a processes.
+ </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.
+ </div></li><li class="listitem"><div
class="para">
+ Edit the System Monitor preferences. These include changing the interval seconds to
refresh the list and selecting process fields to display in the System Monitor window.
+ </div></li></ul></div><div class="para">
+ The <span
class="guimenuitem"><strong>View</strong></span> menu item
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 my 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 the selected process.
+ </div></li><li class="listitem"><div
class="para">
+ Refresh the list of processes.
+ </div></li></ul></div><div class="para">
+ To stop a process, select it and click <span
class="guibutton"><strong>End Process</strong></span>.
Alternatively you can also stop a process by selecting it, clicking <span
class="guimenuitem"><strong>Edit</strong></span> on your
menu and selecting <span class="guimenuitem"><strong>Stop
Process</strong></span>.
+ </div><div class="para">
+ To sort the information by a specific column, click on the name of the column. This
sorts the information by the selected column in ascending order. Click on the name of the
column again to toggle the sort between ascending and descending order.
+ </div><div class="figure"
id="fig-sysinfo-processes"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-processes.png" alt="GNOME System Monitor —
Processes tab" /><div class="longdesc"><div
class="para">
+ Processes tab of the GNOME System Monitor
+ </div></div></div></div><h6>Figure 16.1. GNOME System
Monitor — Processes tab </h6></div><br class="figure-break"
/></div><div class="section"
id="s1-sysinfo-memory-usage"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysinfo-memory-usage">16.2. Memory
Usage</h2></div></div></div><a id="id415532"
class="indexterm"></a><a id="id415545"
class="indexterm"></a><a id="id831221"
class="indexterm"></a><a id="id831230"
class="indexterm"></a><div class="para">
+ The <code class="command">free</code> command displays the total
amount of physical memory and swap space for the system as well as the amount of memory
that is used, free, shared, in kernel buffers, and cached.
+ </div><pre class="screen"> total used
free shared buffers cached
+Mem: 4017660 1619044 2398616 0 59864 637968
+-/+ buffers/cache: 921212 3096448
+Swap: 3071996 0 3071996</pre><div class="para">
+ The command <code class="command">free -m</code> shows the same
information in megabytes, which are easier to read.
+ </div><pre class="screen"> total used
free shared buffers cached
+Mem: 3923 1569 2353 0 58 626
+-/+ buffers/cache: 884 3038
+Swap: 2999 0 2999</pre><div class="para">
+ If you prefer a graphical interface for <code
class="command">free</code>, you can use the <span
class="application"><strong>GNOME System
Monitor</strong></span>. To start it from the desktop, 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
execute <code class="command">gnome-system-monitor</code> at a shell
prompt. Click on the <span
class="guilabel"><strong>Resources</strong></span> tab.
+ </div><div class="figure"
id="fig-sysinfo-memory"><div class="figure-contents"><div
class="mediaobject"><img
src="images/system-monitor-resources.png" alt="GNOME System Monitor —
Resources tab" /><div class="longdesc"><div
class="para">
+ Resources tab of the GNOME System Monitor
+ </div></div></div></div><h6>Figure 16.2. GNOME System
Monitor — Resources tab </h6></div><br class="figure-break"
/></div><div class="section"
id="s1-sysinfo-filesystems"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysinfo-filesystems">16.3. File
Systems</h2></div></div></div><a id="id1226688"
class="indexterm"></a><a id="id640487"
class="indexterm"></a><a id="id640497"
class="indexterm"></a><div class="para">
+ The <code class="command">df</code> command reports the
system's disk space usage. If you Execute the command <code
class="command">df</code> at a shell prompt, the output looks similar
to the following:
+ </div><pre class="screen">Filesystem 1K-blocks
Used Available Use% Mounted on
+rootfs 6726160 3091216 3566620 47% /
+udev 500716 0 500716 0% /dev
+tmpfs 507840 2152 505688 1% /dev/shm
+tmpfs 507840 644 507196 1% /run
+/dev/sda1 6726160 3091216 3566620 47% /
+tmpfs 507840 0 507840 0% /sys/fs/cgroup
+tmpfs 507840 0 507840 0% /media
+/dev/sda4 139412616 105018908 27367684 80% /home
+/dev/sda1 6726160 3091216 3566620 47% /tmp
+/dev/sda1 6726160 3091216 3566620 47% /var/tmp</pre><div
class="para">
+ By default, this utility 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, use the command <code class="command">df -h</code>. The
<code class="command">-h</code> argument stands for human-readable
format. The output looks similar to the following:
+ </div><pre class="screen">Filesystem Size Used Avail
Use% Mounted on
+rootfs 6.5G 3.0G 3.5G 47% /
+udev 489M 0 489M 0% /dev
+tmpfs 496M 2.2M 494M 1% /dev/shm
+tmpfs 496M 644K 496M 1% /run
+/dev/sda1 6.5G 3.0G 3.5G 47% /
+tmpfs 496M 0 496M 0% /sys/fs/cgroup
+tmpfs 496M 0 496M 0% /media
+/dev/sda4 133G 101G 27G 80% /home
+/dev/sda1 6.5G 3.0G 3.5G 47% /tmp
+/dev/sda1 6.5G 3.0G 3.5G 47% /var/tmp</pre><a
id="id584086" class="indexterm"></a><a
id="id629476" class="indexterm"></a><div
class="para">
+ In the list of mounted partitions, there is an entry for <code
class="filename">/dev/shm</code>. This entry represents the
system's virtual memory file system.
+ </div><a id="id580817"
class="indexterm"></a><div class="para">
+ The <code class="command">du</code> command displays the
estimated amount of space being used by files in a directory. If you execute <code
class="command">du</code> at a shell prompt, the disk usage for each of
the subdirectories is displayed in a list. The grand total for the current directory and
subdirectories are also shown as the last line in the list. If you do not want to see the
totals for all the subdirectories, use the command <code
class="command">du -hs</code> to see only the grand total for the
directory in human-readable format. Use the <code class="command">du
--help</code> command to see more options.
+ </div><div class="para">
+ To view the system's partitions and disk space usage in a graphical format, use
the <span class="guilabel"><strong>GNOME System
Monitor</strong></span> by selecting <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
executing the <code class="command">gnome-system-monitor</code>
command at a shell prompt. Select the <span
class="guilabel"><strong>File Systems</strong></span> tab
to view the system's partitions.
+ </div><div class="figure"
id="fig-sysinfo-filesystems"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-file-systems.png" alt="GNOME System Monitor —
File Systems tab" /><div class="longdesc"><div
class="para">
+ File Systems tab of the GNOME System Monitor
+ </div></div></div></div><h6>Figure 16.3. GNOME System
Monitor — File Systems tab </h6></div><br class="figure-break"
/></div><div class="section"
id="s1-sysinfo-hardware"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysinfo-hardware">16.4. Hardware</h2></div></div></div><a
id="id565569" class="indexterm"></a><a
id="id565315" class="indexterm"></a><div
class="para">
+ If you are having trouble configuring your hardware or just want to know what hardware
is in your system, you can use the <code
class="command">lspci</code> command to list all PCI devices. Use the
command <code class="command">lspci -v</code> for more verbose
information or <code class="command">lspci -vv</code> for very
verbose output.
+ </div><div class="para">
+ For example, <code class="command">lspci</code> can be used to
determine the manufacturer, model, and memory size of a system's video card:
+ </div><pre class="screen">00:02.1 Display controller: Intel
Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
+ Subsystem: Lenovo Device 20e4
+ Flags: bus master, fast devsel, latency 0
+ Memory at f4200000 (64-bit, non-prefetchable) [size=1M]
+ Capabilities: [d0] Power Management version 3</pre><div
class="para">
+ The <code class="command">lspci</code> is also useful to
determine the network card in your system if you do not know the manufacturer or model
number.
+ </div></div><div class="section"
id="s1-sysinfo-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysinfo-additional-resources">16.5. Additional
Resources</h2></div></div></div><div
class="para">
+ To learn more about gathering system information, refer to the following resources.
+ </div><div class="section"
id="s2-sysinfo-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-sysinfo-installed-docs">16.5.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">ps --help</code> — Displays a list of
options that can be used with <code class="command">ps</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">top</code> manual page — Execute
<code class="command">man top</code> to learn more about <code
class="command">top</code> and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">free</code> manual page — Execute
<code class="command">man free</code> to learn more about <code
class="command">free</code> and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">df</code> manual page — Execute
<code class="command">man df</code> to learn more about the <code
class="command">df</code> command and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">du</code> manual page — Execute
<code class="command">man du</code> to learn more about the <code
class="command">du</code> command and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">lspci</code> manual page — Execute
<code class="command">man lspci</code> to learn more about the
<code class="command">lspci</code> command and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="id438718" class="indexterm"></a>
+ <code class="filename">/proc/</code> directory — The
contents of the <code class="filename">/proc/</code> directory can
also be used to gather more detailed system information.
+ </div></li></ul></div></div></div></div><div
xml:lang="en-US" class="chapter"
id="ch-Viewing_and_Managing_Log_Files" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 17. Viewing and Managing Log
Files</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-configuring-rsyslog">17.1. Configuring
rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-global-directives">17.1.1.
Global Directives</a></span></dt><dt><span
class="section"><a href="#s2-modules">17.1.2.
Modules</a></span></dt><dt><span
class="section"><a href="#s2-rules">17.1.3.
Rules</a></span></dt><dt><span
class="section"><a href="#s2-rsyslog-cmd-options">17.1.4.
<span
class="application"><strong>rsyslog</strong></span> Command
Line
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-logfiles-locating">17.2.
Locating Log Files</a></span></dt><dd><dl><dt><span
class="section"><a href="#configuring-logrotate">17.2.1. Co
nfiguring
logrotate</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-logfiles-viewing">17.3. Viewing
Log Files</a></span></dt><dt><span
class="section"><a href="#s1-logfiles-adding">17.4. Adding a
Log File</a></span></dt><dt><span
class="section"><a href="#s1-logfiles-examining">17.5.
Monitoring Log Files</a></span></dt><dt><span
class="section"><a
href="#s1-log-files-additional-resources">17.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-log-files-installed-docs">17.6.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-log-files-useful-websites">17.6.2. Useful
Websites</a></span></dt></dl></dd></dl></div><a
id="id833549" class="indexterm"></a><a
id="id550379" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Log files</em> are files that contain
messages about the system, including the kernel, services, and applications running on it.
There are different log files for different information. For example, there is a default
system log file, a log file just for security messages, and a log file for cron tasks.
+ </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="id618875" class="indexterm"></a><a
id="id576455" 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"
id="s1-configuring-rsyslog">17.1. Configuring
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"
id="s2-global-directives">17.1.1. Global
Directives</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"
id="s2-modules">17.1.2. Modules</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">Section 17.1.3.3, “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/">...
+ </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"
id="s2-rules">17.1.3. Rules</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">Section 17.1.3.1, “Filter Conditions”</a>
and for information on actions, refer to <a class="xref"
href="#s3-actions">Section 17.1.3.2, “Actions”</a>.
+ </div><div class="section"
id="s3-filter-conditions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-filter-conditions">17.1.3.1. Filter
Conditions</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><dt
class="varlistentry"><span
class="term">Facility/Priority-based
filters</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">
+ The following are a few examples of simple facility/priority-based filters:
+ </div><pre class="screen">
+kern.* # Selects all kernel syslog messages with any priority
+</pre><pre class="screen">
+mail.crit # Selects all mail syslog messages with priority <code
class="command">crit</code> and higher.
+</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">Property-based filters</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">Section 17.1.3.3.2, “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">Table 17.1, “Property-based
compare-operations”</a>.
+ </div><div class="table"
id="table-compare-operations"><h6>Table 17.1. Property-based
compare-operations</h6><div class="table-contents"><table
summary="Property-based compare-operations"
border="1"><colgroup><col width="38%"
class="operation" /><col width="63%"
class="description" /></colgroup><thead><tr><th>
+ Compare-operation
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <em
class="parameter"><code>contains</code></em>
+ </td><td>
+ Checks whether the provided string matches any part of the text provided by
the property.
+ </td></tr><tr><td>
+ <em
class="parameter"><code>isequal</code></em>
+ </td><td>
+ Compares the provided string against all of the text provided by the
property.
+ </td></tr><tr><td>
+ <em
class="parameter"><code>startswith</code></em>
+ </td><td>
+ Checks whether the provided string matches a prefix of the text provided by
the property.
+ </td></tr><tr><td>
+ <em
class="parameter"><code>regex</code></em>
+ </td><td>
+ Compares the provided POSIX BRE (Basic Regular Expression) regular expression
against the text provided by the property.
+ </td></tr><tr><td>
+ <em
class="parameter"><code>ereregex</code></em>
+ </td><td>
+ Compares the provided POSIX ERE (Extended Regular Expression) regular
expression against the text provided by the property.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ To define a property-based filter, use the following syntax:
+ </div><pre class="screen">:<em
class="replaceable"><code><PROPERTY></code></em>,
[!]<em
class="replaceable"><code><COMPARE_OPERATION></code></em>,
"<em
class="replaceable"><code><STRING></code></em>"</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code><PROPERTY></code></em>
attribute specifies the desired property (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">Table 17.1, “Property-based
compare-operations”</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">
+ The following are few examples of property-based filters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The following filter selects syslog messages which contain the string <code
class="literal">error</code> in their message text:
+ </div><pre class="screen">:msg, contains,
"error"</pre></li><li class="listitem"><div
class="para">
+ The following filter selects syslog messages received from the hostname
<code class="literal">host1</code>:
+ </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">Expression-based
filters</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">
+ To define an expression-based filter, use the following syntax:
+ </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>Do not use regular
expressions</h2></div><div class="admonition"><div
class="para">
+ Regular expressions are currently not supported in expression-based filters.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term">BSD-style
blocks</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">Example 17.1, “BSD-style block”</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>Example 17.1. BSD-style
block</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"
id="s3-actions">17.1.3.2. Actions</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><dt
class="varlistentry"><span class="term">Saving syslog
messages to log files</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">Section 17.1.3.3.1, “Generating dynamic
file names”</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">Sending syslog messages over the
network</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 # Forwards
messages to 192.168.0.1 via the <code class="systemitem">UDP</code>
protocol</pre><pre class="screen">*.* @@example.com:18 # Forwards
messages to "example.com" using port 18 and the <code
class="systemitem">TCP</code> protocol</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">Output
channels</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">Section 17.2.1, “Configuring
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">Example 17.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>Example 17.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">Section 17.1.3.3, “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">
+ The <em
class="replaceable"><code><DB_HOST></code></em>
attribute specifies the database hostname.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code><DB_NAME></code></em>
attribute specifies the name of the database.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code><DB_USER></code></em>
attribute specifies the database user.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code><DB_PASSWORD></code></em>
attribute specifies the password used with the aforementioned database user.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code><TEMPLATE></code></em>
attribute specifies an optional use of a template that modifies the syslog message. For
more information on templates, refer to <a class="xref"
href="#s3-templates">Section 17.1.3.3, “Templates”</a>.
+ </div></li></ul></div><div
class="important"><div
class="admonition_header"><h2>Using MySQL and
PostgreSQL</h2></div><div class="admonition"><div
class="para">
+ Currently, <span
class="application"><strong>rsyslog</strong></span>
provides support for <code class="systemitem">MySQL</code> (for more
information, refer to <code class="filename">/usr/share/doc/rsyslog-<em
class="replaceable"><code><version-number></code></em>/rsyslog_mysql.html</code>)
and <code class="systemitem">PostgreSQL</code> databases only. In
order to use the <code class="systemitem">MySQL</code> and <code
class="systemitem">PostgreSQL</code> database writer functionality,
install the <span class="package">rsyslog-mysql</span> and <span
class="package">rsyslog-pgsql</span> packages installed, respectively.
Also, make sure you load the appropriate modules in your <code
class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad ommysql # Output module for MySQL support
+$ModLoad ompgsql # Output module for PostgreSQL support
+</pre><div class="para">
+ For more information on <span
class="application"><strong>rsyslog</strong></span>
modules, refer to <a class="xref"
href="#s2-modules">Section 17.1.2, “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">Discarding syslog
messages</span></dt><dd><div class="para">
+ To discard your selected messages, use the tilde character (<code
class="literal">~</code>). The following rule discards any cron syslog
messages:
+ </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>Using
templates</h2></div><div class="admonition"><div
class="para">
+ A template must be defined before it is used in an action, otherwise, it is
ignored.
+ </div></div></div><div class="para">
+ For more information on templates, refer to <a class="xref"
href="#s3-templates">Section 17.1.3.3, “Templates”</a>.
+ </div></div><div class="section"
id="s3-templates"><div class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-templates">17.1.3.3. Templates</h4></div></div></div><div
class="para">
+ Any output that is generated by <span
class="application"><strong>rsyslog</strong></span> can be
modified and formatted according to your needs through the use of templates. To create a
template use the following syntax:
+ </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> is the
template directive that indicates that the text following it, defines a template.
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code><TEMPLATE_NAME></code></em>
is the name of the template. Use this name to refer to the template.
+ </div></li><li class="listitem"><div
class="para">
+ Anything between the two quotation marks (<code
class="literal">"</code>…<code
class="literal">"</code>) is the actual template text. Within this
text, 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">Section 17.1.3.3.2,
“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>The sql and stdsql
options</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">Section 17.1.3.2,
“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"
id="s4-generating-dynamic-fnames">17.1.3.3.1. Generating dynamic file
names</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"
id="s4-properties">17.1.3.3.2. Properties</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">
+ The following are some examples of simple properties:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The following property simply obtains the whole message text of a syslog
message:
+ </div><pre class="screen">%msg%</pre></li><li
class="listitem"><div class="para">
+ The following property obtains the first two characters of the message text of a
syslog message:
+ </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"
id="s4-template-examples">17.1.3.3.3. Template
Examples</h5></div></div></div><div class="para">
+ This section presents few examples of <span
class="application"><strong>rsyslog</strong></span>
templates.
+ </div><div class="para">
+ <a class="xref" href="#example-temp1">Example 17.3, “A
verbose syslog message template”</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>Example 17.3. A verbose syslog message
template</h6><div class="example-contents"><pre
class="screen">$template
verbose,"%syslogseverity%,%syslogfacility%,%timegenerated%,%HOSTNAME%,%syslogtag%,%msg%\n"</pre></div></div><br
class="example-break" /><div class="para">
+ <a class="xref" href="#example-temp2">Example 17.4, “A
wall message template”</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>Example 17.4. A wall message
template</h6><div class="example-contents"><pre
class="screen">$template wallmsg,"\r\n\7Message from syslogd@%HOSTNAME%
at %timegenerated% ...\r\n %syslogtag%
%msg%\n\r"</pre></div></div><br class="example-break"
/><div class="para">
+ <a class="xref" href="#example-temp3">Example 17.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>Example 17.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><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:\nFROMHOST:
'%FROMHOST%', fromhost-ip: '%fromhost-ip%', HOSTNAME:
'%HOSTNAME%', PRI: %PRI%,\nsyslogtag '%syslogtag%', programname:
'%programname%', APP-NAME: '%APP-NAME%', PROCID: '%PROCID%',
MSGID: '%MSGID%',\nTIMESTAMP: '%TIMESTAMP%', STRUCTURED-DATA:
'%STRUCTURED-DATA%',\nmsg: '%msg%'\nescaped msg:
'%msg:::drop-cc%'\nrawmsg:
'%rawmsg%'\n\n\"</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%\n\"</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%\n\"</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%\n\"</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 cla
ss="title" id="s2-rsyslog-cmd-options">17.1.4. <span
class="application"><strong>rsyslog</strong></span> Command
Line Configuration</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">
+ For more information on various <code
class="command">rsyslogd</code> options, refer to <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"
id="s1-logfiles-locating">17.2. Locating Log
Files</h2></div></div></div><a id="id852708"
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="id852744"
class="indexterm"></a><a id="id852758"
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"
id="configuring-logrotate">17.2.1. Configuring
logrotate</h3></div></div></div><div
class="para">
+ The following is a sample <code
class="filename">/etc/logrotate.conf</code> configuration file:
+ </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>
— Enables compression of rotated log files. Similar directives include:
+ <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> — Specifies
the command to be used for compressing.
+ </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> — Specifies
what extension is to be used for compressing.
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>compressoptions</code></em> — Lets
you specify any options that may be passed to the used compression program.
+ </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"
id="s1-logfiles-viewing">17.3. Viewing Log
Files</h2></div></div></div><a id="id842453"
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="id599363"
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>Installing the gnome-system-log
package</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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</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">Figure 17.1, “ Log File Viewer ”</a>.
+ </div><a id="id534297"
class="indexterm"></a><a id="id534316"
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="Log File Viewer" /><div
class="longdesc"><div class="para">
+ Log File Viewer
+ </div></div></div></div><h6>Figure 17.1. Log File
Viewer </h6></div><br class="figure-break" /><a
id="id564695" 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="Log File Viewer —
filters" /><div class="longdesc"><div
class="para">
+ Log File Viewer — filters
+ </div></div></div></div><h6>Figure 17.2. Log File
Viewer — filters </h6></div><br class="figure-break" /><div
class="para">
+ Adding or editing a filter lets you define its parameters as is shown in <a
class="xref" href="#fig-redhat-filter-sample">Figure 17.3, “ Log
File Viewer — defining a filter ”</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="Log File Viewer —
defining a filter" /><div class="longdesc"><div
class="para">
+ Log File Viewer — defining a filter
+ </div></div></div></div><h6>Figure 17.3. Log File
Viewer — defining a filter </h6></div><br class="figure-break"
/><div class="para">
+ When defining a filter, you can edit the following parameters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Name</strong></span> — Specifies
the name of the filter.
+ </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>Effect</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>Figure 17.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"
id="s1-logfiles-adding">17.4. Adding a Log
File</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">Figure 17.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>Figure 17.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>Reading zipped log
files</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"
id="s1-logfiles-examining">17.5. Monitoring Log
Files</h2></div></div></div><a id="id619646"
class="indexterm"></a><a id="id969736"
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">Figure 17.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>Figure 17.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"
id="s1-log-files-additional-resources">17.6. Additional
Resources</h2></div></div></div><div
class="para">
+ To learn more about <span
class="application"><strong>rsyslog</strong></span>,
<span
class="application"><strong>logrotate</strong></span>, and
log files in general, refer to the following resources.
+ </div><div class="section"
id="s2-log-files-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-log-files-installed-docs">17.6.1. Installed
Documentation</h3></div></div></div><a id="id827414"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">rsyslogd</code> manual page — Type
<code class="command">man rsyslogd</code> to learn more about
<code class="command">rsyslogd</code> and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">rsyslog.conf</code> manual page — Type
<code class="command">man rsyslog.conf</code> to learn more about
the <code class="command">/etc/rsyslog.conf</code> configuration
file and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/rsyslog-<em
class="replaceable"><code><version-number></code></em>/
</code> — After installing the <span
class="package">rsyslog</span> package, this directory contains
extensive documentation in the <code class="systemitem">html</code>
format.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">logrotate</code> manual page — Type
<code class="command">man logrotate</code> to learn more about
<code class="command">logrotate</code> and its many options.
+ </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"
id="s2-log-files-useful-websites">17.6.2. Useful
Websites</h3></div></div></div><a id="id1263929"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.rsyslog.com/">http://www.rsyslog.com/</a...
— Offers a thorough technical breakdown of <span
class="package">rsyslog</span> features, documentation, configuration
examples, and video tutorials.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://wiki.rsyslog.com/index.php/Main_Page">http://wi...
— Contains useful <code class="filename">/etc/rsyslog.conf</code>
configuration examples.
+ </div></li></ul></div></div></div></div><div
xml:lang="en-US" class="chapter"
id="ch-Automating_System_Tasks" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 18. Automating System
Tasks</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-autotasks-cron-anacron">18.1. Cron and
Anacron</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-autotasks-cron-service">18.1.1.
Starting and Stopping the Service</a></span></dt><dt><span
class="section"><a
href="#s2-configuring-anacron-jobs">18.1.2. Configuring Anacron
Jobs</a></span></dt><dt><span
class="section"><a href="#s2-configuring-cron-jobs">18.1.3.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a href="#s2-autotasks-cron-access">18.1.4.
Controlling Access to Cron</a></span></dt><dt><span
class="section"><a
href="#s2-black-white-listing-of-cron-jobs">18.1.5. Black/White Listing of
Cron Jobs</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-autotasks-at-batch">18.2. At and
Batch</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-autotasks-at-configuring">18.2.1. Configuring At
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-batch-configuring">18.2.2. Configuring Batch
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-viewing">18.2.3. Viewing Pending
Jobs</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-commandline-options">18.2.4. Additional Command Line
Options</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-controlling-access">18.2.5. Controlling Access
to At and Batch</a></span></dt><dt><span
class="section"><a
href="#s2-autotasks-at-batch-service">18.2.6. Starting and Stopping the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-autotasks-additional-resources">18.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-autotasks-installed-docs">18.
3.1. Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id829023" 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="id596451"
class="indexterm"></a><div class="section"
id="s1-autotasks-cron-anacron"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-autotasks-cron-anacron">18.1. Cron and
Anacron</h2></div></div></div><a id="id641666"
class="indexterm"></a><a id="id764563"
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">Section 18.1.2, “Configuring Anacron
Jobs”</a> or <a class="xref"
href="#s2-configuring-cron-jobs">Section 18.1.3, “Configuring Cron
Jobs”</a>. To schedule one-time jobs, refer to <a class="xref"
href="#s1-autotasks-at-batch">Section 18.2, “At and 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"
id="s2-autotasks-cron-service">18.1.1. Starting and Stopping the
Service</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">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s2-configuring-anacron-jobs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-configuring-anacron-jobs">18.1.2. Configuring Anacron
Jobs</h3></div></div></div><a id="id412924"
class="indexterm"></a><a id="id412937"
class="indexterm"></a><a id="id449305"
class="indexterm"></a><a id="id449319"
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
+@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"
id="s3-anacron-examples">18.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
+@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"
id="s3-disabling-anacron">18.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"
id="s2-configuring-cron-jobs">18.1.3. Configuring Cron
Jobs</h3></div></div></div><a id="id537557"
class="indexterm"></a><a id="id702334"
class="indexterm"></a><a id="id702348"
class="indexterm"></a><a id="id481121"
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">Section 18.1.2, “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">
+ For any of the above values, an asterisk (*) can be used to specify all valid values.
For example, an asterisk for the month value means execute the command every month within
the constraints of the other values.
+ </div><div class="para">
+ A hyphen (-) between integers specifies a range of integers. For example, <strong
class="userinput"><code>1-4</code></strong> means the
integers 1, 2, 3, and 4.
+ </div><div class="para">
+ A list of values separated by commas (,) specifies a list. For example, <strong
class="userinput"><code>3, 4, 6, 8</code></strong>
indicates 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"
id="s2-autotasks-cron-access">18.1.4. Controlling Access to
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"
id="s2-black-white-listing-of-cron-jobs">18.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">Section 18.1.4,
“Controlling Access to 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"
id="s1-autotasks-at-batch">18.2. At and
Batch</h2></div></div></div><a id="id541048"
class="indexterm"></a><a id="id572835"
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"
id="s2-autotasks-at-configuring">18.2.1. Configuring At
Jobs</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">
+ The argument <em
class="replaceable"><code>time</code></em> can be one of
the following:
+ </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 — Specifies 12:00 a.m.
+ </div></li><li class="listitem"><div
class="para">
+ noon — Specifies 12:00 p.m.
+ </div></li><li class="listitem"><div
class="para">
+ teatime — Specifies 4:00 p.m.
+ </div></li><li class="listitem"><div
class="para">
+ month-name day year format — For example, January 15 2002 specifies the 15th day of
January in the year 2002. The year is optional.
+ </div></li><li class="listitem"><div
class="para">
+ MMDDYY, MM/DD/YY, or MM.DD.YY formats — For example, 011502 for the 15th day of
January in the year 2002.
+ </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">Section 18.2.3, “Viewing Pending
Jobs”</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">Section 18.2.5, “Controlling
Access to At and 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"
id="s2-autotasks-batch-configuring">18.2.2. Configuring Batch
Jobs</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">
+ If the set of commands or script tries to display information to standard out, 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">Section 18.2.3, “Viewing Pending
Jobs”</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">Section 18.2.5, “Controlling
Access to At and 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"
id="s2-autotasks-at-batch-viewing">18.2.3. Viewing Pending
Jobs</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"
id="s2-autotasks-commandline-options">18.2.4. Additional Command Line
Options</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>Table 18.1. <code
class="command">at</code> and <code
class="command">batch</code> Command Line Options</h6><div
class="table-contents"><table summary=" at and batch Command Line
Options" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-f</code>
+ </td><td>
+ Read the commands or shell script from a file instead of specifying them at the
prompt.
+ </td></tr><tr><td>
+ <code class="option">-m</code>
+ </td><td>
+ Send email to the user when the job has been completed.
+ </td></tr><tr><td>
+ <code class="option">-v</code>
+ </td><td>
+ Display the time that the job is executed.
+ </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"
id="s2-autotasks-at-batch-controlling-access">18.2.5. Controlling Access to
At and 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"
id="s2-autotasks-at-batch-service">18.2.6. Starting and Stopping the
Service</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">
+ Refer to <a class="xref"
href="#ch-Services_and_Daemons">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div></div><div class="section"
id="s1-autotasks-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-autotasks-additional-resources">18.3. Additional
Resources</h2></div></div></div><a id="id1306464"
class="indexterm"></a><a id="id725880"
class="indexterm"></a><a id="id725894"
class="indexterm"></a><div class="para">
+ To learn more about configuring automated tasks, refer to the following resources.
+ </div><div class="section"
id="s2-autotasks-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-autotasks-installed-docs">18.3.1. Installed
Documentation</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="en-US" class="chapter" id="ch-abrt"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 19. Automatic Bug-Reporting Tool
(ABRT)</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#id1226654">19.1.
Overview</a></span></dt><dt><span
class="section"><a href="#id976999">19.2. Installing and
Running ABRT</a></span></dt><dt><span
class="section"><a href="#abrt-plugins">19.3. ABRT
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a href="#analyzer-plugins">19.3.1. Analyzer
Plugins</a></span></dt><dt><span
class="section"><a href="#reporter-plugins">19.3.2. Reporter
Plugins</a></span></dt><dt><span
class="section"><a
href="#configuring-plugins-in-the-gui">19.3.3. Plugin Configuration in the
GUI</a></span></dt></dl></dd><dt><span
class="section"><a href="#generating-backtrace">19.4.
Generating
Backtraces</a></span></dt><dd><dl><dt><span
class="section"><a href="#troub
leshooting">19.4.1. Troubleshooting Backtrace
Generation</a></span></dt></dl></dd><dt><span
class="section"><a href="#id424708">19.5. Using the Command
Line Interface</a></span></dt><dd><dl><dt><span
class="section"><a href="#id424722">19.5.1. Viewing
Crashes</a></span></dt><dt><span
class="section"><a href="#id679552">19.5.2. Reporting
Crashes</a></span></dt><dt><span
class="section"><a href="#id568017">19.5.3. Deleting
Crashes</a></span></dt></dl></dd><dt><span
class="section"><a href="#configuring">19.6. Configuring
ABRT</a></span></dt><dt><span
class="section"><a
href="#configuring-centralized-crash-collection">19.7. Configuring
Centralized Crash
Collection</a></span></dt><dd><dl><dt><span
class="section"><a href="#id583691">19.7.1. Testing
ABRT's Crash Detection</a></span></dt><dt><span
class="section"><a href="#testing-upload-method">19.7.2.
Testing the Upload
Method</a></span></dt></dl></dd><dt><span
class="section"><a
href="#configuring-automatic-reporting">19.8. Con
figuring Automatic
Reporting</a></span></dt></dl></div><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="id1226654">19.1. Overview</h2></div></div></div><div
class="para">
+ <span
class="application"><strong>ABRT</strong></span> is the
<span class="application"><strong>Automatic Bug-Reporting
Tool</strong></span>. <span
class="application"><strong>ABRT</strong></span> consists
of a daemon that runs silently in the background most of the time. It springs into action
when an application crashes. It then collects the relevant crash data such as a core file
if there is one, the crashing application's command line parameters, and other
contextual puzzle pieces of forensic utility. Finally, <span
class="application"><strong>ABRT</strong></span> is capable
of reporting crash data to a relevant issue tracker, such as Red Hat Bugzilla. Reporting
crash data to a relevant issue tracker can be configured to happen automatically at every
detected crash, or crash dumps can be stored locally, reviewed, reported, and deleted
manually by a user. <span
class="application"><strong>ABRT</strong></span>'s
various plugins analyze crash data from applications writ
ten in the C, C++ and Python language, as well as report crashes to relevant issue
trackers.
+ </div><div class="para">
+ The <span
class="application"><strong>ABRT</strong></span> package
consists of:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">abrtd</code>, the system service
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="application"><strong>abrt-applet</strong></span>,
which runs in the user's Notification Area
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="application"><strong>abrt-gui</strong></span>, the
GUI application that shows collected crash dumps and allows you to edit, report, and
delete them
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="application"><strong>abrt-cli</strong></span>, the
command line interface with functionality similar to <span
class="application"><strong>abrt-gui</strong></span>.
+ </div></li></ul></div><div class="para">
+ You can open the <span
class="application"><strong>ABRT</strong></span> GUI
application by selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>Automatic Bug Reporting
Tool</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu.
+ </div><div class="figure"
id="fig-ABRT-Main_Window"><div
class="figure-contents"><div class="mediaobject"
align="center"><img src="images/abrt.png"
align="middle" alt="The Automatic Bug Reporting Tool main window"
/><div class="longdesc"><div class="para">
+ The Automatic Bug Reporting Tool main window
+ </div></div></div></div><h6>Figure 19.1. The Automatic
Bug Reporting Tool main window</h6></div><br class="figure-break"
/><div class="para">
+ A number of additional packages can be installed to provide <span
class="application"><strong>ABRT</strong></span> plugins
and addons. To view all the available <span
class="application"><strong>ABRT</strong></span> packages,
type the following command:
+ </div><pre class="screen"><code
class="command">yum list all | grep
abrt</code></pre></div><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="id976999">19.2. Installing and Running
ABRT</h2></div></div></div><div class="para">
+ By default, <span
class="application"><strong>ABRT</strong></span> should be
installed on your system, the <code class="systemitem">abrtd</code>
daemon configured to run at boot time, and <span
class="application"><strong>abrt-applet</strong></span> to
run in the Notification Area of your desktop session.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the ABRT
packages</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>ABRT</strong></span>, first
ensure the <code class="command">abrt-desktop</code> package is
installed on your system by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">yum install abrt-desktop</code></pre><div
class="para">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span> is
typically configured to start up at boot time. You can check that the <code
class="systemitem">abrtd</code> daemon is running by running the
following command, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl is-active
abrtd.service</code></pre><div class="para">
+ If you receive <code class="computeroutput">abrt is
stopped</code>, you can start the <code
class="systemitem">abrtd</code> service by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl start abrtd.service</code></pre><div
class="para">
+ You can ensure that the <code class="systemitem">abrtd</code>
service initializes at startup time by running the following command, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl enable
abrtd.service</code></pre><div class="para">
+ <span
class="application"><strong>ABRT</strong></span>'s
applet can be started by hand by running the <code
class="command">abrt-applet</code> program as a normal user when logged
into your desktop session, or by arranging for it to be started when the GUI session is
initialized.
+ </div><div class="figure"
id="fig-ABRT-Notification_Area_alarm_icon"><div
class="figure-contents"><div class="mediaobject"><img
src="images/abrt-alert.png" alt="The ABRT problem report" /><div
class="longdesc"><div class="para">
+ The ABRT problem report
+ </div></div></div></div><h6>Figure 19.2. The ABRT
problem report</h6></div><br class="figure-break" /><div
class="para">
+ When a crash is detected and saved, a broadcast <code
class="systemitem">D-Bus</code> message is sent about this crash. If
<code class="command">abrt-applet</code> is running, it receives
this message and displays an alarm icon in the Notification Area. You can open the GUI
application by clicking on this icon.
+ </div><div class="para">
+ Alternatively, you can open the <span
class="application"><strong>ABRT</strong></span> GUI
application by selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>Automatic Bug Reporting
Tool</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu.
+ </div></div><div class="section"
id="abrt-plugins"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="abrt-plugins">19.3. ABRT
Plugins</h2></div></div></div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span> offers a
variety of analyzer plugins and reporter plugins. These plugins are described in the
following two sections. Not all of the plugins mentioned in the following sections are
installed by default. To view all available plugins, run the following command:
+<pre class="screen"><code class="command">yum list all |
grep abrt-plugin-*</code></pre>
+
+ </div><div class="section"
id="analyzer-plugins"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="analyzer-plugins">19.3.1. Analyzer
Plugins</h3></div></div></div><div class="para">
+ These plugins serve as analyzers and crash information collectors for specific types
of crashes. For example, the <span
class="application"><strong>Kerneloops</strong></span>
analyzer plugin checks for crashes in the kernel only. These plugins can be
enabled/disabled from loading at start-up in their corresponding configuration files
placed in the <code class="filename">/etc/abrt/plugins/</code>
directory. The following is a list of all analyzer plugins.
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span
class="term">Kerneloops</span></dt><dd><div
class="para">
+ — Checks for crashes in the kernel and consequently collects kernel crash
information. It can be enabled/disabled from loading at start-up in the <code
class="filename">/etc/abrt/plugins/Kerneloops.conf</code> file.
+ </div></dd><dt class="varlistentry"><span
class="term">Python</span></dt><dd><div
class="para">
+ — Checks for crashes in Python programs and consequently collects the crash
information. It can be enabled/disabled from loading at start-up in the <code
class="filename">/etc/abrt/plugins/Python.conf</code> file.
+ </div></dd><dt class="varlistentry"><span
class="term">CCpp</span></dt><dd><div
class="para">
+ — Checks for crashes in C and C++ programs and consequently collects the crash
information. It can be enabled/disabled from loading at start-up in the <code
class="filename">/etc/abrt/plugins/CCpp.conf</code> file.
+ </div></dd></dl></div></div><div
class="section" id="reporter-plugins"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="reporter-plugins">19.3.2. Reporter
Plugins</h3></div></div></div><div class="para">
+ These plugins gather the crash data acquired by the analyzer plugins, combine the
data with any user input (such as comments about the crash, reproducibility, etc.), and
provide a specific output. Each of these plugins is configurable in its corresponding
configuration file placed in the <code
class="filename">/etc/abrt/plugins/</code> directory or in the <span
class="application"><strong>ABRT</strong></span> GUI
application (for more information on reporter plugin configuration in the <span
class="application"><strong>ABRT</strong></span> GUI
application, refer to <a class="xref"
href="#configuring-plugins-in-the-gui">Section 19.3.3, “Plugin Configuration
in the GUI”</a>).
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span
class="term">MailX</span></dt><dd><div
class="para">
+ — Sends a crash report via the <span
class="application"><strong>mailx</strong></span> utility
to a specified email address.
+ </div></dd><dt class="varlistentry"><span
class="term">Report Uploader</span></dt><dd><div
class="para">
+ — Uploads a tarball with crash data into a <code
class="systemitem">FTP</code>/<code
class="systemitem">SCP</code> server
+ </div></dd><dt class="varlistentry"><span
class="term">Bugzilla</span></dt><dd><div
class="para">
+ — Reports crashes into Bugzilla in the form of Bugzilla database entries.
+ </div></dd><dt class="varlistentry"><span
class="term">Logger</span></dt><dd><div
class="para">
+ — Creates a crash report and saves it to a specified local file.
+ </div></dd></dl></div></div><div
class="section" id="configuring-plugins-in-the-gui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="configuring-plugins-in-the-gui">19.3.3. Plugin Configuration in the
GUI</h3></div></div></div><div class="para">
+ You can override the system-wide plugin configuration in the <code
class="filename">/etc/abrt/plugins/*.conf</code> configuration files on
a per-user basis. Each of the plugins specified in section <a class="xref"
href="#reporter-plugins">Section 19.3.2, “Reporter Plugins”</a> can be
configured in the <span
class="application"><strong>ABRT</strong></span> GUI
application. Open the plugins window by clicking <span
class="guimenu"><strong>Edit</strong></span> → <span
class="guisubmenu"><strong>Event
configuration</strong></span>. This window shows a list of all installed
plugins. When you select one of the configurable plugins, you can click the <span
class="guibutton"><strong>Configure Event</strong></span>
button and you will be able to configure your desired plugin. If you change any of the
plugins' parameters, they are saved in the GNOME Keyring and will be used in the
future GUI sessions.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not store sensitive data in global
configuration files</h2></div><div class="admonition"><div
class="para">
+ All of the <code
class="filename">/etc/abrt/plugins/*.conf</code> configuration files
are world readable and are meant to be used as global settings. Thus, it is not advisable
to store usernames, passwords or any other sensitive data in them. The per-user settings
(set in the GUI application and readable by the owner of $HOME only) are stored in the
Gnome keyring or can be stored in a text file in <code
class="filename">$HOME/.abrt/*.conf</code> for use in <code
class="command">abrt-cli</code>.
+ </div></div></div><div class="figure"
id="mediaobj-abrt-plugins"><div
class="figure-contents"><div class="mediaobject"><img
src="images/abrt-event-configuration.png" alt="ABRT plugins"
/><div class="longdesc"><div class="para">
+ ABRT plugins
+ </div></div></div></div><h6>Figure 19.3. ABRT
plugins</h6></div><br class="figure-break" /><div
class="para">
+ The following is a list of all configuration options available for each configurable
plugin in the <span
class="application"><strong>ABRT</strong></span> GUI
application.
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span
class="term">MailX</span></dt><dd><div
class="para">
+ In the <span class="guilabel"><strong>MailX plugin
configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Subject</strong></span> — A string
that appears in the <code class="literal">Subject</code> field of a
crash report email sent by <span
class="application"><strong>mailx</strong></span> (by
default, set to <code class="literal">"[abrt] crash
report"</code>).
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Your
Email</strong></span> — A string that appears in the <code
class="literal">From</code> field of a crash report email.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Recipient's
Email</strong></span> — Email address of the recipient of a crash report
email.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Send Binary
Data</strong></span> option is checked, the crash report email will also
contain all binary files associated with the crash in an attachment. The core dump file is
also sent as an attachment.
+ </div></dd><dt class="varlistentry"><span
class="term">ReportUploader</span></dt><dd><div
class="para">
+ In the <span class="guilabel"><strong>ReportUploader plugin
configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Customer</strong></span> —
Specifies customer's identification.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Ticket</strong></span> — Specifies
the Ticket ID number in a specific issue tracker that collects crash reports.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>URL</strong></span> — Specifies
the URL of the issue tracker used to collect crash reports.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Retry
count</strong></span> — Specifies the number of retries should an upload
fail.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Retry
delay</strong></span> — Specifies the number or seconds between two retries.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Use
encryption</strong></span> option is checked, the crash report sent to the
issue tracker is encrypted.
+ </div><div class="para">
+ When the <span
class="guilabel"><strong>Upload</strong></span> option is
checked, all crash reports are uploaded to the specified issue tracker. If the option is
unchecked, all crash reports are saved locally.
+ </div></dd><dt class="varlistentry"><span
class="term">Bugzilla</span></dt><dd><div
class="para">
+ In the <span class="guilabel"><strong>Bugzilla plugin
configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Bugzilla
URL</strong></span> — Specifies the Bugzilla URL where crash dumps are sent
(by default, set to <a
href="https://bugzilla.redhat.com">https://bugzilla.redhat.com</a>).
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Login
(email)</strong></span> — User login which is used to log into Bugzilla and
create a Bugzilla database entry for a reported crash.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Password</strong></span> —
Password used to log into Bugzilla.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>SSL
verify</strong></span> option is checked, the <code
class="systemitem">SSL</code> protocol is used when sending the data
over the network.
+ </div></dd><dt class="varlistentry"><span
class="term">Logger</span></dt><dd><div
class="para">
+ In the <span class="guilabel"><strong>Logger plugin
configuration</strong></span>, you can configure the following parameter:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Logger
file</strong></span> — Specifies a file into which the crash reports are saved
(by default, set to <code
class="filename">/var/log/abrt.log</code>).
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Append new
logs</strong></span> option is checked, the Logger plugin will append new
crash reports to the log file specified in the <span
class="guilabel"><strong>Logger file</strong></span>
option. When unchecked, the new crash report always replaces the previous one.
+ </div></dd></dl></div></div></div><div
class="section" id="generating-backtrace"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="generating-backtrace">19.4. Generating
Backtraces</h2></div></div></div><div
class="para">
+ In order to analyze a reported crash, developers need as much detail about the crash
as possible. A <em class="firstterm">stack backtrace</em> is an
important source of information when a crash in a binary program (caught by the <code
class="command">CCpp</code> analyzer plugin) occurs.
+ </div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span> is
configured to generate a backtrace whenever a crash is reported through the <span
class="application"><strong>ABRT</strong></span> GUI
application or the <span
class="application"><strong>ABRT</strong></span> command
line interface.
+ </div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span> completes
the following steps to generate a backtrace:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It examines the core dump (which consists of the recorded contents of the memory of
an application at a specific time), which is saved in the crash dump directory. From this
file, <span
class="application"><strong>ABRT</strong></span> extracts
the information about the crashed binary program and information about every loaded
dynamic library.
+ </div></li><li class="listitem"><div
class="para">
+ It queries <span
class="application"><strong>Yum</strong></span> to
determine which <span class="package">debuginfo</span> packages
correspond to all the files extracted from the crash dump. This is the first potentially
slow operation. <span
class="application"><strong>Yum</strong></span> may need to
refresh the <em
class="parameter"><code>filelists</code></em> of various
repositories in order to find the correct package names. This process may take a few
minutes.
+ </div></li><li class="listitem"><div
class="para">
+ It downloads the needed <span class="package">debuginfo</span>
packages, and extracts and saves the <code
class="command">debuginfo</code> files. In order to speed up future
backtrace generation, <code class="command">debuginfo</code> files
are cached in the <code class="filename">/var/cache/abrt-di</code>
directory.
+ </div></li><li class="listitem"><div
class="para">
+ It generates a backtrace using <span
class="application"><strong>GDB</strong></span> (the GNU
Debugger) and saves it into the crash dump directory.
+ </div></li></ul></div><div class="para">
+ You can change the following backtrace generation parameters in the <code
class="filename">/etc/abrt/plugins/CCpp.conf</code> file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">Backtrace = <em
class="replaceable"><code>yes/no</code></em></code> —
Enables/Disables backtrace generation.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">BacktraceRemotes = <em
class="replaceable"><code>yes/no</code></em></code> —
For more information about this parameter, refer to <a class="xref"
href="#configuring-centralized-crash-collection">Section 19.7, “Configuring
Centralized Crash Collection”</a>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">InstallDebugInfo = <em
class="replaceable"><code>yes/no</code></em></code> —
Enables/Disables the installation of <span
class="package">debuginfo</span> packages (useful if your network is
not available or it is firewalled).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ReadonlyLocalDebugInfoDirs =
/path1:/path2:...</code> — Specifies the paths of local repositories (available, for
example, through a network mount) that contain pre-downloaded <span
class="package">debuginfo</span> packages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">DebugInfoCacheMB = <code
class="constant">4000</code></code> — Specifies the maximum size
of the cached <span class="package">debuginfo</span> packages in the
<code class="filename">/var/cache/abrt-di</code> directory.
+ </div></li></ul></div><div class="section"
id="troubleshooting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="troubleshooting">19.4.1. Troubleshooting Backtrace
Generation</h3></div></div></div><div
class="para">
+ In some cases, a long delay in the <span
class="application"><strong>ABRT</strong></span> GUI
application occurs after choosing a crash and pressing the <span
class="guibutton"><strong>Report</strong></span> button. In
this case, open the <span
class="guibutton"><strong>Details</strong></span> in the
<span class="guilabel"><strong>Generating
backtrace</strong></span> window and examine the messages.
+ </div><div class="para">
+ The following is a typical output seen in the <span
class="guilabel"><strong>Generating
backtrace</strong></span> window:
+ </div><pre class="screen">Starting the debuginfo installation
+Getting list of build IDs
+12 missing debuginfos, getting package list from cache
+12 missing debuginfos, getting package list from repositories
+Downloading 7 packages
+Download 1/7: acl-debuginfo-2.2.49-6.fc13.x86_64
+Unpacking: acl-debuginfo-2.2.49-6.fc13.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/3d/e20df1db609bd9313b1dc440796004f95911fd.debug
+Download 2/7: firefox-debuginfo-3.6.7-1.fc13.x86_64
+Unpacking: firefox-debuginfo-3.6.7-1.fc13.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/3d/b29c9308cb276431ce8854a2d88cf83518afc6.debug
+Caching debuginfo:
+usr/lib/debug/.build-id/a3/86884285365c8288e4e761ec034fafaa1daee1.debug
+⋮
+Download 7/7: zlib-debuginfo-1.2.3-23.fc12.x86_64
+Unpacking: zlib-debuginfo-1.2.3-23.fc12.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/f7/933750da80f555321576e72b375caf7a3cc075.debug
+All needed debuginfos are present
+Generating backtrace</pre><div class="para">
+ This process is performed by the <span
class="application"><strong>/usr/bin/abrt-debuginfo-install</strong></span>
shell script. This script uses a temporary directory (e.g. <code
class="filename">/var/run/abrt/tmp-29177-1283344373</code>) for its
operations. Normally, this directory is removed when <span
class="application"><strong>abrt-debuginfo-install</strong></span>
exits.
+ </div><div class="para">
+ If the <span class="package">debuginfo</span> installation
hangs, or is unable to download anything, you may debug the problem by editing the
<span
class="application"><strong>abrt-debuginfo-install</strong></span>
script. Change the following parameters:
+ </div><pre class="programlisting">debug=false
+keep_tmp=false</pre><div class="para">
+ at the top of the script to:
+ </div><pre class="programlisting">debug=true
+keep_tmp=true</pre><div class="para">
+ The first parameter instructs <span
class="application"><strong>abrt-debuginfo-install</strong></span>
to be verbose, the second parameter instructs <span
class="application"><strong>abrt-debuginfo-install</strong></span>
to not delete the <code
class="filename">/var/run/abrt/tmp-NNN-NNN</code> directory. You can
examine the log files in this directory, they may contain useful error messages.
+ </div><div class="para">
+ <span
class="application"><strong>abrt-debuginfo-install</strong></span>
uses <span
class="application"><strong>yum</strong></span> and
<span
class="application"><strong>yumdownloader</strong></span>
to handle the <span class="package">debuginfo</span> packages. In
order to quickly check that your <span
class="application"><strong>yum</strong></span>
configuration does not cause any problems which prevent <span
class="application"><strong>abrt-debuginfo-install</strong></span>
from working properly, change to the <code
class="filename">/tmp</code> directory and run the following commands,
as <code class="systemitem">root</code>:
+ </div><pre class="screen">tmp]# <code
class="command">yum --enablerepo=*debuginfo* --quiet provides
/usr/bin/true</code>
+tmp]# <code class="command">yumdownloader --enablerepo=*debuginfo*
--quiet coreutils</code></pre><div class="para">
+ Both of these commands should complete successfully, with no error messages. The
second command should download the <code
class="filename">coreutils-*.rpm</code> file. If any error messages
appear, check your <span
class="application"><strong>yum</strong></span>
configuration files in the <code
class="filename">/etc/yum.repos.d/*</code> directory and the <code
class="filename">/etc/yum/*</code> directory. If any of these commands
hang, check that you do not have another instance of <span
class="application"><strong>yum</strong></span> running,
and that your network connection is working properly.
+ </div></div></div><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="id424708">19.5. Using the Command Line
Interface</h2></div></div></div><div
class="para">
+ Crashes detected by <span
class="application"><strong>ABRT</strong></span> can be
viewed, reported, and deleted using the command line interface.
+ </div><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id424722">19.5.1. Viewing
Crashes</h3></div></div></div><div class="para">
+ To get a list of all crashes, simply enter <code
class="command">abrt-cli --list</code> or <code
class="command">abrt-cli -l</code>:
+ </div><pre class="screen">~]$ <code
class="command">abrt-cli --list</code>
+0.
+ UID : 500
+ UUID : 784b06666020e9f43718d99bf2649f19b4f251a9
+ Package : bash-4.1.2-3.el6
+ Executable : /bin/bash
+ Crash Time : Tue 20 Jul 2010 03:22:52 PM CEST
+ Crash Count: 2
+1.
+ UID : 500
+ UUID : 48007b98d65cca4530d99a564379e2609169239d
+ Package : coreutils-8.4-9.el6
+ Executable : /bin/sleep
+ Crash Time : Tue 20 Jul 2010 03:22:00 PM CEST
+ Crash Count: 1</pre><div class="para">
+ This output contains basic information for every crash. The <code
class="computeroutput">UID:</code> field shows the ID of the user which
ran the program that caused the crash. The <code
class="computeroutput">Package</code> field shows the name and version
of the Fedora package that contains the program, and the <code
class="computeroutput">Executable</code> field shows the location of
the binary or script that crashed. The <code class="computeroutput">Crash
Count</code> field indicates how many times the same crash happened.
+ </div></div><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id679552">19.5.2. Reporting
Crashes</h3></div></div></div><div class="para">
+ To report a certain crash, enter <code
class="command">abrt-cli --report <em
class="replaceable"><code>UUID</code></em></code> or
<code class="command">abrt-cli --r <em
class="replaceable"><code>UUID</code></em></code>,
where <code class="varname">UUID</code> is a Universally Unique
Identifier of a crash from the list of crashes; to view this list, execute the <code
class="command">abrt-cli --list</code> command. You do not need to
remember the exact <code class="varname">UUID</code>; either use a
mouse to copy and paste it, or enter a unique prefix and press <span
class="keycap"><strong>ENTER</strong></span>.
+ </div><pre class="screen">~]$ <code
class="command">abrt-cli --report 480</code>
+<span
class="keycap"><strong><ENTER></strong></span>
+>> Starting report creation...</pre><div
class="para">
+ <span
class="application"><strong>ABRT</strong></span> analyzes
the crash and creates a report about it. This might take a while. When the report is
ready, <code class="command">abrt-cli</code> opens a text editor
with the content of the report. You can see what is being reported, and you can fill in
instructions on how to reproduce the crash and other comments. You should also check the
backtrace, because the backtrace might be sent to a public server and viewed by anyone,
depending on the plugin settings.
+ </div><div class="note"><div
class="admonition_header"><h2>Selecting a preferred text
editor</h2></div><div class="admonition"><div
class="para">
+ You can choose which text editor is used to check the reports. <code
class="command">abrt-cli</code> uses the editor defined in the <code
class="envar">ABRT_EDITOR</code> environment variable. If the variable
is not defined, it checks the <code class="envar">VISUAL</code> and
<code class="envar">EDITOR</code> variables. If none of these
variables is set, <code class="command">vi</code> is used. You can
set the preferred editor in your <code
class="filename">.bashrc</code> configuration file. For example, if you
prefer GNU Emacs, add the following line to the file:
+ </div><pre class="programlisting">export <code
class="varname">VISUAL</code>=<strong
class="userinput"><code>emacs</code></strong></pre></div></div><div
class="para">
+ When you are done with the report, save your changes and close the editor. You will
be asked which of the enabled <span
class="application"><strong>ABRT</strong></span> plugins
you want to use to send the report. Respond <span
class="keycap"><strong>Y</strong></span> to send the report
using your desired plugin or <span
class="keycap"><strong>N</strong></span> to skip a plugin
you wish not to use.
+ </div></div><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id568017">19.5.3. Deleting
Crashes</h3></div></div></div><div class="para">
+ If you know that you do not want to report a certain crash dump, you can delete it
from the crash list. To delete a certain crash dump, enter the command: <code
class="command">abrt-cli --delete <em
class="replaceable"><code>UUID</code></em> </code>.
+ </div><div class="para">
+ Note that <span
class="application"><strong>ABRT</strong></span> performs a
detection of duplicate crashes by comparing new crashes with all locally saved crashes.
For a repeating crash, <span
class="application"><strong>ABRT</strong></span> requires
you to act upon it only once. However, if you delete the crash dump of that crash, the
next time this specific crash occurs, <span
class="application"><strong>ABRT</strong></span> will treat
it as a new crash: <span
class="application"><strong>ABRT</strong></span> will alert
you about it, prompt you to fill in a description, and report it. This can be redundant,
therefore, deleting a crash is not advisable.
+ </div></div></div><div class="section"
id="configuring"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="configuring">19.6. Configuring
ABRT</h2></div></div></div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span>'s main
configuration file is <code
class="filename">/etc/abrt/abrt.conf</code>. <span
class="application"><strong>ABRT</strong></span> plugins
can be configured through their configuration files, located in the <code
class="filename">/etc/abrt/plugins/</code> directory.
+ </div><div class="important"><div
class="admonition_header"><h2>Restart the abrtd daemon to apply the
changes</h2></div><div class="admonition"><div
class="para">
+ After changing and saving the <code
class="filename">/etc/abrt/abrt.conf</code> configuration file, you
must restart the <code class="systemitem">abrtd</code> daemon—as
<code class="systemitem">root</code>—for the new settings to take
effect:
+ </div><pre class="screen"><code
class="command">systemctl restart
abrtd.service</code></pre></div></div><div
class="para">
+ The following configuration directives are currently supported in <code
class="filename">/etc/abrt/abrt.conf</code>.
+ </div><div class="variablelist"><h6>[ Common ] Section
Directives</h6><dl><dt class="varlistentry"><span
class="term">OpenGPGCheck = <em
class="replaceable"><code>yes/no</code></em>
</span></dt><dd><div class="para">
+ Setting the <code class="computeroutput">OpenGPGCheck</code>
directive to <strong
class="userinput"><code>yes</code></strong> (the default
setting) tells <span
class="application"><strong>ABRT</strong></span> to
<span class="emphasis"><em>only</em></span> analyze and
handle crashes in applications provided by packages which are signed by the GPG keys whose
locations are listed in the <code
class="filename">/etc/abrt/gpg_keys</code> file. Setting <em
class="parameter"><code>OpenGPGCheck</code></em> to
<strong class="userinput"><code>no</code></strong> tells
<span class="application"><strong>ABRT</strong></span>
to catch crashes in all programs.
+ </div></dd><dt class="varlistentry"><span
class="term">BlackList = nspluginwrapper, valgrind, strace,
avant-window-navigator, [<span class="optional"><em
class="replaceable"><code>additional_packages</code></em>
</span>] </span></dt><dd><div class="para">
+ Crashes in packages and binaries listed after the <em
class="parameter"><code>BlackList</code></em> directive
will not be handled by <span
class="application"><strong>ABRT</strong></span>. If you
want <span
class="application"><strong>ABRT</strong></span> to ignore
other packages and binaries, list them here separated by commas.
+ </div></dd><dt class="varlistentry"><span
class="term">ProcessUnpackaged = <em
class="replaceable"><code>yes/no</code></em>
</span></dt><dd><div class="para">
+ This directive tells <span
class="application"><strong>ABRT</strong></span> whether to
process crashes in executables that do not belong to any package.
+ </div></dd><dt class="varlistentry"><span
class="term">BlackListedPaths = <code
class="filename">/usr/share/doc/*</code>, <code
class="filename">*/example*</code>
</span></dt><dd><div class="para">
+ Crashes in executables in these paths will be ignored by <span
class="application"><strong>ABRT</strong></span>.
+ </div></dd><dt class="varlistentry"><span
class="term">Database = SQLite3</span></dt><dd><div
class="para">
+ This directive instructs <span
class="application"><strong>ABRT</strong></span> to store
its crash data in the <span
class="application"><strong>SQLite3</strong></span>
database. Other databases are not currently supported. However, <span
class="application"><strong>ABRT</strong></span>'s
plugin architecture allows for future support for alternative databases.
+ </div></dd><dt class="varlistentry"><span
class="term">#WatchCrashdumpArchiveDir =
/var/spool/abrt-upload/</span></dt><dd><div
class="para">
+ This directive is commented out by default. Enable (uncomment) it if you want
<code class="systemitem">abrtd</code> to auto-unpack crashdump
tarballs which appear in the specified directory — in this case <code
class="filename">/var/spool/abrt-upload/</code> — (for example,
uploaded via <code class="systemitem">ftp</code>, <code
class="systemitem">scp</code>, etc.). You must ensure that whatever
directory you specify in this directive exists and is writable for <code
class="systemitem">abrtd</code>. <code
class="systemitem">abrtd</code> will not create it automatically.
+ </div></dd><dt class="varlistentry"><span
class="term">MaxCrashReportsSize = <em
class="replaceable"><code>size_in_megabytes</code></em>
</span></dt><dd><div class="para">
+ This option sets the amount of storage space, in megabytes, used by <span
class="application"><strong>ABRT</strong></span> to store
all crash information from all users. The default setting is <code
class="constant">1000</code> MB. Once the quota specified here has been
met, <span
class="application"><strong>ABRT</strong></span> will
continue catching crashes, and in order to make room for the new crash dumps, it will
delete the oldest and largest ones.
+ </div></dd><dt class="varlistentry"><span
class="term">ActionsAndReporters = SOSreport, [<span
class="optional"><em
class="replaceable"><code>additional_plugins</code></em>
</span>] </span></dt><dd><div class="para">
+ This option tells <span
class="application"><strong>ABRT</strong></span> to run the
specified plugin(s) immediately after a crash is detected and saved. For example, the
<strong
class="userinput"><code>SOSreport</code></strong> plugin
runs the <code class="systemitem">sosreport</code> tool which adds
the data collected by it to the created crash dump. You can turn this behavior off by
commenting out this line. For further fine-tuning, you can add <strong
class="userinput"><code>SOSreport</code></strong> (or any
other specified plugin) to either the <em
class="parameter"><code>CCpp</code></em> or <em
class="parameter"><code>Python</code></em> options to make
<span class="application"><strong>ABRT</strong></span>
run <code class="command">sosreport</code> (or any other specified
plugin) after any C and C++ or Python applications crash, respectively. For more
information on various Action and Reporter plugins, refer to <a class="xref"
href="#abrt-plugins">Section 19.3, �
�� ABRT Plugins”</a>
+ </div></dd></dl></div><div
class="variablelist"><h6>[ AnalyzerActionsAndReporters ] Section
Directives</h6><div class="para">
+ This section allows you to associate certain analyzer actions and reporter actions to
run when <span
class="application"><strong>ABRT</strong></span> catches
kernel oopses or crashes in C, C++ or Python programs. The actions and reporters specified
in any of the directives below will run only if you run <code
class="command">abrt-gui</code> or <code
class="command">abrt-cli</code> and report the crash that occurred. If
you do not specify any actions and reporters in these directives, you will not be able to
report a crash via <code class="command">abrt-gui</code> or <code
class="command">abrt-cli</code>. The order of actions and reporters is
important. Commenting out a directive, will cause <span
class="application"><strong>ABRT</strong></span> not to
catch the crashes associated with that directive. For example, commenting out the
Kerneloops line will cause <span
class="application"><strong>ABRT</strong></span> not to
catch kernel oopses.
+ </div><dl><dt class="varlistentry"><span
class="term">Kerneloops = Logger</span></dt><dd><div
class="para">
+ This directive specifies that, for kernel oopses, the Logger reporter will be run.
+ </div></dd><dt class="varlistentry"><span
class="term">CCpp = Logger</span></dt><dd><div
class="para">
+ This directive specifies that, when C or C++ program crashes occur, the Logger
reporter will be run.
+ </div></dd><dt class="varlistentry"><span
class="term">Python = Logger</span></dt><dd><div
class="para">
+ This directive specifies that, when Python program crashes occur, the Logger
reporter will be run.
+ </div></dd></dl></div><div class="para">
+ Each of these destinations' details can be specified in the corresponding <code
class="filename">plugins/*.conf</code> file. All these options can also
be configured through the <code class="command">abrt-gui</code>
application (for more information on plugin configuration refer to <a
class="xref" href="#abrt-plugins">Section 19.3, “ ABRT
Plugins”</a>).
+ </div><div class="variablelist"><h6>[ Cron ] Section
Directives</h6><dl><dt class="varlistentry"><span
class="term"> <em
class="replaceable"><code>time</code></em> = <em
class="replaceable"><code>action_to_run</code></em>
</span></dt><dd><div class="para">
+ The <code class="computeroutput">[ Cron ]</code> section of
<code class="filename">abrt.conf</code> allows you to specify the
exact time, or elapsed amount of time between, when <span
class="application"><strong>ABRT</strong></span> should run
a certain action, such as scanning for kernel oopses or performing file transfers. You can
list further actions to run by appending them to the end of this section.
+ </div><div class="example"
id="ex-_Cron__section_of__etc_abrt_abrt.conf"><h6>Example 19.1. [ Cron ]
section of /etc/abrt/abrt.conf</h6><div
class="example-contents"><pre class="programlisting"># Which
Action plugins to run repeatedly
+[ Cron ]
+# h:m - at h:m
+# s - every s seconds
+120 = KerneloopsScanner
+#02:00 = FileTransfer</pre></div></div><br
class="example-break" /><div class="para">
+ The format for an entry is either <strong
class="userinput"><code>time_in_seconds = <em
class="replaceable"><code>action_to_run</code></em>
</code></strong> or <strong
class="userinput"><code>hh:mm = action_to_run
</code></strong>, where <strong
class="userinput"><code>hh</code></strong> (hour) is in the
range <code class="constant">00-23</code> (all hours less than 10
should be zero-filled, i.e. preceded by a <code
class="constant">0</code>), and <strong
class="userinput"><code>mm</code></strong> (minute) is
<code class="constant">00-59</code>, zero-filled likewise.
+ </div></dd></dl></div></div><div
class="section"
id="configuring-centralized-crash-collection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="configuring-centralized-crash-collection">19.7. Configuring Centralized
Crash Collection</h2></div></div></div><div
class="para">
+ You can set up <span
class="application"><strong>ABRT</strong></span> so that
crash reports are collected from multiple systems and sent to a dedicated system for
further processing. This is useful when an administrator does not want to log into
hundreds of systems and manually check for crashes found by <span
class="application"><strong>ABRT</strong></span>. In order
to use this method, you need to install the <span
class="application"><strong>abrt-plugin-reportuploader</strong></span>
plugin (<code class="command">yum install
abrt-plugin-reportuploader</code>).
+ </div><div class="para">
+ The steps to configure <span
class="application"><strong>ABRT</strong></span>'s
centralized crash collection are:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ Complete the following steps on a dedicated system ("server system"):
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Create a directory to which you want the crash reports to be uploaded to. Usually,
<code class="filename">/var/spool/abrt-upload/</code> is used (the
rest of the document assumes you are using <code
class="filename">/var/spool/abrt-upload/</code>). Make sure this
directory is writable by the <code class="systemitem">abrt</code>
user.
+ </div><div class="note"><div
class="admonition_header"><h2>The abrt user and
group</h2></div><div class="admonition"><div
class="para">
+ When the <span class="package">abrt-desktop</span> package
is installed, it creates a new system user and a group, both named <code
class="systemitem">abrt</code>. This user is used by the <code
class="systemitem">abrtd</code> daemon for various things, for example,
as the owner:group of <code
class="filename">/var/spool/abrt/*</code> directories.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ In the <code class="filename">/etc/abrt/abrt.conf</code>
configuration file, set the <code
class="varname">WatchCrashdumpArchiveDir</code> directive to the
following:
+<pre class="programlisting">WatchCrashdumpArchiveDir =
/var/spool/abrt-upload/</pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ Determine your preferred upload mechanism; for example, <code
class="systemitem">FTP</code> or <code
class="systemitem">SCP</code>. For more information on how to configure
<code class="systemitem">FTP</code>, refer to <a
class="xref" href="#s1-FTP">Section 15.2, “FTP”</a>. For more
information on how to configure <code class="systemitem">SCP</code>,
refer to <a class="xref"
href="#s2-ssh-clients-scp">Section 9.3.2, “Using the <code
class="command">scp</code> Utility”</a>.
+ </div><div class="para">
+ For security reasons, make sure that uploads can only be performed by a specific
user and with a password. The rest of the document assumes that the username used for
uploads is <code class="systemitem">USERNAME</code> and the password
is <code class="literal">PASSWORD</code>. If you do not already have
a suitable username which can be used to perform uploads under, you may use the <code
class="systemitem">abrt</code> user which already exists on every
system where <span
class="application"><strong>ABRT</strong></span> is
installed.
+ </div><div class="para">
+ It is advisable to check whether your upload method works. For more information,
refer to <a class="xref"
href="#testing-upload-method">Section 19.7.2, “Testing the Upload
Method”</a>.
+ </div></li><li class="listitem"><div
class="para">
+ It is advisable to check and modify the following parameters if needed:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="parameter"><code>MaxCrashReportsSize</code></em>
directive (in <code class="filename">/etc/abrt/abrt.conf</code>)
needs to be set to a larger value if the expected volume of crash data is larger than the
default <code class="constant">1000</code> MB.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="parameter"><code>ProcessUnpackaged</code></em>
directive (in <code class="filename">/etc/abrt/abrt.conf</code>)
needs to be set to <em
class="replaceable"><code>yes</code></em> and the <em
class="parameter"><code>BacktraceRemotes</code></em> (in
<code class="filename">/etc/abrt/plugins/CCpp.conf</code>) needs to
be set to <em class="replaceable"><code>no</code></em>
if the client system and the server system have significantly different sets of installed
packages.
+ </div></li></ul></div></li></ul></div></li><li
class="listitem"><div class="para">
+ Complete the following steps on every client system which will use the central
management method:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Modify the <code
class="filename">/etc/abrt/plugins/ReportUploader.conf</code>
configuration file so that the <span
class="application"><strong>ReportUploader</strong></span>
plugin knows where to copy the saved crash reports in the following way:
+<pre class="programlisting">Enabled = yes
+Upload = yes
+URL = ftp://USERNAME:PASSWORD@SERVERNAME/var/spool/abrt-upload/</pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ To automatically send the crash reports to the server system immediately after the
crash occurs, is detected, and saved, set the <code
class="varname">[ ActionsAndReporters ]</code> directive in the
<code class="filename">/etc/abrt/abrt.conf</code> configuration file
to the following:
+<pre class="programlisting">ActionsAndReporters =
ReportUploader</pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ Alternatively, if user interaction is required before the crash dump is sent to
the server system, set the <em
class="parameter"><code>ReportUploader</code></em> to be a
reporter plugin for a specific crash type in the <code
class="literal">[ AnalyzerActionsAndReporters ]</code> section of the
<code class="filename">/etc/abrt/abrt.conf</code> configuration
file. The user will be required to run <span
class="application"><strong>abrt-cli</strong></span> or
<span
class="application"><strong>abrt-gui</strong></span> and
instruct the <code class="systemitem">abrtd</code> daemon to report
the crash and send it to the server system. For example, if you want all crash types to
use this method, edit the <code
class="literal">[ AnalyzerActionsAndReporters ]</code> section in your
<code class="filename">/etc/abrt/abrt.conf</code> configuration file
in the following way:
+ </div><pre class="programlisting">Kerneloops =
ReportUploader
+CCpp = ReportUploader
+Python =
ReportUploader</pre></li></ul></div></li></ol></div><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id583691">19.7.1. Testing ABRT's Crash
Detection</h3></div></div></div><div
class="para">
+ After completing all the steps of the configuration process, the basic setup is
finished. To test that this setup works properly use the <code
class="command">kill -s SEGV <em
class="replaceable"><code>PID</code></em> </code>
command to terminate a process on a client system. For example, start a <code
class="systemitem">sleep</code> process and terminate it with the
<code class="command">kill</code> command in the following way:
+<pre class="screen">~]$ <code class="command">sleep 100
&</code>
+[1] 2823
+~]$ <code class="command">kill -s SEGV 2823</code></pre>
+ <span
class="application"><strong>ABRT</strong></span> should
detect a crash shortly after executing the <code
class="command">kill</code> command. Check that the crash was detected
by <span
class="application"><strong>ABRT</strong></span> on the
client system (this can be checked by examining the appropriate syslog file, by running
the <code class="command">abrt-cli --list --full</code> command, or
by examining the crash dump created in the <code
class="filename">/var/spool/abrt</code> directory), copied to the
server system, unpacked on the server system and can be seen and acted upon using <code
class="command">abrt-cli</code> or <code
class="command">abrt-gui</code> on the server system.
+ </div></div><div class="section"
id="testing-upload-method"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="testing-upload-method">19.7.2. Testing the Upload
Method</h3></div></div></div><div class="para">
+ Test your upload method from a client system to ensure that it works. For example,
upload a file using the interactive <code
class="systemitem">FTP</code> client:
+ </div><pre class="screen">~]$ <code
class="command">ftp</code>
+ftp> open SERVERNAME
+Name: USERNAME
+Password: PASSWORD
+ftp> cd /var/spool/abrt-upload
+250 Operation successful
+ftp> put TESTFILE
+ftp> quit</pre><div class="para">
+ Check whether <code class="filename">TESTFILE</code> appeared
in the correct directory on the server system.
+ </div></div></div><div class="section"
id="configuring-automatic-reporting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="configuring-automatic-reporting">19.8. Configuring Automatic
Reporting</h2></div></div></div><div
class="para">
+ <span
class="application"><strong>ABRT</strong></span> can be
configured to automatically report any detected issues or crashes. The following steps
show how to enable this feature:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ In your <code class="filename">/etc/abrt/abrt.conf</code>
configuration file, for each analyzer, change the list of reporters according to your
needs, for example:
+ </div><pre class="programlisting">[ AnalyzerActionsAndReporters
]
+Kerneloops = Logger
+CCpp = Logger
+Python = Logger</pre></li><li class="listitem"><div
class="para">
+ In the configuration files corresponding to each analyzer plugin (that is, <code
class="filename">/etc/abrt/plugins/CCpp.conf</code>, <code
class="filename">/etc/abrt/plugins/Kerneloops.conf</code> and <code
class="filename">/etc/abrt/plugins/Python.conf</code>), add the
following line:
+ </div><pre class="programlisting">AutoReportUIDs = <em
class="replaceable"><code>USERNAME</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>USERNAME</code></em> represents a
user whose detected crashes and issues will be automatically reported via your specified
reporters. You can specify multiple users by separating them with a comma (<code
class="literal">,</code>).
+ </div></li></ol></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">Part VII. Kernel, Module and Driver
Configuration</h1></div></div></div><div
class="partintro" id="id805549"><div></div><div
class="para">
+ This part covers various tools that assist administrators with kernel customization.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a
href="#ch-Manually_Upgrading_the_Kernel">20. Manually Upgrading the
Kernel</a></span></dt><dd><dl><dt><span
class="section"><a href="#s1-kernel-packages">20.1. Overview
of Kernel Packages</a></span></dt><dt><span
class="section"><a href="#s1-kernel-preparing">20.2.
Preparing to Upgrade</a></span></dt><dt><span
class="section"><a href="#s1-kernel-download">20.3.
Downloading the Upgraded Kernel</a></span></dt><dt><span
class="section"><a href="#s1-kernel-perform-upgrade">20.4.
Performing the Upgrade</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_the_Initial_RAM_Disk_Image">20.5. Verifying the Initial
RAM Disk Image</a></span></dt><dt><span
class="section"><a href="#s1-kernel-boot-loader">20.6.
Verifying the Boot
Loader</a></span></dt><dd><dl><dt><span
class="section"><a href="#s3-kernel-boot-loader-grub">20.6.1.
Configuring the GRUB Boot Loader</a></span></dt><
dt><span class="section"><a
href="#s2-kernel-boot-loader-iseries">20.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-pseries">20.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">21.
Working with Kernel
Modules</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Listing_Currently-Loaded_Modules">21.1. Listing Currently-Loaded
Modules</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Information_About_a_Module">21.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="#sec-Loading_a_Module">21.3. Loading
a Module</a></span></dt><dt><span
class="section"><a href="#sec-Unloading_a_Module">21.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_Module_Parameters">21.5. Setting Module
Parameters</a></span></dt><dt><span class="sect
ion"><a href="#sec-Persistent_Module_Loading">21.6. Persistent
Module Loading</a></span></dt><dt><span
class="section"><a
href="#sec-Specific_Kernel_Module_Capabilities">21.7. Specific Kernel Module
Capabilities</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Using_Multiple_Ethernet_Cards">21.7.1. Using Multiple Ethernet
Cards</a></span></dt><dt><span
class="section"><a href="#sec-Using_Channel_Bonding">21.7.2.
Using Channel
Bonding</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-kernel-modules-additional-resources">21.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-kernel-modules-additional-resources-installed">21.8.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-modules-additional-resources-websites">21.8.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="#ch-kdump">22. The kdump Crash
Recovery Service</a></span></dt><dd><dl><dt
<span class="section"><a
href="#s1-kdump-configuration">22.1. Configuring the kdump
Service</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-kdump-configuration-gui">22.1.1.
Using the Kernel Dump Configuration
Utility</a></span></dt><dt><span
class="section"><a href="#s2-kdump-configuration-cli">22.1.2.
Configuring kdump on the Command Line</a></span></dt><dt><span
class="section"><a
href="#s2-kdump-configuration-testing">22.1.3. Testing the
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-kdump-crash">22.2. Analyzing the
Core Dump</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-kdump-crash-running">22.2.1.
Running the crash Utility</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-log">22.2.2.
Displaying the Message Buffer</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-backtrace">22.2.3.
Displaying a Backtrace</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-processe
s">22.2.4. Displaying a Process
Status</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-memory">22.2.5.
Displaying Virtual Memory Information</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-files">22.2.6.
Displaying Open Files</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-exit">22.2.7.
Exiting the
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-kdump-resources">22.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-kdump-resources-installed">22.3.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a href="#s2-kdump-resources-online">22.3.2.
Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></div></div><div
xml:lang="en-US" class="chapter"
id="ch-Manually_Upgrading_the_Kernel" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 20. Manually Upgrading the
Kernel</h2></div></div></div><div
class="toc"><dl><dt><span class="
section"><a href="#s1-kernel-packages">20.1. Overview of Kernel
Packages</a></span></dt><dt><span
class="section"><a href="#s1-kernel-preparing">20.2.
Preparing to Upgrade</a></span></dt><dt><span
class="section"><a href="#s1-kernel-download">20.3.
Downloading the Upgraded Kernel</a></span></dt><dt><span
class="section"><a href="#s1-kernel-perform-upgrade">20.4.
Performing the Upgrade</a></span></dt><dt><span
class="section"><a
href="#sec-Verifying_the_Initial_RAM_Disk_Image">20.5. Verifying the Initial
RAM Disk Image</a></span></dt><dt><span
class="section"><a href="#s1-kernel-boot-loader">20.6.
Verifying the Boot
Loader</a></span></dt><dd><dl><dt><span
class="section"><a href="#s3-kernel-boot-loader-grub">20.6.1.
Configuring the GRUB Boot Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-iseries">20.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-boot-loader-pseries">20.6.3. Configuring the
YABOOT Boot
Loader</a></span></dt></dl></dd></dl></div><a
id="id911529" class="indexterm"></a><a
id="id394674" class="indexterm"></a><a
id="id1012755" class="indexterm"></a><a
id="id627820" 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">
+ This chapter is therefore <span
class="emphasis"><em>only</em></span> useful for users who
need to manually update a kernel package using the <code
class="command">rpm</code> command instead of <code
class="command">yum</code>.
+ </div><a id="id857062" class="indexterm"></a><a
id="id482215" 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="id695621"
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">Section 4.1.2,
“Updating Packages”</a>.
+ </div><div class="section"
id="s1-kernel-packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kernel-packages">20.1. Overview of Kernel
Packages</h2></div></div></div><a id="id441656"
class="indexterm"></a><a id="id470794"
class="indexterm"></a><a id="id470810"
class="indexterm"></a><a id="id637333"
class="indexterm"></a><a id="id637349"
class="indexterm"></a><a id="id701753"
class="indexterm"></a><a id="id701769"
class="indexterm"></a><a id="id643098"
class="indexterm"></a><a id="id643114"
class="indexterm"></a><a id="id643130"
class="indexterm"></a><a id="id831921"
class="indexterm"></a><a id="id831937"
class="indexterm"></a><a id="id793840"
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"
id="s1-kernel-preparing">20.2. Preparing to
Upgrade</h2></div></div></div><a id="id417954"
class="indexterm"></a><a id="id611659"
class="indexterm"></a><a id="id611675"
class="indexterm"></a><a id="id611687"
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 2.6.38.6-27.fc15 installed
+kernel-doc.noarch 2.6.38.6-27.fc15 installed
+kernel-headers.x86_64 2.6.38.6-27.fc15 installed</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">Section 20.1, “Overview of
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"
id="s1-kernel-download">20.3. Downloading the Upgraded
Kernel</h2></div></div></div><a id="id585620"
class="indexterm"></a><a id="id585634"
class="indexterm"></a><a id="id585645"
class="indexterm"></a><a id="id566901"
class="indexterm"></a><div class="para">
+ There are several ways to determine if an updated kernel is available for the system.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Security Advisories — Refer to <a
href="http://fedoraproject.org/wiki/FSA">http://fedoraprojec...
for information on Security Advisories, including kernel upgrades that fix security
issues.
+ </div></li><li class="listitem"><div
class="para">
+ Via Fedora Update System — Download and install the kernel RPM packages. For more
information, refer to <a
href="http://admin.fedoraproject.org/updates/">http://admin....;.
+ </div></li></ul></div><div class="para">
+ To install the kernel manually, continue to <a class="xref"
href="#s1-kernel-perform-upgrade">Section 20.4, “Performing the
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"
id="s1-kernel-perform-upgrade">20.4. Performing the
Upgrade</h2></div></div></div><a id="id953051"
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">Section 20.5, “Verifying the
Initial RAM Disk Image”</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"
id="sec-Verifying_the_Initial_RAM_Disk_Image">20.5. Verifying the Initial RAM
Disk Image</h2></div></div></div><a id="id431041"
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 15 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">Section 20.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">
+ 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">grub.conf</code> configuration file by
following this procedure:
+ </div><div class="procedure"
id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>Procedure 20.1. Verifying
the Initial RAM Disk Image</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-2.6.38.6-26.fc15.x86_64
+config-2.6.38.6-27.fc15.x86_64
+efi
+elf-memtest86+-4.10
+grub
+initramfs-2.6.38.6-26.fc15.x86_64.img
+initramfs-2.6.38.6-27.fc15.x86_64.img
+lost+found
+memtest86+-4.10
+System.map-2.6.38.6-26.fc15.x86_64
+System.map-2.6.38.6-27.fc15.x86_64
+vmlinuz-2.6.38.6-26.fc15.x86_64
+vmlinuz-2.6.38.6-27.fc15.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-2.6.38.6-27.fc15.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-2.6.38.6-27.fc15.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>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">Chapter 22, <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-2.6.38.6-26.fc15.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>:
+ </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-2.6.38.6-26.fc15.x86_64.img</code>
+/boot/initramfs-2.6.38.6-26.fc15.x86_64.img:
+========================================================================
+dracut-009-10.fc15
+========================================================================
+drwxr-xr-x 23 root root 0 May 20 14:45 .
+drwxr-xr-x 2 root root 0 May 20 14:45 bin
+-rwxr-xr-x 1 root root 38400 Feb 8 12:46 bin/rmdir
+-rwxr-xr-x 1 root root 116632 Feb 8 12:46 bin/ls
+-rwxr-xr-x 1 root root 39568 Feb 8 03:27 bin/setfont
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</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">grub.conf</code>
configuration file in the <code class="filename">/boot/grub/</code>
directory to ensure that an <code class="computeroutput">initrd <code
class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code></code>
exists for the kernel version you are booting. Refer to <a class="xref"
href="#s1-kernel-boot-loader">Section 20.6, “Verifying the Boot
Loader”</a> for more information.
+ </div></li></ol></div><h3>Verifying the Initial RAM
Disk Image and Kernel on IBM eServer System i</h3><a id="id738964"
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, use the command <code
class="command">ls -l /boot/</code> to make sure the <code
class="filename">/boot/vmlinitrd-<em
class="replaceable"><code>kernel_version</code></em></code>
file already exists (the <code class="filename"><em
class="replaceable"><code>kernel_version</code></em></code>
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"
id="s1-kernel-boot-loader">20.6. Verifying the Boot
Loader</h2></div></div></div><a id="id556467"
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>Table 20.1. Boot loaders by
architecture</h6><div class="table-contents"><table
summary="Boot loaders by architecture"
border="1"><colgroup><col class="architecture"
width="33%" /><col class="bootloader" width="33%"
/><col class="refer-to" width="33%"
/></colgroup><thead><tr><th>
+ Architecture
+ </th><th>
+ Boot Loader
+ </th><th>
+ Refer to
+ </th></tr></thead><tbody><tr><td>
+ x86
+ </td><td>
+ GRUB
+ </td><td>
+ <a class="xref"
href="#s3-kernel-boot-loader-grub">Section 20.6.1, “Configuring the GRUB Boot
Loader”</a>
+ </td></tr><tr><td>
+ AMD AMD64 <span
class="emphasis"><em>or</em></span> Intel 64
+ </td><td>
+ GRUB
+ </td><td>
+ <a class="xref"
href="#s3-kernel-boot-loader-grub">Section 20.6.1, “Configuring the GRUB Boot
Loader”</a>
+ </td></tr><tr><td>
+ IBM eServer System i
+ </td><td>
+ OS/400
+ </td><td>
+ <a class="xref"
href="#s2-kernel-boot-loader-iseries">Section 20.6.2, “Configuring the OS/400
Boot Loader”</a>
+ </td></tr><tr><td>
+ IBM eServer System p
+ </td><td>
+ YABOOT
+ </td><td>
+ <a class="xref"
href="#s2-kernel-boot-loader-pseries">Section 20.6.3, “Configuring the YABOOT
Boot Loader”</a>
+ </td></tr><tr><td>
+ IBM System z
+ </td><td>
+ z/IPL
+ </td><td>
+ </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"
id="s3-kernel-boot-loader-grub">20.6.1. Configuring the GRUB Boot
Loader</h3></div></div></div><a id="id691766"
class="indexterm"></a><a id="id691778"
class="indexterm"></a><div class="para">
+ GRUB's configuration file, <code
class="filename">/boot/grub/grub.conf</code>, contains a few lines with
directives, such as <code class="computeroutput">default</code>,
<code class="computeroutput">timeout</code>, <code
class="computeroutput">splashimage</code> and <code
class="computeroutput">hiddenmenu</code> (the last directive has no
argument). The remainder of the file contains 4-line <em
class="firstterm">stanzas</em> that each refer to an installed kernel.
These stanzas always start with a <code
class="computeroutput">title</code> entry, after which the associated
<code class="computeroutput">root</code>, <code
class="computeroutput">kernel</code> and <code
class="computeroutput">initrd</code> directives should always be
indented. Ensure that each stanza starts with a <code
class="computeroutput">title</code> that contains a version number (in
parentheses) that matches the version number in the <code
class="computeroutput">kernel /vmlinuz-<em
class="replaceable">
<code>version_number</code></em></code> line of the same stanza.
+ </div><div class="example"
id="ex-_boot_grub_grub.conf"><h6>Example 20.1. /boot/grub/grub.conf</h6><div
class="example-contents"><pre class="programlisting">#
grub.conf generated by anaconda
+<em class="lineannotation"><span
class="lineannotation">[comments omitted]</span></em>
+default=1
+timeout=0
+splashimage=(hd0,0)/boot/grub/splash.xpm.gz
+hiddenmenu
+
+title Fedora (2.6.38.6-27.fc15.x86_64)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.38.6-27.fc15.x86_64 ro
root=UUID=e8148266-4a56-4f4d-b6df-9eafea4586b2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM
LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
+ initrd /boot/initramfs-2.6.38.6-27.fc15.x86_64.img
+title Fedora (2.6.38.6-26.rc1.fc15.x86_64)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.38.6-26.fc15.x86_64 ro
root=UUID=e8148266-4a56-4f4d-b6df-9eafea4586b2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM
LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
+ initrd
/boot/initramfs-2.6.38.6-26.fc15.x86_64.img</pre></div></div><br
class="example-break" /><div class="para">
+ 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>. This is the case in <a
class="xref" href="#ex-_boot_grub_grub.conf">Example 20.1,
“/boot/grub/grub.conf”</a>, therefore the <code
class="computeroutput">initrd <code
class="filename">/initramfs-2.6.38.6-27.fc15.x86_64.img</code></code>
line in the first kernel stanza means that the <code
class="systemitem">initramfs</code> image is actually located at
<code
class="filename">/boot/initramfs-2.6.38.6-27.fc15.x86_64.img</code>
when the root file system is mounted, and likewise for the kernel path (for example:
<code class="computeroutput">kernel <code
class="filename">/vmlinuz-2.6.38.6-27.fc15.x86_64</code></code>)
in each stanza of <code class="filename">grub.conf</code>.
+ </div><div class="note"
id="note-The_initrd_directive_in_grub.conf_refers_to_an_initramfs_image"><div
class="admonition_header"><h2>The initrd directive in grub.conf refers
to an initramfs image</h2></div><div
class="admonition"><div class="para">
+ In kernel boot stanzas in <code
class="filename">grub.conf</code>, 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 <span
class="emphasis"><em><code
class="filename">initramfs</code> </em></span> file
corresponding to the same kernel version. This directive is called <code
class="computeroutput">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. Thus the <code
class="filename">grub.conf</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_ver
sion</code></em>.img</code>
+ </div><div class="para">
+ <span
class="application"><strong>Dracut</strong></span> is a new
utility available in Fedora 15, and much-improved over <code
class="command">mkinitrd</code>. For information on using <span
class="application"><strong>Dracut</strong></span>, refer
to <a class="xref"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">Section 20.5, “Verifying the
Initial RAM Disk Image”</a>.
+ </div></div></div><div class="para">
+ You should ensure that the kernel version number as given on the <code
class="computeroutput">kernel <code
class="filename">/vmlinuz-<em
class="replaceable"><code>kernel_version</code></em></code></code>
line matches the version number of the <code
class="systemitem">initramfs</code> image given on the <code
class="computeroutput">initrd <code
class="filename">/initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code></code>
line of each stanza. Refer to <a class="xref"
href="#procedure-Verifying_the_Initial_RAM_Disk_Image">Procedure 20.1,
“Verifying the Initial RAM Disk Image”</a> for more information.
+ </div><div class="para">
+ The <code class="computeroutput">default=</code> directive
tells GRUB which kernel to boot <span class="emphasis"><em>by
default</em></span>. Each <code
class="computeroutput">title</code> in <code
class="filename">grub.conf</code> represents a bootable kernel. GRUB
counts the <code class="computeroutput">title</code>d stanzas
representing bootable kernels starting with <code
class="constant">0</code>. In <a class="xref"
href="#ex-_boot_grub_grub.conf">Example 20.1,
“/boot/grub/grub.conf”</a>, the line <code
class="computeroutput">default=1</code> indicates that GRUB will boot,
by default, the <span
class="emphasis"><em>second</em></span> kernel entry, i.e.
<code class="computeroutput">title Fedora
(2.6.38.6-26.fc15.x86_64)</code>.
+ </div><div class="para">
+ In <a class="xref"
href="#ex-_boot_grub_grub.conf">Example 20.1,
“/boot/grub/grub.conf”</a> GRUB is therefore configured to boot an older kernel,
when we compare by version numbers. In order to boot the newer kernel, which is the
<span class="emphasis"><em>first</em></span> <code
class="computeroutput">title</code> entry in <code
class="filename">grub.conf</code>, we would need to change the <code
class="computeroutput">default</code> value to <code
class="constant">0</code>.
+ </div><div class="para">
+ After installing a new kernel with <code
class="command">rpm</code>, verify that <code
class="filename">/boot/grub/grub.conf</code> is correct, change the
<code class="computeroutput">default=</code> value to the new kernel
(while remembering to count from <code class="constant">0</code>),
and reboot the computer into the new kernel. Ensure your hardware is detected by watching
the boot process output.
+ </div><div class="para">
+ If GRUB presents an error and is unable to boot into the default kernel, it is often
easiest to try to boot into an alternative or older kernel so that you can fix the
problem.
+ </div><div class="important"><div
class="admonition_header"><h2>Causing the GRUB boot menu to
display</h2></div><div class="admonition"><div
class="para">
+ If you set the <code class="computeroutput">timeout</code>
directive in <code class="filename">grub.conf</code> to <code
class="constant">0</code>, GRUB 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 will present you with the GRUB menu.
+ </div></div></div><div class="para">
+ Alternatively, use the boot media you created earlier to boot the system.
+ </div></div><div class="section"
id="s2-kernel-boot-loader-iseries"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-kernel-boot-loader-iseries">20.6.2. Configuring the OS/400 Boot
Loader</h3></div></div></div><a id="id593148"
class="indexterm"></a><a id="id593160"
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">
+ Begin testing the new kernel by rebooting the computer and watching the messages to
ensure that the hardware is detected properly.
+ </div></div><div class="section"
id="s2-kernel-boot-loader-pseries"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-kernel-boot-loader-pseries">20.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">
+ Begin testing the new kernel by rebooting the computer and watching the messages to
ensure that the hardware is detected properly.
+ </div></div></div></div><div xml:lang="en-US"
class="chapter" id="ch-Working_with_Kernel_Modules"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 21. Working with Kernel
Modules</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#sec-Listing_Currently-Loaded_Modules">21.1. Listing Currently-Loaded
Modules</a></span></dt><dt><span
class="section"><a
href="#sec-Displaying_Information_About_a_Module">21.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="#sec-Loading_a_Module">21.3. Loading
a Module</a></span></dt><dt><span
class="section"><a href="#sec-Unloading_a_Module">21.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="#sec-Setting_Module_Parameters">21.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="#sec-Persistent_Module_Loading">21.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a href="#sec-Specific_
Kernel_Module_Capabilities">21.7. Specific Kernel Module
Capabilities</a></span></dt><dd><dl><dt><span
class="section"><a
href="#sec-Using_Multiple_Ethernet_Cards">21.7.1. Using Multiple Ethernet
Cards</a></span></dt><dt><span
class="section"><a href="#sec-Using_Channel_Bonding">21.7.2.
Using Channel
Bonding</a></span></dt></dl></dd><dt><span
class="section"><a
href="#s1-kernel-modules-additional-resources">21.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-kernel-modules-additional-resources-installed">21.8.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="#s2-kernel-modules-additional-resources-websites">21.8.2. Useful
Websites</a></span></dt></dl></dd></dl></div><a
id="id621823" class="indexterm"></a><a
id="id894745" class="indexterm"></a><a
id="id391196" 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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="section"
id="sec-Listing_Currently-Loaded_Modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-Listing_Currently-Loaded_Modules">21.1. Listing Currently-Loaded
Modules</h2></div></div></div><a id="id1061873"
class="indexterm"></a><a id="id840749"
class="indexterm"></a><a id="id840769"
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">[output
truncated]</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">Section 21.4, “Unloading a Module”</a>.
+ </div></li></ul></div><a id="id981582"
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"
id="sec-Displaying_Information_About_a_Module">21.2. Displaying Information
About a Module</h2></div></div></div><a id="id484188"
class="indexterm"></a><a id="id484204"
class="indexterm"></a><a id="id832011"
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>Example 21.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, &lt;linux.nics(a)intel.com&gt;
+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><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>Example 21.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"
id="sec-Loading_a_Module">21.3. Loading a
Module</h2></div></div></div><a id="id793754"
class="indexterm"></a><a id="id833045"
class="indexterm"></a><a id="id833065"
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="id437958"
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>Example 21.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="id817146" class="indexterm"></a><a
id="id568358" 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"
id="sec-Unloading_a_Module">21.4. Unloading a
Module</h2></div></div></div><a id="id666418"
class="indexterm"></a><a id="id666430"
class="indexterm"></a><a id="id666450"
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">Section 21.1, “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>Example 21.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="id1306780" class="indexterm"></a><a
id="id1306800" 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"
id="sec-Setting_Module_Parameters">21.5. Setting Module
Parameters</h2></div></div></div><a id="id1305244"
class="indexterm"></a><a id="id1305256"
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">Section 21.6, “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>Procedure 21.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">Section 21.4, “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<sup>[<a
id="footnote-Energy_Efficient_Ethernet"
href="#ftn.footnote-Energy_Efficient_Ethernet"
class="footnote">3</a>]</sup> , 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"
id="sec-Persistent_Module_Loading">21.6. Persistent Module
Loading</h2></div></div></div><a id="id806813"
class="indexterm"></a><a id="id806829"
class="indexterm"></a><div class="para">
+ As shown in <a class="xref"
href="#ex-Listing_information_about_a_kernel_module_with_lsmod">Example 21.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>Example 21.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"
id="sec-Specific_Kernel_Module_Capabilities">21.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"
id="sec-Using_Multiple_Ethernet_Cards">21.7.1. Using Multiple Ethernet
Cards</h3></div></div></div><a id="id476991"
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&qu...;.
+ </div></div><div class="section"
id="sec-Using_Channel_Bonding"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Using_Channel_Bonding">21.7.2. Using Channel
Bonding</h3></div></div></div><a id="id620801"
class="indexterm"></a><a id="id620817"
class="indexterm"></a><a id="id620829"
class="indexterm"></a><a id="id620841"
class="indexterm"></a><a id="id691714"
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="id691739"
class="indexterm"></a><a id="id691751"
class="indexterm"></a><div class="para">
+ To channel bond multiple network interfaces, the administrator must perform the
following steps:
+ </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">Section 6.2.2, “Channel Bonding
Interfaces”</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">Section 21.7.2.1, “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"
id="s3-modules-bonding-directives">21.7.2.1. Bonding Module
Directives</h4></div></div></div><a id="id1228654"
class="indexterm"></a><a id="id1228669"
class="indexterm"></a><a id="id528863"
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">Section 6.2.2, “Channel Bonding
Interfaces”</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">[output truncated]</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">Section 6.2.2, “Channel Bonding
Interfaces”</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">Section 21.8, “Additional
Resources”</a>).
+ </div><div class="variablelist"><h6>Bonding Interface
Parameters</h6><dl><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>Note</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"
id="s1-kernel-modules-additional-resources">21.8. Additional
Resources</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"
id="s2-kernel-modules-additional-resources-installed">21.8.1. Installed
Documentation</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><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><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"
id="s2-kernel-modules-additional-resources-websites">21.8.2. Useful
Websites</h3></div></div></div><div
class="variablelist"><dl><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 class="footnote"
id="footnote-Energy_Efficient_Ethernet"><div
class="para"><sup>[<a
id="ftn.footnote-Energy_Efficient_Ethernet"
href="#footnote-Energy_Efficient_Ethernet"
class="para">3</a>] </sup>
+ 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="en-US"
class="chapter" id="ch-kdump" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 22. The kdump Crash Recovery
Service</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="#s1-kdump-configuration">22.1. Configuring the kdump
Service</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-kdump-configuration-gui">22.1.1.
Using the Kernel Dump Configuration
Utility</a></span></dt><dt><span
class="section"><a href="#s2-kdump-configuration-cli">22.1.2.
Configuring kdump on the Command Line</a></span></dt><dt><span
class="section"><a
href="#s2-kdump-configuration-testing">22.1.3. Testing the
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-kdump-crash">22.2. Analyzing the
Core Dump</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-kdump-crash-running">22.2.1.
Running the crash Utility</a></span></dt><dt><span
class="section"><a href="#s2
-kdump-crash-log">22.2.2. Displaying the Message
Buffer</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-backtrace">22.2.3.
Displaying a Backtrace</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-processes">22.2.4.
Displaying a Process Status</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-memory">22.2.5.
Displaying Virtual Memory Information</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-files">22.2.6.
Displaying Open Files</a></span></dt><dt><span
class="section"><a href="#s2-kdump-crash-exit">22.2.7.
Exiting the
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="#s1-kdump-resources">22.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="#s2-kdump-resources-installed">22.3.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a href="#s2-kdump-resources-online">22.3.2.
Useful
Websites</a></span></dt></dl></dd></dl></div><div
class="para">
+ <code class="systemitem">kdump</code> is an advanced crash
dumping mechanism. When 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. Since being able to analyze the core dump
helps significantly to determine the exact cause of the system failure, it is strongly
recommended to have this feature enabled.
+ </div><div class="para">
+ 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-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kdump-configuration">22.1. Configuring the kdump
Service</h2></div></div></div><div class="para">
+ This section covers two common means of configuring the <code
class="systemitem">kdump</code> service: using the <span
class="application"><strong>Kernel Dump
Configuration</strong></span> graphical utility, and doing so manually on the
command line. It also describes how to test the configuration to verify that everything
works as expected.
+ </div><a id="id1065295"
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="note"><div
class="admonition_header"><h2>Make sure you have relevant packages
installed</h2></div><div class="admonition"><div
class="para">
+ To use the <code class="systemitem">kdump</code> service, you
must have the <span class="package">kexec-tools</span> and <span
class="package">system-config-kdump</span> 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 kexec-tools
system-config-kdump</code></pre><div class="para">
+ For more information on how to install new packages in Fedora, refer to <a
class="xref" href="#sec-Installing">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="section"
id="s2-kdump-configuration-gui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-kdump-configuration-gui">22.1.1. Using the Kernel Dump Configuration
Utility</h3></div></div></div><a id="id439681"
class="indexterm"></a><a id="id794641"
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">Figure 22.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, the utility will not start, and you will be
presented with the following error message:
+ </div><div class="mediaobject" align="center"><img
src="images/kdump-kernel_dump_configuration-not_enough_memory.png"
align="middle" /><div class="longdesc"><div
class="para">
+ The <span class="quote">“<span class="quote">not
enough memory</span>”</span> error
+ </div></div></div><div class="para">
+ For the information on minimum memory requirements, refer to the <em
class="citetitle">Hardware Overview</em> section of the <a
href="http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Not...
class="citetitle">Fedora 15 Release Notes</em></a>. Note that
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 a user, and defaults to 128MB.
+ </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"
id="s3-kdump-configuration-gui-enable">22.1.1.1. Enabling the
Service</h4></div></div></div><a id="id1454624"
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 for runlevels <code
class="literal">2</code>, <code
class="literal">3</code>, <code
class="literal">4</code>, and <code
class="literal">5</code>, and start it for the current session.
Similarly, clicking the <span
class="guibutton"><strong>Disable</strong></span> button
will disable it for all runlevels and stop the service immediately.
+ </div><div class="para">
+ For more information on runlevels and configuring services in general, refer to
<a class="xref" href="#ch-Services_and_Daemons">Chapter 7,
<em>Services and Daemons</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"
id="s3-kdump-configuration-gui-basic">22.1.1.2. The Basic Settings
Tab</h4></div></div></div><a id="id408020"
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>Figure 22.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"
id="s3-kdump-configuration-gui-target">22.1.1.3. The Target Settings
Tab</h4></div></div></div><a id="id480318"
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>Figure 22.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">Chapter 9, <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="id666335"
class="indexterm"></a><div class="para">
+ For a complete list of currently supported targets, see <a class="xref"
href="#tab-kdump-supported_targets">Table 22.1, “Supported kdump
targets”</a>.
+ </div><div class="table"
id="tab-kdump-supported_targets"><h6>Table 22.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>
+ Type
+ </th><th>
+ Supported Targets
+ </th><th>
+ Unsupported Targets
+ </th></tr></thead><tbody><tr><td
valign="middle">
+ Raw device
+ </td><td>
+ All locally attached raw disks and partitions.
+ </td><td>
+ —
+ </td></tr><tr><td valign="middle">
+ Local file system
+ </td><td>
+ <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>
+ The <code class="systemitem">eCryptfs</code> file system.
+ </td></tr><tr><td rowspan="7"
valign="middle">
+ Remote directory
+ </td><td>
+ 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>
+ Remote directories on the <code
class="systemitem">rootfs</code> file system accessed using the
<code class="systemitem">NFS</code> protocol.
+ </td></tr><tr><td>
+ Remote directories accessed using the <code
class="systemitem">iSCSI</code> protocol over hardware initiators.
+ </td><td>
+ Remote directories accessed using the <code
class="systemitem">iSCSI</code> protocol over software initiators.
+ </td></tr><tr><td rowspan="5">
+ —
+ </td><td>
+ Remote directories accessed over <code
class="systemitem">IPv6</code>.
+ </td></tr><tr><td>
+ Remote directories accessed using the <code
class="systemitem">SMB</code>/<code
class="systemitem">CIFS</code> protocol.
+ </td></tr><tr><td>
+ Remote directories accessed using the <code
class="systemitem">FCoE</code> (<em
class="firstterm">Fibre Channel over Ethernet</em>) protocol.
+ </td></tr><tr><td>
+ Remote directories accessed using wireless network interfaces.
+ </td></tr><tr><td>
+ Multipath-based storages.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="id842265"
class="indexterm"></a><div class="important"><div
class="admonition_header"><h2>Using the hpsa driver for a
storage</h2></div><div class="admonition"><div
class="para">
+ Due to known issue with the <code
class="systemitem">hpsa</code> driver, <code
class="systemitem">kdump</code> is unable to save the dump to a storage
that uses this driver for HP Smart Array Controllers. If this applies to your machine, it
is advised that you save the dump to a remote system using the NFS or SSH protocol
instead.
+ </div></div></div></div><div class="section"
id="s3-kdump-configuration-gui-filtering"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-kdump-configuration-gui-filtering">22.1.1.4. The Filtering Settings
Tab</h4></div></div></div><a id="id481293"
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>Figure 22.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 check box 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"
id="s3-kdump-configuration-gui-expert">22.1.1.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>Figure 22.4. Expert
Settings</h6></div><br class="figure-break" /><a
id="id853234" 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="id424604"
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="id424632"
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="id390059"
class="indexterm"></a><div class="para">
+ To choose what steps should be taken when the kernel crash is captured, select the
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="id1062548"
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">Section 22.1.2.3, “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"
id="s2-kdump-configuration-cli">22.1.2. Configuring kdump on the Command
Line</h3></div></div></div><div class="para">
+ To perform actions described in this section, you have to be logged in as <code
class="systemitem">root</code>. To do so, run the following command:
+ </div><pre class="screen"><code
class="command">su -</code></pre><div
class="section" id="s3-kdump-configuration-cli-memory"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-kdump-configuration-cli-memory">22.1.2.1. Configuring the Memory
Usage</h4></div></div></div><a id="id901222"
class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code
class="systemitem">kdump</code> kernel, open the <code
class="filename">/boot/grub/grub.conf</code> file in a text editor such
as <span class="application"><strong>vi</strong></span>
or <span
class="application"><strong>nano</strong></span>, and add
the <code class="option">crashkernel=<em
class="replaceable"><code><size></code></em>M</code>
parameter to the list of kernel options as shown in <a class="xref"
href="#ex-kdump-configuration-cli-memory-grub">Example 22.1, “A sample
/boot/grub/grub.conf file”</a>.
+ </div><a id="id379025"
class="indexterm"></a><a id="id423672"
class="indexterm"></a><a id="id423692"
class="indexterm"></a><div class="example"
id="ex-kdump-configuration-cli-memory-grub"><h6>Example 22.1. A sample
/boot/grub/grub.conf file</h6><div class="example-contents"><pre
class="screen"># grub.conf generated by anaconda
+#
+# Note that you do not have to rerun grub after making changes to this file
+# NOTICE: You have a /boot partition. This means that
+# all kernel and initrd paths are relative to /boot/, eg.
+# root (hd0,0)
+# kernel /vmlinuz-version ro root=/dev/sda3
+# initrd /initrd
+#boot=/dev/sda
+default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux (2.6.32-54.el6.i686)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.32-54.el6.i686 root=/dev/sda3 ro crashkernel=128M
+ initrd /initramfs-2.6.32-54.el6.i686.img
+</pre></div></div><br class="example-break" /><div
class="important"><div
class="admonition_header"><h2>Make sure the system has enough
memory</h2></div><div class="admonition"><div
class="para">
+ 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 a user, and defaults to 128 MB, as lower values proved to
be unreliable. For the information on minimum memory requirements, refer to the <em
class="citetitle">Hardware Overview</em> section of the <a
href="http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Not...
class="citetitle">Fedora 15 Release Notes</em></a>.
+ </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"
id="s3-kdump-configuration-cli-target">22.1.2.2. Configuring the Target
Type</h4></div></div></div><a id="id933613"
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. Note that only one of these options
can be set at the moment. 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, open the <code
class="filename">/etc/kdump.conf</code> configuration file in a text
editor such as <span
class="application"><strong>vi</strong></span> or <span
class="application"><strong>nano</strong></span>, and 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="screen">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="screen">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="screen">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(a)my.server.com</code> line, and
replace the value with a valid username and hostname. For example:
+ </div><pre class="screen">net
john(a)penguin.example.com</pre><div class="para">
+ Refer to <a class="xref" href="#ch-OpenSSH">Chapter 9,
<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="id647615"
class="indexterm"></a><div class="para">
+ For a complete list of currently supported targets, see <a class="xref"
href="#tab-kdump-supported_targets">Table 22.1, “Supported kdump
targets”</a>.
+ </div><a id="id647644"
class="indexterm"></a><div class="important"><div
class="admonition_header"><h2>Using the hpsa driver for a
storage</h2></div><div class="admonition"><div
class="para">
+ Due to known issue with the <code
class="systemitem">hpsa</code> driver, <code
class="systemitem">kdump</code> is unable to save the dump to a storage
that uses this driver for HP Smart Array Controllers. If this applies to your machine, it
is advised that you save the dump to a remote system using the NFS or SSH protocol
instead.
+ </div></div></div></div><div class="section"
id="s3-kdump-configuration-cli-filtering"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-kdump-configuration-cli-filtering">22.1.2.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, open the <code
class="filename">/etc/kdump.conf</code> configuration file in a text
editor such as <span
class="application"><strong>vi</strong></span> or <span
class="application"><strong>nano</strong></span>, 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="id903924"
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="screen">core_collector makedumpfile
-c</pre><a id="id833161"
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">Table 22.2,
“Supported filtering levels”</a>. For example, to remove both zero and free pages,
use the following:
+ </div><pre class="screen">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>Table 22.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>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">1</code>
+ </td><td>
+ Zero pages
+ </td></tr><tr><td>
+ <code class="option">2</code>
+ </td><td>
+ Cache pages
+ </td></tr><tr><td>
+ <code class="option">4</code>
+ </td><td>
+ Cache private
+ </td></tr><tr><td>
+ <code class="option">8</code>
+ </td><td>
+ User pages
+ </td></tr><tr><td>
+ <code class="option">16</code>
+ </td><td>
+ 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"
id="s3-kdump-configuration-cli-action">22.1.2.4. Changing the Default
Action</h4></div></div></div><a id="id630715"
class="indexterm"></a><div class="para">
+ By default, when the kernel crash is captured, the root file system is mounted, and
<code class="command">/sbin/init</code> is run. To change this
behavior, open the <code class="filename">/etc/kdump.conf</code>
configuration file in a text editor such as <span
class="application"><strong>vi</strong></span> or <span
class="application"><strong>nano</strong></span>, 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">Table 22.3, “Supported
actions”</a>. For example:
+ </div><pre class="screen">default halt</pre><div
class="table"
id="table-kdump-configuration-cli-action-actions"><h6>Table 22.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>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">reboot</code>
+ </td><td>
+ Reboot the system, losing the core in the process.
+ </td></tr><tr><td>
+ <code class="option">halt</code>
+ </td><td>
+ After attempting to capture a core, halt the system no matter if it succeeded.
+ </td></tr><tr><td>
+ <code class="option">poweroff</code>
+ </td><td>
+ Power off the system.
+ </td></tr><tr><td>
+ <code class="option">shell</code>
+ </td><td>
+ 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><div class="section"
id="s3-kdump-configuration-cli-enable"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-kdump-configuration-cli-enable">22.1.2.5. Enabling the
Service</h4></div></div></div><a id="id636041"
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:
+ </div><pre class="screen"><code
class="command">systemctl enable
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:
+ </div><a id="id1056612"
class="indexterm"></a><pre class="screen"><code
class="command">systemctl start kdump.service</code></pre><div
class="para">
+ For more information on runlevels and configuring services in general, refer to
<a class="xref" href="#ch-Services_and_Daemons">Chapter 7,
<em>Services and Daemons</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"
id="s2-kdump-configuration-testing">22.1.3. Testing the
Configuration</h3></div></div></div><a id="id620269"
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">Section 7.2, “Running Services”</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 class="example"
id="ex-kdump-configuration-testing-vmcore"><h6>Example 22.2. Listing a
content of /var/crash/ after a crash</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">tree --charset=ascii /var/crash</code>
+/var/crash
+`-- 127.0.0.1-2010-08-25-08:45:02
+ `-- vmcore
+
+1 directory, 1 file</pre></div></div><br
class="example-break" /></div></div><div
class="section" id="s1-kdump-crash"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kdump-crash">22.2. Analyzing the Core
Dump</h2></div></div></div><a id="id554091"
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="id695040"
class="indexterm"></a><div class="note"><div
class="admonition_header"><h2>Make sure you have relevant packages
installed</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">Section 4.2.4, “Installing
Packages”</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"
id="s2-kdump-crash-running">22.2.1. Running the crash
Utility</h3></div></div></div><a id="id720310"
class="indexterm"></a><div class="para">
+ To start the utility, type the command in the following form at a shell prompt:
+ </div><pre class="screen"><code
class="command">crash /var/crash/<em
class="replaceable"><code>timestamp</code></em>/vmcore
/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>Example 22.3. 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"
id="s2-kdump-crash-log">22.2.2. Displaying the Message
Buffer</h3></div></div></div><a id="id610823"
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>Example 22.4. 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"
id="s2-kdump-crash-backtrace">22.2.3. Displaying a
Backtrace</h3></div></div></div><a id="id543385"
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>Example 22.5. 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"
id="s2-kdump-crash-processes">22.2.4. Displaying a Process
Status</h3></div></div></div><a id="id646812"
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>Example 22.6. 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"
id="s2-kdump-crash-memory">22.2.5. Displaying Virtual Memory
Information</h3></div></div></div><a id="id709206"
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>Example 22.7. 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"
id="s2-kdump-crash-files">22.2.6. Displaying Open
Files</h3></div></div></div><a id="id905771"
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>Example 22.8. 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"
id="s2-kdump-crash-exit">22.2.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>Example 22.9. 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"
id="s1-kdump-resources">22.3. Additional
Resources</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"
id="s2-kdump-resources-installed">22.3.1. Installed
Documentation</h3></div></div></div><a id="id669900"
class="indexterm"></a><a id="id669920"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><code
class="command">man
kdump.conf</code></span></dt><dd><div
class="para">
+ The manual page for the <code
class="filename">/etc/kdump.conf</code> configuration file containing
the full documentation of available options.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
makedumpfile</code></span></dt><dd><div
class="para">
+ The manual page for the <code
class="command">makedumpfile</code> core collector containing the full
documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
kexec</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">kexec</code>
containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
crash</code></span></dt><dd><div class="para">
+ The manual page for the <span
class="application"><strong>crash</strong></span> utility
containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="filename">/usr/share/doc/kexec-tools-<em
class="replaceable"><code>version</code></em>/kexec-kdump-howto.txt</code></span></dt><dd><div
class="para">
+ An overview of the <code class="systemitem">kdump</code> and
<code class="command">kexec</code> installation and usage.
+ </div></dd></dl></div></div><div
class="section" id="s2-kdump-resources-online"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-kdump-resources-online">22.3.2. Useful
Websites</h3></div></div></div><a id="id537209"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://people.redhat.com/anderson/">http://people.redh...
class="para">
+ The <span
class="application"><strong>crash</strong></span> utility
homepage.
+ </div></dd></dl></div></div></div></div></div><div
xml:lang="en-US" class="appendix" id="ch-RPM"
lang="en-US"><div
class="titlepage"><div><div><h1
class="title">RPM</h1></div></div></div><a
id="id813565" class="indexterm"></a><a
id="id813558" class="indexterm"></a><div
class="para">
+ The <em class="firstterm">RPM Package Manager</em> (RPM) is an
open packaging system
+ <a id="id813545" 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 15. 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="id565147" 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">Chapter 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">Chapter 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="id721386" 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"
id="s1-rpm-design">A.1. RPM Design
Goals</h2></div></div></div><a id="id788642"
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><dt
class="varlistentry"><span class="term">Upgradability
+ <a id="id788620" 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="id800886" 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="id592061" 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="id670003" 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"
id="s1-rpm-using">A.2. Using
RPM</h2></div></div></div><div class="para">
+ RPM has five basic modes of operation
+ <a id="id601047" 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">Section A.5,
“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"
id="s2-rpm-finding">A.2.1. Finding RPM
Packages</h3></div></div></div><a id="id839746"
class="indexterm"></a><a id="id729400"
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="id561633" class="indexterm"></a>
+ <a id="id765956" 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="id616241" class="indexterm"></a>
+ <a id="id507248" class="indexterm"></a>
+ . Refer to <a class="xref" href="#ch-yum">Chapter 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://m...;.
+ </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"
id="sec-Installing_and_Upgrading">A.2.2. Installing and
Upgrading</h3></div></div></div><a id="id607750"
class="indexterm"></a><a id="id913536"
class="indexterm"></a><a id="id791015"
class="indexterm"></a><a id="id409448"
class="indexterm"></a><div class="para">
+ RPM packages typically have file names
+ <a id="id509654" class="indexterm"></a>
+ like <code
class="filename">tree-1.5.3-2.fc15.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">fc15</code>) and CPU architecture (<code
class="filename">x86_64</code>).
+ </div><div class="para">
+ You can use <code class="command">rpm</code>'s <code
class="option">-U</code> option to:
+ </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.fc15.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.fc15.x86_64.rpm</code>
+</pre><div class="note"
id="note-Use_-Uvh_for_nicely-formatted_RPM_installs"><div
class="admonition_header"><h2>Use -Uvh for nicely-formatted RPM
installs</h2></div><div class="admonition"><div
class="para">
+ The <code class="option">-v</code> and <code
class="option">-h</code> options (which are combined with <code
class="option">-U</code>) cause <span
class="application"><strong>rpm</strong></span> to print
more verbose output and display a progress meter using hash signs.
+ </div></div></div><div class="para">
+ If the upgrade/installation is successful, the following output is displayed:
+ </div><pre class="screen">Preparing...
########################################### [100%]
+ 1:tree ###########################################
[100%]</pre><div class="warning"
id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages"><div
class="admonition_header"><h2>Always use the -i (install) option to
install new kernel packages!</h2></div><div
class="admonition"><div class="para">
+ <code class="command">rpm</code> provides two different
options for installing packages: the aforementioned <code
class="option">-U</code> option (which historically stands for <span
class="emphasis"><em>upgrade</em></span>), and the <code
class="option">-i</code> option, 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">Chapter 20, <em>Manually
Upgrading the Kernel</em></a>.
+ </div></div></div><div class="para">
+ The signature of a package is checked automatically when installing or upgrading a
package. The signature confirms that the package was signed by an authorized party. For
example, if the verification of the signature fails, an error message such as the
following is displayed:
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc15.x86_64.rpm:
Header V3 RSA/SHA256 signature: BAD, key ID
+d22e77f2</pre><div class="para">
+ If it is a new, header-only, signature, an error message such as the following is
displayed:
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc15.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.fc15.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">Section A.3, “Checking a Package's
Signature”</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"
id="s3-rpm-errors">A.2.2.1. Package Already
Installed</h4></div></div></div><div
class="para">
+ If a package of the same name and version is already installed
+ <a id="id591017" class="indexterm"></a>
+ <a id="id591029" class="indexterm"></a>
+ , the following output is displayed:
+ </div><pre class="screen">Preparing...
########################################### [100%]
+ package tree-1.5.3-2.fc15.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.fc15.x86_64.rpm</code>
+</pre><div class="para">
+ This option is helpful if files installed from the RPM were deleted or if you want
the original configuration files from the RPM to be installed.
+ </div></div><div class="section"
id="s3-rpm-conflicting-files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-rpm-conflicting-files">A.2.2.2. Conflicting
Files</h4></div></div></div><a id="id815226"
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="id1283211" class="indexterm"></a>
+ <a id="id1283223" class="indexterm"></a>
+ , the following is displayed:
+ </div><pre class="screen">Preparing...
##################################################
+ file /usr/bin/foobar from install of foo-1.0-1.fc15.x86_64 conflicts
+with file from package bar-3.1.1.fc15.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.fc15.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"
id="s3-rpm-unresolved-dependency">A.2.2.3. Unresolved
Dependency</h4></div></div></div><a id="id711845"
class="indexterm"></a><a id="id711857"
class="indexterm"></a><div class="para">
+ RPM packages may sometimes depend on other packages
+ <a id="id441412" class="indexterm"></a>
+ <a id="id441424" 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.fc15.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.fc15.x86_64.rpm
bar-3.1.1.fc15.x86_64.rpm</code>
+</pre><div class="para">
+ If installation of both packages is successful, output similar to the following is
displayed:
+ </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">
+ If the package that contains <code
class="filename">bar.so.3</code> is in the RPM database, the name of
the package is displayed:
+ </div><pre
class="screen">bar-3.1.1.fc15.i586.rpm</pre><div
class="warning"
id="warning-install-Warning-Forcing_Package_Installation"><div
class="admonition_header"><h2>Warning: Forcing Package
Installation</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"
id="sec-Configuration_File_Changes">A.2.3. Configuration File
Changes</h3></div></div></div><a id="id624144"
class="indexterm"></a><a id="id624156"
class="indexterm"></a><div class="para">
+ Because RPM performs intelligent upgrading of packages with configuration files
+ <a id="id417810" 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.fc15.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.fc15.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"
id="s2-rpm-uninstalling">A.2.4. Uninstalling</h3></div></div></div><a
id="id934186" class="indexterm"></a><a
id="id1265839" class="indexterm"></a><a
id="id1265851" class="indexterm"></a><a
id="id447685" class="indexterm"></a><div
class="para">
+ Uninstalling a package is just as simple as installing one. Type the following
command at a shell prompt:
+ </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.fc15.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.fc15.x86_64
+ libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc15.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc15.x86_64
+ ghostscript is needed by (installed)
printer-filters-1.1-4.fc15.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">Section A.2.2.3, “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.fc15.x86_64</pre><div class="warning"
id="warning-uninstall-Warning-Forcing_Package_Installation"><div
class="admonition_header"><h2>Warning: Forcing Package
Installation</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"
id="s2-rpm-freshening">A.2.5. Freshening</h3></div></div></div><a
id="id544179" class="indexterm"></a><a
id="id544191" 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.fc15.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"
id="s2-rpm-querying">A.2.6. Querying</h3></div></div></div><a
id="id418551" class="indexterm"></a><a
id="id418563" 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.fc15.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> — queries all currently
installed packages.
+ </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"
id="s2-rpm-verifying">A.2.7. Verifying</h3></div></div></div><a
id="id418572" class="indexterm"></a><a
id="id418584" 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">
+ To verify a package containing a particular file:
+ </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">
+ To verify an installed package against an RPM package file:
+ </div><pre class="screen">
+<code class="command">rpm -Vp
tree-1.5.2.2-4.fc15.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 checksum
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">S</code> — file size
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">L</code> — symbolic link
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">T</code> — file modification
time
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">D</code> — device
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">U</code> — user
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">G</code> — group
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">M</code> — mode (includes
permissions and file type)
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">?</code> — unreadable file (file
permission errors, for example)
+ </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="en-US"
class="section" id="s1-check-rpm-sig"
lang="en-US"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-check-rpm-sig">A.3. Checking a Package's
Signature</h2></div></div></div><a id="id943695"
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="id981841" class="indexterm"></a><a
id="id976422" class="indexterm"></a><a
id="id976435" 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"
id="s2-keys-importing">A.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"
id="s2-keys-checking">A.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...;.
+ </div></div></div><div class="section"
id="s1-rpm-impressing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-rpm-impressing">A.4. Practical and Common Examples of RPM
Usage</h2></div></div></div><a id="id798326"
class="indexterm"></a><a id="id798338"
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">
+ Perhaps you have deleted some files by accident, but you are not sure what you
deleted. To verify your entire system and see what might be missing, you could try the
following command:
+ </div><a id="id721464"
class="indexterm"></a><a id="id721475"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre><div class="para">
+ If some files are missing or appear to have been corrupted, you should probably
either re-install the package or uninstall and then re-install the package.
+ </div></li><li class="listitem"><div
class="para">
+ At some point, you might see a file that you do not recognize. To find out which
package owns it, enter:
+ </div><a id="id744159"
class="indexterm"></a><a id="id744171"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qf /usr/bin/ghostscript</code>
+</pre><div class="para">
+ The output would look like the following:
+ </div><pre
class="screen">ghostscript-8.70-1.fc15.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">
+ and the appropriate package is verified.
+ </div></li><li class="listitem"><div
class="para">
+ Do you want to find out more information about a particular program? You can try the
following command to locate the documentation which came with the package that owns that
program:
+ </div><a id="id552288"
class="indexterm"></a><a id="id552300"
class="indexterm"></a><a id="id587061"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qdf /usr/bin/free</code>
+</pre><div class="para">
+ The output would be similar to the following:
+ </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">
+ You may find a new RPM, but you do not know what it does. To find information about
it, use the following command:
+ </div><a id="id469779"
class="indexterm"></a><a id="id469791"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qip
crontabs-1.10-31.fc15.noarch.rpm</code>
+</pre><div class="para">
+ The output would be similar to the following:
+ </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="id934210"
class="indexterm"></a><a id="id934222"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qlp
crontabs-1.10-31.fc15.noarch.rpm</code>
+</pre><div class="para">
+ The output is similar to the following:
+ </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"
id="s1-rpm-additional-resources">A.5. Additional
Resources</h2></div></div></div><a id="id628956"
class="indexterm"></a><div class="para">
+ RPM is an extremely complex utility with many options and methods for querying,
installing, upgrading, and removing packages. Refer to the following resources to learn
more about RPM.
+ </div><div class="section"
id="s2-rpm-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-rpm-installed-docs">A.5.1. Installed
Documentation</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"
id="s2-rpm-useful-websites">A.5.2. Useful
Websites</h3></div></div></div><div
class="itemizedlist"><a id="id574085"
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/">http...
+ </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"
id="s2-rpm-related-books">A.5.3. Related
Books</h3></div></div></div><a id="id474535"
class="indexterm"></a><div
class="variablelist"><dl><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-rp...
</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="en-US" class="appendix"
id="ch-The_sysconfig_Directory" lang="en-US"><div
class="titlepage"><div><div><h1 class="title">The
sysconfig Directory</h1></div></div></div><a
id="id541700" class="indexterm"></a><a
id="id811089" 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">
+ The actual content of your <code
class="filename">/etc/sysconfig/</code> directory depends on the
programs you have installed on your machine. To find the name of the package the
configuration file belongs to, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">yum provides /etc/sysconfig/<em
class="replaceable"><code>filename</code></em>
</code>
+</pre><div class="para">
+ Refer to <a class="xref"
href="#sec-Installing">Section 4.2.4, “Installing Packages”</a> for
more information on how to install new packages in Fedora.
+ </div></div></div><div class="section"
id="s1-sysconfig-files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysconfig-files">B.1. Files in the /etc/sysconfig/
Directory</h2></div></div></div><a id="id619871"
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"
id="s2-sysconfig-arpwatch">B.1.1. /etc/sysconfig/arpwatch
</h3></div></div></div><a id="id758364"
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><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"
id="s2-sysconfig-authconfig">B.1.2. /etc/sysconfig/authconfig
</h3></div></div></div><a id="id908571"
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><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">Chapter 8, <em>Configuring
Authentication</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"
id="s2-sysconfig-autofs">B.1.3. /etc/sysconfig/autofs
</h3></div></div></div><a id="id1062136"
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><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/"...
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"
id="s2-sysconfig-clock">B.1.4. /etc/sysconfig/clock
</h3></div></div></div><a id="id449016"
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><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-Date_and_Time_Configuration-Date_and_Time">Section 2.1, “Date and
Time Configuration Tool”</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"
id="s2-sysconfig-dhcpd">B.1.5. /etc/sysconfig/dhcpd
</h3></div></div></div><a id="id393706"
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><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">Chapter 10, <em>DHCP
Servers</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"
id="s2-sysconfig-firewall">B.1.6. /etc/sysconfig/firstboot
</h3></div></div></div><a id="id764790"
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><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"
id="s2-sysconfig-i18n">B.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><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"
id="s2-sysconfig-init">B.1.8. /etc/sysconfig/init
</h3></div></div></div><a id="id623778"
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><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"
id="s2-sysconfig-ip6tables">B.1.9. /etc/sysconfig/ip6tables-config
</h3></div></div></div><a id="id566452"
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><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"
id="s2-sysconfig-kybd">B.1.10. /etc/sysconfig/keyboard
</h3></div></div></div><a id="id818479"
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><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"
id="s2-sysconfig-ldap">B.1.11. /etc/sysconfig/ldap
</h3></div></div></div><a id="id1061947"
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><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">Section 14.1,
“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"
id="s2-sysconfig-named">B.1.12. /etc/sysconfig/named
</h3></div></div></div><a id="id495678"
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><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">Section 11.2,
“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"
id="s2-sysconfig-network">B.1.13. /etc/sysconfig/network
</h3></div></div></div><a id="id840888"
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><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"
id="s2-sysconfig-ntpd">B.1.14. /etc/sysconfig/ntpd
</h3></div></div></div><a id="id421870"
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><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-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Section 2.2.2,
“Configuring the 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"
id="s2-sysconfig-quagga">B.1.15. /etc/sysconfig/quagga
</h3></div></div></div><a id="id592456"
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><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"
id="s2-sysconfig-radvd">B.1.16. /etc/sysconfig/radvd
</h3></div></div></div><a id="id1244731"
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><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"
id="s2-sysconfig-samba">B.1.17. /etc/sysconfig/samba
</h3></div></div></div><a id="id423105"
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><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">Section 15.1,
“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"
id="s2-sysconfig-selinux">B.1.18. /etc/sysconfig/selinux
</h3></div></div></div><a id="id509866"
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><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"
id="s2-sysconfig-sendmail">B.1.19. /etc/sysconfig/sendmail
</h3></div></div></div><a id="id417843"
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><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">Section 13.3.2, “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"
id="s2-sysconfig-spamd">B.1.20. /etc/sysconfig/spamassassin
</h3></div></div></div><a id="id429907"
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><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">Section 13.4.2.6, “Spam Filters”</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"
id="s2-sysconfig-squid">B.1.21. /etc/sysconfig/squid
</h3></div></div></div><a id="id787320"
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><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"
id="s2-sysconfig-rcu">B.1.22. /etc/sysconfig/system-config-users
</h3></div></div></div><a id="id552262"
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><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">Section 3.2, “User Manager Tool”</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"
id="s2-sysconfig-vncservers">B.1.23. /etc/sysconfig/vncservers
</h3></div></div></div><a id="id828096"
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><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"
id="s2-sysconfig-xinetd">B.1.24. /etc/sysconfig/xinetd
</h3></div></div></div><a id="id629011"
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><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">Chapter 7, <em>Services and
Daemons</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"
id="s1-sysconfig-etcsysconf-dir">B.2. Directories in the /etc/sysconfig/
Directory</h2></div></div></div><a id="id609588"
class="indexterm"></a><div class="para">
+ The following directories are normally found in <code
class="filename">/etc/sysconfig/</code>.
+ </div><a id="id609614"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="filename">/etc/sysconfig/cbq/</code>
</span></dt><dd><div class="para">
+ <a id="id958381" 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="id678211" 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="id410259" 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">
+ Various shared network function scripts which should not be edited directly.
+ </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">Chapter 6, <em>Network
Interfaces</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"
id="s1-sysconfig-additional-resources">B.3. Additional
Resources</h2></div></div></div><a id="id544629"
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"
id="s2-sysconfig-installed-documentation">B.3.1. Installed
Documentation</h3></div></div></div><a id="id544668"
class="indexterm"></a><div
class="variablelist"><dl><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="en-US" class="appendix" id="ch-proc"
lang="en-US"><div
class="titlepage"><div><div><h1 class="title">The
proc File System</h1></div></div></div><a
id="id708284" class="indexterm"></a><a
id="id548202" 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"
id="s1-proc-virtual">C.1. A Virtual File
System</h2></div></div></div><a id="id836807"
class="indexterm"></a><a id="id476148"
class="indexterm"></a><a id="id1279267"
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"
id="s2-proc-viewing">C.1.1. Viewing Virtual
Files</h3></div></div></div><a id="id1229773"
class="indexterm"></a><a id="id1229787"
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"
id="s2-proc-change">C.1.2. Changing Virtual
Files</h3></div></div></div><a id="id768609"
class="indexterm"></a><a id="id628856"
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">Section C.4, “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">Section C.3.9, “ /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"
id="s1-proc-topfiles">C.2. Top-level Files within the <code
class="filename">proc</code> File
System</h2></div></div></div><a id="id971839"
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"
id="s2-proc-buddyinfo">C.2.1. /proc/buddyinfo
</h3></div></div></div><a id="id628430"
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"
id="s2-proc-cmdline">C.2.2. /proc/cmdline
</h3></div></div></div><a id="id482394"
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:/...;.
+ </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"
id="s2-proc-cpuinfo">C.2.3. /proc/cpuinfo
</h3></div></div></div><a id="id450507"
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"
id="s2-proc-crypto">C.2.4. /proc/crypto
</h3></div></div></div><a id="id804785"
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"
id="s2-proc-devices">C.2.5. /proc/devices
</h3></div></div></div><a id="id572167"
class="indexterm"></a><a id="id572192"
class="indexterm"></a><a id="id953504"
class="indexterm"></a><a id="id953517"
class="indexterm"></a><a id="id953535"
class="indexterm"></a><a id="id953553"
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"
id="s2-proc-dma">C.2.6. /proc/dma
</h3></div></div></div><a id="id603685"
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"
id="s2-proc-execdomains">C.2.7. /proc/execdomains
</h3></div></div></div><a id="id603729"
class="indexterm"></a><a id="id926783"
class="indexterm"></a><a id="id926800"
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"
id="s2-proc-fb">C.2.8. /proc/fb
</h3></div></div></div><a id="id926845"
class="indexterm"></a><a id="id788700"
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"
id="s2-proc-filesystems">C.2.9. /proc/filesystems
</h3></div></div></div><a id="id788740"
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"
id="s2-proc-interrupts">C.2.10. /proc/interrupts
</h3></div></div></div><a id="id747212"
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"
id="s2-proc-iomem">C.2.11. /proc/iomem
</h3></div></div></div><a id="id662304"
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"
id="s2-proc-ioports">C.2.12. /proc/ioports
</h3></div></div></div><a id="id639799"
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"
id="s2-proc-kcore">C.2.13. /proc/kcore
</h3></div></div></div><a id="id639853"
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"
id="s2-proc-kmsg">C.2.14. /proc/kmsg
</h3></div></div></div><a id="id954050"
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"
id="s2-proc-loadavg">C.2.15. /proc/loadavg
</h3></div></div></div><a id="id496050"
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"
id="s2-proc-locks">C.2.16. /proc/locks
</h3></div></div></div><a id="id593760"
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"
id="s2-proc-mdstat">C.2.17. /proc/mdstat
</h3></div></div></div><a id="id1003983"
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"
id="s2-proc-meminfo">C.2.18. /proc/meminfo
</h3></div></div></div><a id="id601484"
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"
id="s2-proc-misc">C.2.19. /proc/misc
</h3></div></div></div><a id="id705234"
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"
id="s2-proc-modules">C.2.20. /proc/modules
</h3></div></div></div><a id="id705281"
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"
id="s2-proc-mounts">C.2.21. /proc/mounts
</h3></div></div></div><a id="id530069"
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"
id="s2-proc-mtrr">C.2.22. /proc/mtrr
</h3></div></div></div><a id="id683344"
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"
id="s2-proc-partitions">C.2.23. /proc/partitions
</h3></div></div></div><a id="id612032"
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"
id="s2-proc-slabinfo">C.2.24. /proc/slabinfo
</h3></div></div></div><a id="id397241"
class="indexterm"></a><a id="id432391"
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"
id="s2-proc-stat">C.2.25. /proc/stat
</h3></div></div></div><a id="id484827"
class="indexterm"></a><a id="id678768"
class="indexterm"></a><a id="id678783"
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"
id="s2-proc-swaps">C.2.26. /proc/swaps
</h3></div></div></div><a id="id525310"
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"
id="s2-proc-sysrq-trigger">C.2.27. /proc/sysrq-trigger
</h3></div></div></div><a id="id740892"
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">Section C.3.9.3, “ /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"
id="s2-proc-uptime">C.2.28. /proc/uptime
</h3></div></div></div><a id="id740955"
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"
id="s2-proc-version">C.2.29. /proc/version
</h3></div></div></div><a id="id581129"
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(a)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"
id="s1-proc-directories">C.3. Directories within
/proc/</h2></div></div></div><a id="id720061"
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"
id="s2-proc-processdirs">C.3.1. Process
Directories</h3></div></div></div><a id="id720098"
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"
id="s3-proc-self">C.3.1.1. /proc/self/
</h4></div></div></div><a id="id1310680"
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"
id="s2-proc-dir-bus">C.3.2. /proc/bus/
</h3></div></div></div><a id="id1310732"
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"
id="s2-proc-pci">C.3.3. /proc/bus/pci
</h3></div></div></div><a id="id678372"
class="indexterm"></a><a id="id678403"
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">[output truncated]</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"
id="s2-proc-dir-driver">C.3.4. /proc/driver/
</h3></div></div></div><a id="id967284"
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"
id="s2-proc-dir-fs">C.3.5. /proc/fs
</h3></div></div></div><a id="id440924"
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"
id="s2-proc-dir-irq">C.3.6. /proc/irq/
</h3></div></div></div><a id="id440978"
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"
id="s2-proc-dir-net">C.3.7. /proc/net/
</h3></div></div></div><a id="id943366"
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"
id="s2-proc-dir-scsi">C.3.8. /proc/scsi/
</h3></div></div></div><a id="id462574"
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"
id="s2-proc-dir-sys">C.3.9. /proc/sys/
</h3></div></div></div><a id="id627245"
class="indexterm"></a><a id="id627268"
class="indexterm"></a><a id="id627282"
class="indexterm"></a><a id="id997558"
class="indexterm"></a><a id="id997576"
class="indexterm"></a><a id="id997591"
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">Section C.4, “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"
id="s3-proc-sys-dev">C.3.9.1. /proc/sys/dev/
</h4></div></div></div><a id="id753460"
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"
id="s3-proc-sys-fs">C.3.9.2. /proc/sys/fs/
</h4></div></div></div><a id="id541963"
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"
id="s3-proc-sys-kernel">C.3.9.3. /proc/sys/kernel/
</h4></div></div></div><a id="id396874"
class="indexterm"></a><a id="id396904"
class="indexterm"></a><a id="id396919"
class="indexterm"></a><a id="id852495"
class="indexterm"></a><a id="id852514"
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, in bytes. 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, in bytes. 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"
id="s3-proc-sys-net">C.3.9.4. /proc/sys/net/
</h4></div></div></div><a id="id534808"
class="indexterm"></a><a id="id534838"
class="indexterm"></a><a id="id534853"
class="indexterm"></a><a id="id660216"
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"
id="s3-proc-sys-vm">C.3.9.5. /proc/sys/vm/
</h4></div></div></div><a id="id855212"
class="indexterm"></a><a id="id621388"
class="indexterm"></a><a id="id621402"
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"
id="s2-proc-dir-sysvipc">C.3.10. /proc/sysvipc/
</h3></div></div></div><a id="id825280"
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"
id="s2-proc-tty">C.3.11. /proc/tty/
</h3></div></div></div><a id="id719466"
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"
id="s2-proc-pid">C.3.12. /proc/<em
class="replaceable"><code>PID</code></em>/
</h3></div></div></div><a id="id440776"
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"
id="s1-proc-sysctl">C.4. Using the sysctl
Command</h2></div></div></div><a id="id942936"
class="indexterm"></a><a id="id766540"
class="indexterm"></a><a id="id766554"
class="indexterm"></a><a id="id766577"
class="indexterm"></a><a id="id766607"
class="indexterm"></a><a id="id658723"
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, the <code
class="command">init</code> program runs the <code
class="filename">/etc/rc.d/rc.sysinit</code> script. This script
contains a command to execute <code class="command">sysctl</code>
using <code class="filename">/etc/sysctl.conf</code> 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><div class="section"
id="s1-proc-additional-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-proc-additional-resources">C.5. References</h2></div></div></div><a
id="id607646" 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">Installed
Documentation</h1></div></div></div><a id="id914787"
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">Useful
Websites</h1></div></div></div><a id="id500687"
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="en-US" class="appendix" id="app-Revision_History"
lang="en-US"><div
class="titlepage"><div><div><h1
class="title">Revision
History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table border="0"
width="100%" summary="Revision history"><tr><th
align="left" valign="top"
colspan="3"><strong>Revision
History</strong></th></tr><tr><td
align="left">Revision 1-0</td><td align="left">Tue May
24 2011</td><td align="left"><span
class="author"><span class="firstname">Jaromír</span>
<span
class="surname">Hradílek</span></span></td></tr><tr><td
align="left" colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Fedora 15 release of the <em
class="citetitle">Deployment
Guide</em>.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><div class="index"
id="id895660"><div
class="titlepage"><div><div><h2
class="title">Index</h2></div></div></div><div
class="index"><div
class="indexdiv"><h3>Symbols</h3><dl><dt>
.fetchmailrc , <a class="indexterm"
href="#s3-email-mda-fetchmail-configuration">Fetchmail Configuration
Options</a></dt><dd><dl><dt>server options, <a
class="indexterm"
href="#s3-email-mda-fetchmail-configuration-server">Server
Options</a></dt><dt>user options, <a class="indexterm"
href="#s3-email-fetchmail-configuration-user">User
Options</a></dt></dl></dd><dt>.htaccess, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dd><dl><dt>(see also Apache
HTTP Server)</dt></dl></dd><dt>.htpasswd, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dd><dl><dt>(see also Apache
HTTP Server)</dt></dl></dd><dt> .procmailrc , <a
class="indexterm" href="#s2-email-procmail-configuration">Procmail
Configuratio
n</a></dt><dt> /dev/shm , <a class="indexterm"
href="#s1-sysinfo-filesystems">File
Systems</a></dt><dt>/etc/named.conf (see BIND)</dt><dt>
/etc/sysconfig/ directory (see sysconfig directory)</dt><dt>
/etc/sysconfig/dhcpd , <a class="indexterm"
href="#id619308">Starting and Stopping the
Server</a></dt><dt> /proc/ directory, <a class="indexterm"
href="#s2-sysinfo-installed-docs">Installed Documentation</a> (see
proc file system)</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></dl></div><div
class="indexdiv"><h3>A</h3><dl><dt>Access
Control</dt><dd><dl><dt>configuring in SSSD, <a
class="indexterm" href="#id1301394">Configuring Access
Control</a></dt><dt>in SSSD, rules, <a class="indexterm"
href="#id1301434">The Simple Access
Provider</a></dt></dl></dd><dt>adding</dt><dd><dl><dt>group,
<a class="inde
xterm" href="#s2-users-cmd-line">Command Line
Configuration</a></dt><dt>user, <a class="indexterm"
href="#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>anacron, <a
class="indexterm" href="#s1-autotasks-cron-anacron">Cron and
Anacron</a></dt><dd><dl><dt>anacron configuration file,
<a class="indexterm"
href="#s2-configuring-anacron-jobs">Configuring Anacron
Jobs</a></dt><dt>user-defined tasks, <a class="indexterm"
href="#s2-configuring-anacron-jobs">Configuring Anacron
Jobs</a></dt></dl></dd><dt> anacrontab , <a
class="indexterm" href="#s2-configuring-anacron-jobs">Configuring
Anacron Jobs</a></dt><dt>Apache HTTP
Server</dt><dd><dl><dt>additional
resources</dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="#s3-apache-resources-installed">Installed
Documentation</a></dt><dt>useful websites, <a
class="indexterm" href="#s3-apache-resources-web">Useful
Websites</a></dt></dl></dd><dt>checking configuration, <a
class="indexterm" href="#s2-apach
e-editing">Editing the Configuration Files</a></dt><dt>checking
status, <a class="indexterm"
href="#s3-apache-running-status">Checking the Service
Status</a></dt><dt>directives</dt><dd><dl><dt><Directory>,
<a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt><IfDefine>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt><IfModule>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt><Location>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt><Proxy>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt><VirtualHost>, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AccessFileName, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Commo
n httpd.conf Directives</a></dt><dt>Action, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AddDescription, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AddEncoding, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AddHandler, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AddIcon, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AddIconByEncoding, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AddIconByType, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AddLanguage, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>AddType, <a
class="indexterm" href="#s3-
apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Alias, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Allow, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AllowOverride, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>BrowserMatch, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CacheDefaultExpire, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>CacheDisable, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>CacheEnable, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>CacheLastModifiedFactor, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt>
<dt>CacheMaxExpire, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CacheNegotiatedDocs, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>CacheRoot, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>CustomLog, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>DefaultIcon, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>DefaultType, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>Deny, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>DirectoryIndex, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>DocumentRoot, <a
class="indexterm" href="#s3-apache-httpdconf-directiv
es">Common httpd.conf Directives</a></dt><dt>ErrorDocument,
<a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ErrorLog, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ExtendedStatus, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Group, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>HeaderName, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>HostnameLookups, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>Include, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>IndexIgnore, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>IndexOptions, <a
class="indexterm" hr
ef="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>KeepAlive, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>KeepAliveTimeout, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>LanguagePriority, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>Listen, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>LoadModule, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>LogFormat, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>LogLevel, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>MaxClients, <a
class="indexterm" href="#s3-apache-mpm-common">Common
Multi-Processing Module Directives</a></dt><dt>
MaxKeepAliveRequests, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>MaxSpareServers, <a
class="indexterm" href="#s3-apache-mpm-common">Common
Multi-Processing Module Directives</a></dt><dt>MaxSpareThreads, <a
class="indexterm" href="#s3-apache-mpm-common">Common
Multi-Processing Module Directives</a></dt><dt>MinSpareServers, <a
class="indexterm" href="#s3-apache-mpm-common">Common
Multi-Processing Module Directives</a></dt><dt>MinSpareThreads, <a
class="indexterm" href="#s3-apache-mpm-common">Common
Multi-Processing Module Directives</a></dt><dt>NameVirtualHost, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>Options, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>Order, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>PidFile, <a
class="indexterm" href="#s3-apache
-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ProxyRequests, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ReadmeName, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Redirect, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ScriptAlias, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerAdmin, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerName, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerRoot, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerSignature, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>ServerTokens,
<a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>SetEnvIf, <a class="indexterm"
href="#s3-apache-sslconf-common">Common ssl.conf
Directives</a></dt><dt>StartServers, <a class="indexterm"
href="#s3-apache-mpm-common">Common Multi-Processing Module
Directives</a></dt><dt>SuexecUserGroup, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>ThreadsPerChild, <a
class="indexterm" href="#s3-apache-mpm-common">Common
Multi-Processing Module Directives</a></dt><dt>Timeout, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>TypesConfig, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>UseCanonicalName, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>User, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf
Directives</a></dt><dt>UserDir, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/httpd/,
<a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/etc/httpd/conf.d/, <a
class="indexterm" href="#s2-apache-editing">Editing the
Configuration Files</a>, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/usr/lib/httpd/modules/, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</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">Common
httpd.conf Directives</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">Common
httpd.conf Direct
ives</a></dt><dt>/var/www/cgi-bin/, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/var/www/html/, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/var/www/icons/, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>~/public_html/, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf
Directives</a></dt></dl></dd><dt>files</dt><dd><dl><dt>.htaccess,
<a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>.htpasswd, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/etc/httpd/conf.d/ssl.conf, <a
class="indexterm" href="#s3-apache-sslconf-common">Common ssl.conf
Directives</a>, <a class="indexterm"
href="#s3-apache-mod_ssl-enabling">Enabling the mod_ssl
Module</a></dt><dt>/etc/httpd/conf/httpd.conf, <a cla
ss="indexterm" href="#s2-apache-editing">Editing the Configuration
Files</a>, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a>, <a class="indexterm"
href="#s3-apache-mpm-common">Common Multi-Processing Module
Directives</a></dt><dt>/etc/httpd/logs/access_log, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>/etc/httpd/logs/error_log, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>/etc/httpd/run/httpd.pid, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>/etc/mime.types, <a
class="indexterm" href="#s3-apache-httpdconf-directives">Common
httpd.conf
Directives</a></dt></dl></dd><dt>modules</dt><dd><dl><dt>developing,
<a class="indexterm" href="#s3-apache-dso-writing">Writing a
Module</a></dt><dt>loading, <a class="indexterm"
href="#s3-apache-dso-loading">Loading a Module</a></dt>
<dt>mod_asis, <a class="indexterm"
href="#s2-apache-version2-changes">Notable
Changes</a></dt><dt>mod_cache, <a class="indexterm"
href="#s2-apache-version2-features">New
Features</a></dt><dt>mod_cern_meta, <a class="indexterm"
href="#s2-apache-version2-changes">Notable
Changes</a></dt><dt>mod_disk_cache, <a class="indexterm"
href="#s2-apache-version2-features">New
Features</a></dt><dt>mod_ext_filter, <a class="indexterm"
href="#s2-apache-version2-changes">Notable
Changes</a></dt><dt>mod_proxy_balancer, <a
class="indexterm" href="#s2-apache-version2-features">New
Features</a></dt><dt>mod_rewrite, <a class="indexterm"
href="#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>mod_ssl, <a class="indexterm"
href="#s2-apache-mod_ssl">Setting Up an SSL
Server</a></dt><dt>mod_userdir, <a class="indexterm"
href="#s2-apache-version2-migrating">Updating the
Configuration</a></dt></dl></dd><dt>restarting, <a
class="indexterm" href="#s3-apache-running-restarting">Re
starting the Service</a></dt><dt>SSL
server</dt><dd><dl><dt>certificate, <a
class="indexterm" href="#s3-apache-mod_ssl-certificates">An
Overview of Certificates and Security</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">Generating a New Key and
Certificate</a></dt><dt>certificate authority, <a
class="indexterm" href="#s3-apache-mod_ssl-certificates">An
Overview of Certificates and Security</a></dt><dt>private key, <a
class="indexterm" href="#s3-apache-mod_ssl-certificates">An
Overview of Certificates and Security</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">Generating a New Key and
Certificate</a></dt><dt>public key, <a class="indexterm"
href="#s3-apache-mod_ssl-certificates">An Overview of Certificates and
Security</a></dt></dl></dd><dt>starting, <a class
="indexterm" href="#s3-apache-running-starting">Starting the
Service</a></dt><dt>stopping, <a class="indexterm"
href="#s3-apache-running-stopping">Stopping the
Service</a></dt><dt>version
2.2</dt><dd><dl><dt>changes, <a class="indexterm"
href="#s2-apache-version2-changes">Notable
Changes</a></dt><dt>features, <a class="indexterm"
href="#s2-apache-version2-features">New
Features</a></dt><dt>updating from version 2.0, <a
class="indexterm" href="#s2-apache-version2-migrating">Updating the
Configuration</a></dt></dl></dd><dt>virtual host, <a
class="indexterm" href="#s2-apache-virtualhosts">Setting Up Virtual
Hosts</a></dt></dl></dd><dt> at , <a
class="indexterm" href="#s1-autotasks-at-batch">At and
Batch</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="#s1-autotasks-additional-resources">Additional
Resources</a></dt></dl></dd><dt> authconfig (see
Authentication Configuration Tool )</dt><dd><dl><dt> commands ,
<a class="indexterm" href="#sect-The_Authenticat
ion_Configuration_Tool-Command_Line_Version">Command Line
Version</a></dt></dl></dd><dt>authentication</dt><dd><dl><dt>
Authentication Configuration Tool , <a class="indexterm"
href="#sect-The_Authentication_Configuration_Tool">The Authentication
Configuration Tool</a></dt><dt> using fingerprint support , <a
class="indexterm"
href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">Advanced
Options</a></dt><dt> using smart card authentication , <a
class="indexterm"
href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">Advanced
Options</a></dt></dl></dd><dt> Authentication Configuration
Tool </dt><dd><dl><dt> and Kerberos authentication , <a
class="indexterm"
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and LDAP , <a
class="indexterm"
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and NIS , <a class="i
ndexterm"
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and NIS authentication , <a
class="indexterm"
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and Winbind , <a
class="indexterm"
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and Winbind authentication , <a
class="indexterm"
href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt></dl></dd><dt>authoritative
nameserver (see BIND)</dt><dt>Automated Tasks, <a
class="indexterm" href="#ch-Automating_System_Tasks">Automating
System Tasks</a></dt></dl></div><div
class="indexdiv"><h3>B</h3><dl><dt> batch , <a
class="indexterm" href="#s1-autotasks-at-batch">At and
Batch</a></dt><dd><dl><dt>additional resources, <a
class="indexterm" href="#s1-autot
asks-additional-resources">Additional
Resources</a></dt></dl></dd><dt>Berkeley Internet Name
Domain (see
BIND)</dt><dt>BIND</dt><dd><dl><dt>additional
resources</dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="#s3-bind-installed-docs">Installed
Documentation</a></dt><dt>related books, <a
class="indexterm" href="#s3-bind-related-books">Related
Books</a></dt><dt>useful websites, <a class="indexterm"
href="#s3-bind-useful-websites">Useful
Websites</a></dt></dl></dd><dt>common mistakes, <a
class="indexterm" href="#s2-bind-mistakes">Common Mistakes to
Avoid</a></dt><dt>configuration</dt><dd><dl><dt>acl
statement, <a class="indexterm"
href="#s3-bind-namedconf-state">Common Statement
Types</a></dt><dt>comment tags, <a class="indexterm"
href="#s3-bind-namedconf-comm">Comment
Tags</a></dt><dt>controls statement, <a class="indexterm"
href="#s3-bind-namedconf-state-other">Other Statement
Types</a></dt><dt>include statement, <a class="indexterm"
href="#s3-bind-namedco
nf-state">Common Statement Types</a></dt><dt>key statement,
<a class="indexterm" href="#s3-bind-namedconf-state-other">Other
Statement Types</a></dt><dt>logging statement, <a
class="indexterm" href="#s3-bind-namedconf-state-other">Other
Statement Types</a></dt><dt>options statement, <a
class="indexterm" href="#s3-bind-namedconf-state">Common Statement
Types</a></dt><dt>server statement, <a class="indexterm"
href="#s3-bind-namedconf-state-other">Other Statement
Types</a></dt><dt>trusted-keys statement, <a
class="indexterm" href="#s3-bind-namedconf-state-other">Other
Statement Types</a></dt><dt>view statement, <a
class="indexterm" href="#s3-bind-namedconf-state-other">Other
Statement Types</a></dt><dt>zone statement, <a
class="indexterm" href="#s3-bind-namedconf-state">Common Statement
Types</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/named/,
<a class="indexterm" href="#s2-bind-namedconf">Configuring the
named Service</a></dt><dt>/var/named/, <a class="indexterm"
hr
ef="#s2-bind-zone">Editing Zone
Files</a></dt><dt>/var/named/data/, <a class="indexterm"
href="#s2-bind-zone">Editing Zone
Files</a></dt><dt>/var/named/dynamic/, <a class="indexterm"
href="#s2-bind-zone">Editing Zone
Files</a></dt><dt>/var/named/slaves/, <a class="indexterm"
href="#s2-bind-zone">Editing Zone
Files</a></dt></dl></dd><dt>features</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 Zone
Transfers (IXFR)</a></dt><dt>Internet Protocol version 6 (IPv6), <a
class="indexterm" href="#s3-bind-features-ipv6">Internet Protocol
version 6 (IPv6)</a></dt><dt>multiple views, <a
class="indexterm" href="#s3-bind-features-views">Multiple
Views</a></dt><dt>Trans
action SIGnature (TSIG), <a class="indexterm"
href="#s3-bind-features-tsig">Transaction SIGnatures
(TSIG)</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/etc/named.conf,
<a class="indexterm" href="#s2-bind-namedconf">Configuring the
named Service</a>, <a class="indexterm"
href="#s3-bind-rndc-configuration">Configuring the
Utility</a></dt><dt>/etc/rndc.conf, <a class="indexterm"
href="#s3-bind-rndc-configuration">Configuring the
Utility</a></dt><dt>/etc/rndc.key, <a class="indexterm"
href="#s3-bind-rndc-configuration">Configuring the
Utility</a></dt></dl></dd><dt>resource record, <a
class="indexterm" href="#s2-dns-introduction-zones">Nameserver
Zones</a></dt><dt>types</dt><dd><dl><dt>authoritative
nameserver, <a class="indexterm"
href="#s2-dns-introduction-nameservers">Nameserver
Types</a></dt><dt>primary (master) nameserver, <a
class="indexterm" href="#s2-dns-introduction-zones">Nameserver
Zones</a>, <a class="indexterm"
href="#s2-dns-introduction-nameservers">Nameserver Types<
/a></dt><dt>recursive nameserver, <a class="indexterm"
href="#s2-dns-introduction-nameservers">Nameserver
Types</a></dt><dt>secondary (slave) nameserver, <a
class="indexterm" href="#s2-dns-introduction-zones">Nameserver
Zones</a>, <a class="indexterm"
href="#s2-dns-introduction-nameservers">Nameserver
Types</a></dt></dl></dd><dt>utilities</dt><dd><dl><dt>dig,
<a class="indexterm" href="#s2-dns-introduction-bind">BIND as a
Nameserver</a>, <a class="indexterm"
href="#s2-bind-dig">Using the dig Utility</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 as a Nameserver</a>, <a
class="indexterm" href="#s2-bind-namedconf">Configuring the named
Service</a></dt><dt>rndc, <a class="indexterm"
href="#s2-dns-introduction-bind">BIND as a Nameserver</a>, <a
class="indexterm" href="#s2-bind-rndc">Using the rndc
Utility</a></dt></dl></dd><dt>zones</dt><dd><dl><dt>$INCLUDE
d
irective, <a class="indexterm"
href="#s3-bind-zone-directives">Common
Directives</a></dt><dt>$ORIGIN directive, <a
class="indexterm" href="#s3-bind-zone-directives">Common
Directives</a></dt><dt>$TTL directive, <a class="indexterm"
href="#s3-bind-zone-directives">Common
Directives</a></dt><dt>A (Address) resource record, <a
class="indexterm" href="#s4-bind-zone-rr">Common Resource
Records</a></dt><dt>CNAME (Canonical Name) resource record, <a
class="indexterm" href="#s4-bind-zone-rr">Common Resource
Records</a></dt><dt>comment tags, <a class="indexterm"
href="#s3-bind-zone-comm">Comment
Tags</a></dt><dt>description, <a class="indexterm"
href="#s2-dns-introduction-zones">Nameserver
Zones</a></dt><dt>example usage, <a class="indexterm"
href="#s4-bind-zone-examples-basic">A Simple Zone File</a>, <a
class="indexterm" href="#s3-bind-configuration-zone-reverse">A
Reverse Name Resolution Zone File</a></dt><dt>MX (Mail Exchange)
resource record, <a class="indexterm" href="#s4-bind-z
one-rr">Common Resource Records</a></dt><dt>NS (Nameserver)
resource record, <a class="indexterm"
href="#s4-bind-zone-rr">Common Resource
Records</a></dt><dt>PTR (Pointer) resource record, <a
class="indexterm" href="#s4-bind-zone-rr">Common Resource
Records</a></dt><dt>SOA (Start of Authority) resource record, <a
class="indexterm" href="#s4-bind-zone-rr">Common Resource
Records</a></dt></dl></dd></dl></dd><dt>block
devices, <a class="indexterm" href="#s2-proc-devices">
/proc/devices </a></dt><dd><dl><dt>(see also /proc/devices
)</dt><dt>definition of, <a class="indexterm"
href="#s2-proc-devices"> /proc/devices
</a></dt></dl></dd><dt>bonding (see channel
bonding)</dt><dt>boot
loader</dt><dd><dl><dt>verifying, <a
class="indexterm" href="#s1-kernel-boot-loader">Verifying the Boot
Loader</a></dt></dl></dd><dt>boot media, <a
class="indexterm" href="#s1-kernel-preparing">Preparing to
Upgrade</a></dt></dl></div><div
class="indexdiv"><h3>C</h3><dl><dt>ch-email
.fetchmailrc </dt><dd
<dl><dt>global options, <a class="indexterm"
href="#s3-email-mda-fetchmail-configuration-global">Global
Options</a></dt></dl></dd><dt>chage
command</dt><dd><dl><dt>forcing password expiration with, <a
class="indexterm" href="#s2-users-cmd-line">Command Line
Configuration</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>interface</dt><dd><dl><dt>configuration
of, <a class="indexterm"
href="#s2-networkscripts-interfaces-chan">Channel Bonding
Interfaces</a></dt></dl></dd><dt>parameters to bonded
interfaces, <a class="indexterm"
href="#s3-modules-bonding-directives">Bonding Module
Directives</a></dt></dl></dd><dt>channel bonding interface
(see kernel module)</dt><dt>character devices, <a
class="indexterm" href="#s2-proc-devices"> /proc/devices
</a></dt><dd><dl><dt>(see a
lso /proc/devices
)</dt><dt>definition of, <a class="indexterm"
href="#s2-proc-devices"> /proc/devices
</a></dt></dl></dd><dt>Configuration File Changes, <a
class="indexterm"
href="#sec-Preserving_Configuration_File_Changes">Preserving Configuration
File
Changes</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">Automating
System Tasks</a></dt><dt> cron , <a class="indexterm"
href="#s1-autotasks-cron-anacron">Cron and
Anacron</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="#s1-autotasks-additional-resources">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></dl></div><div
class="indexdiv"><h3>D</h3><dl><dt>date, <a
class="indexterm"
href="#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time
Configuration Tool</a>, <a class="indexterm"
href="#sect-Date_and_Time_Configuration-Command_Li
ne_Configuration-Date_and_Time">Configuring the Date and
Time</a></dt><dd><dl><dt>(see also Date and
Time)</dt></dl></dd><dt>Date and
Time</dt><dd><dl><dt>system date, <a
class="indexterm"
href="#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time
Configuration Tool</a></dt><dt>system time, <a
class="indexterm"
href="#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time
Configuration Tool</a></dt><dt>time zone settings, <a
class="indexterm"
href="#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time
Configuration Tool</a></dt></dl></dd><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>(see also
/proc/sys/net/ directory)</dt><dt>definition of, <a
class="indexterm" href="#s3-proc-sys-net"> /proc/sys/n
et/ </a></dt></dl></dd><dt> df , <a
class="indexterm" href="#s1-sysinfo-filesystems">File
Systems</a></dt><dt>DHCP, <a class="indexterm"
href="#ch-DHCP_Servers">DHCP
Servers</a></dt><dd><dl><dt>additional resources, <a
class="indexterm" href="#s1-dhcp-additional-resources">Additional
Resources</a></dt><dt>client configuration, <a
class="indexterm" href="#s1-dhcp-configuring-client">Configuring a
DHCP Client</a></dt><dt>command line options, <a
class="indexterm" href="#id619308">Starting and Stopping the
Server</a></dt><dt>connecting to, <a class="indexterm"
href="#s1-dhcp-configuring-client">Configuring a DHCP
Client</a></dt><dt>dhcpd.conf, <a class="indexterm"
href="#config-file">Configuration File</a></dt><dt>
dhcpd.leases , <a class="indexterm" href="#id619308">Starting
and Stopping the Server</a></dt><dt>dhcpd6.conf, <a
class="indexterm" href="#s1-dhcp_for_ipv6_dhcpv6">DHCP for IPv6
(DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm"
href="#s1-dhcp_for_ipv6_dhcpv6">DHCP fo
r IPv6 (DHCPv6)</a></dt><dt> dhcrelay , <a
class="indexterm" href="#dhcp-relay-agent">DHCP Relay
Agent</a></dt><dt>global parameters, <a class="indexterm"
href="#config-file">Configuration File</a></dt><dt>group,
<a class="indexterm" href="#config-file">Configuration
File</a></dt><dt>options, <a class="indexterm"
href="#config-file">Configuration File</a></dt><dt>reasons
for using, <a class="indexterm" href="#s1-dhcp-why">Why Use
DHCP?</a></dt><dt>Relay Agent, <a class="indexterm"
href="#dhcp-relay-agent">DHCP Relay
Agent</a></dt><dt>server configuration, <a
class="indexterm" href="#s1-dhcp-configuring-server">Configuring a
DHCP Server</a></dt><dt> shared-network , <a
class="indexterm" href="#config-file">Configuration
File</a></dt><dt>starting the server, <a class="indexterm"
href="#id619308">Starting and Stopping the
Server</a></dt><dt>stopping the server, <a
class="indexterm" href="#id619308">Starting and Stopping the
Server</a></dt><dt>subnet, <a class="indexterm"
href="
#config-file">Configuration
File</a></dt></dl></dd><dt>dhcpd.conf, <a
class="indexterm" href="#config-file">Configuration
File</a></dt><dt>dhcpd.leases, <a class="indexterm"
href="#id619308">Starting and Stopping the
Server</a></dt><dt> dhcrelay , <a class="indexterm"
href="#dhcp-relay-agent">DHCP Relay Agent</a></dt><dt>dig
(see BIND)</dt><dt>directory server (see
OpenLDAP)</dt><dt>DNS</dt><dd><dl><dt>definition,
<a class="indexterm" href="#ch-DNS_Servers">DNS
Servers</a></dt><dd><dl><dt>(see also
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 (see Denial of
Service attack)</dt><dt>drivers (see kernel module)</dt><dt>DSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">Generating Key
Pairs</a></dt></dl></dd><dt> du , <a
class="indexterm" href="#s1-sysinfo-filesyste
ms">File Systems</a></dt><dt>Dynamic Host Configuration
Protocol (see DHCP)</dt></dl></div><div
class="indexdiv"><h3>E</h3><dl><dt>email</dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="#s1-email-additional-resources">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="#s2-email-installed-docs">Installed
Documentation</a></dt><dt>related books, <a
class="indexterm" href="#s2-email-related-books">Related
Books</a></dt><dt>useful websites, <a class="indexterm"
href="#s2-email-useful-websites">Useful
Websites</a></dt></dl></dd><dt>Fetchmail, <a
class="indexterm"
href="#s2-email-mta-fetchmail">Fetchmail</a></dt><dt>history
of, <a class="indexterm" href="#ch-Mail_Servers">Mail
Servers</a></dt><dt>mail
server</dt><dd><dl><dt>Dovecot, <a class="indexterm"
href="#s3-mail-server-dovecot">Dovecot</a></dt></dl></dd><dt>Postfix,
<a class="indexterm"
href="#s2-email-mta-postfix">Postfix</a></dt><dt>Procmail,
<a class="indexterm" hr
ef="#s1-email-mda">Mail Delivery
Agents</a></dt><dt>program classifications, <a
class="indexterm" href="#s1-email-types">Email Program
Classifications</a></dt><dt>protocols, <a class="indexterm"
href="#s1-email-protocols">Email
Protocols</a></dt><dd><dl><dt>IMAP, <a
class="indexterm"
href="#s3-email-protocols-imap">IMAP</a></dt><dt>POP, <a
class="indexterm"
href="#s3-email-protocols-pop">POP</a></dt><dt>SMTP, <a
class="indexterm"
href="#s3-email-protocols-smtp">SMTP</a></dt></dl></dd><dt>security,
<a class="indexterm" href="#s2-email-security">Securing
Communication</a></dt><dd><dl><dt>clients, <a
class="indexterm" href="#s3-email-security-clients">Secure Email
Clients</a></dt><dt>servers, <a class="indexterm"
href="#s3-email-security-servers">Securing Email Client
Communications</a></dt></dl></dd><dt>Sendmail, <a
class="indexterm"
href="#s2-email-mta-sendmail">Sendmail</a></dt><dt>spam</dt><dd><dl><dt>filtering
out, <a class="indexterm" href="#s3-email-mda-spam">Spam Filter
s</a></dt></dl></dd><dt>types</dt><dd><dl><dt>Mail
Delivery Agent, <a class="indexterm"
href="#s2-email-types-mda">Mail Delivery
Agent</a></dt><dt>Mail Transport Agent, <a
class="indexterm" href="#s2-email-types-mta">Mail Transport
Agent</a></dt><dt>Mail User Agent, <a class="indexterm"
href="#s2-email-types-mua">Mail User
Agent</a></dt></dl></dd></dl></dd><dt>epoch,
<a class="indexterm" href="#s2-proc-stat"> /proc/stat
</a></dt><dd><dl><dt>(see also /proc/stat
)</dt><dt>definition of, <a class="indexterm"
href="#s2-proc-stat"> /proc/stat
</a></dt></dl></dd><dt>Ethernet (see
network)</dt><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>(see also /proc/execdomains
)</dt><dt>definition of, <a c
lass="indexterm" href="#s2-proc-execdomains"> /proc/execdomains
</a></dt></dl></dd><dt>expiration of password, forcing,
<a class="indexterm" href="#s2-users-cmd-line">Command Line
Configuration</a></dt></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">Finding RPM
Packages</a></dt></dl></dd><dt>feedback</dt><dd><dl><dt>contact
information for this manual, <a class="indexterm"
href="#sect-Preface-Feedback">Feedback</a></dt></dl></dd><dt>Fetchmail,
<a class="indexterm"
href="#s2-email-mta-fetchmail">Fetchmail</a></dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="#s1-email-additional-resources">Additional
Resources</a></dt><dt>command options, <a class="indexterm"
href="#s3-email-mda-fetchmail-commands">Fetchmail Command
Options</a></dt><dd><dl><dt>informational, <a
class="indexterm"
href="#s3-email-mda-fetchmail-commands-info">Informational or Debugging Op
tions</a></dt><dt>special, <a class="indexterm"
href="#s3-email-mda-fetchmail-commands-special">Special
Options</a></dt></dl></dd><dt>configuration options, <a
class="indexterm"
href="#s3-email-mda-fetchmail-configuration">Fetchmail Configuration
Options</a></dt><dd><dl><dt>global options, <a
class="indexterm"
href="#s3-email-mda-fetchmail-configuration-global">Global
Options</a></dt><dt>server options, <a class="indexterm"
href="#s3-email-mda-fetchmail-configuration-server">Server
Options</a></dt><dt>user options, <a class="indexterm"
href="#s3-email-fetchmail-configuration-user">User
Options</a></dt></dl></dd></dl></dd><dt>file
system</dt><dd><dl><dt>virtual (see proc file
system)</dt></dl></dd><dt>file systems, <a
class="indexterm" href="#s1-sysinfo-filesystems">File
Systems</a></dt><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 Comm
and</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> findsmb , <a
class="indexterm" href="#s3-samba-connect-share-cmdline">Command
Line</a></dt><dt> findsmb program, <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>FQDN (see fully qualified domain
name)</dt><dt>frame buffer device, <a class="indexterm"
href="#s2-proc-fb"> /proc/fb
</a></dt><dd><dl><dt>(see also /proc/fb
)</dt></dl></dd><dt> free , <a class="indexterm"
href="#s1-sysinfo-memory-usage">Memory
Usage</a></dt><dt>FTP, <a class="indexterm"
href="#s1-FTP">FTP</a></dt><dd><dl><dt>(see
also vsftpd )</dt><dt>active mode, <a class="indexterm"
href="#s3-ftp-protocol-multiport">Multiple Ports, Multiple
Modes</a></dt><dt>command port, <a class="indexterm"
href="#s3-ftp-protocol-multiport">Multiple Ports, Multiple
Modes</a></dt><dt>data port, <a class
="indexterm" href="#s3-ftp-protocol-multiport">Multiple Ports,
Multiple Modes</a></dt><dt>definition of, <a
class="indexterm"
href="#s1-FTP">FTP</a></dt><dt>introducing, <a
class="indexterm" href="#s2-ftp-protocol">The File Transfer
Protocol</a></dt><dt>passive mode, <a class="indexterm"
href="#s3-ftp-protocol-multiport">Multiple Ports, Multiple
Modes</a></dt><dt>server
software</dt><dd><dl><dt> Red Hat Content Accelerator , <a
class="indexterm" href="#s2-ftp-servers">FTP
Servers</a></dt><dt> vsftpd , <a class="indexterm"
href="#s2-ftp-servers">FTP
Servers</a></dt></dl></dd></dl></dd><dt>fully
qualified domain name, <a class="indexterm"
href="#s2-dns-introduction-zones">Nameserver
Zones</a></dt></dl></div><div
class="indexdiv"><h3>G</h3><dl><dt> GNOME System
Monitor , <a class="indexterm"
href="#s1-sysinfo-system-processes">System
Processes</a></dt><dt> gnome-system-log (see Log File Viewer
)</dt><dt> gnome-system-monitor , <a class="indexterm"
href="#s1-sysinfo-system-pro
cesses">System
Processes</a></dt><dt>GnuPG</dt><dd><dl><dt>checking
RPM package signatures, <a class="indexterm"
href="#s1-check-rpm-sig">Checking a Package's
Signature</a></dt></dl></dd><dt>group
configuration</dt><dd><dl><dt>adding groups, <a
class="indexterm" href="#s2-redhat-config-users-group-new">Adding a
New Group</a></dt><dt>filtering list of groups, <a
class="indexterm" href="#s1-users-configui">User Manager
Tool</a></dt><dt>groupadd, <a class="indexterm"
href="#s2-users-cmd-line">Command Line
Configuration</a></dt><dt>modify users in groups, <a
class="indexterm"
href="#s2-redhat-config-users-group-properties">Modifying Group
Properties</a></dt><dt>modifying group properties, <a
class="indexterm"
href="#s2-redhat-config-users-group-properties">Modifying Group
Properties</a></dt><dt>viewing list of groups, <a
class="indexterm" href="#s1-users-configui">User Manager
Tool</a></dt></dl></dd><dt>groups (see group
configuration)</dt><dd><dl><dt>additional resources, <a cl
ass="indexterm"
href="#s1-users-groups-additional-resources">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="#s2-users-groups-documentation">Installed
Documentation</a></dt></dl></dd><dt>GID, <a
class="indexterm" href="#ch-Managing_Users_and_Groups">Managing
Users and Groups</a></dt><dt>introducing, <a
class="indexterm" href="#ch-Managing_Users_and_Groups">Managing
Users and Groups</a></dt><dt>shared directories, <a
class="indexterm" href="#s2-users-groups-rationale">Group
Directories</a></dt><dt>standard, <a class="indexterm"
href="#s1-users-groups-standard-groups">Standard
Groups</a></dt><dt>tools for management
of</dt><dd><dl><dt>groupadd, <a class="indexterm"
href="#s1-users-tools">User and Group Management Tools</a>, <a
class="indexterm" href="#s1-users-groups-private-groups">User
Private Groups</a></dt><dt>system-config-users, <a
class="indexterm" href="#s1-users-groups-private-groups">User
Private Groups</a></dt><dt>User Ma
nager, <a class="indexterm" href="#s1-users-tools">User and
Group Management Tools</a></dt></dl></dd><dt>user private,
<a class="indexterm" href="#s1-users-groups-private-groups">User
Private Groups</a></dt></dl></dd><dt>GRUB boot
loader</dt><dd><dl><dt>configuration file, <a
class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring
the GRUB Boot Loader</a></dt><dt>configuring, <a
class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring
the GRUB Boot
Loader</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>H</h3><dl><dt>hardware</dt><dd><dl><dt>viewing,
<a class="indexterm"
href="#s1-sysinfo-hardware">Hardware</a></dt></dl></dd><dt>HTTP
server (see Apache HTTP Server)</dt><dt>httpd (see 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">Interfa
ce Control Scripts</a></dt><dt> ifup , <a
class="indexterm" href="#s1-networkscripts-control">Interface
Control
Scripts</a></dt><dt>information</dt><dd><dl><dt>about
your system, <a class="indexterm"
href="#ch-System_Monitoring_Tools">System Monitoring
Tools</a></dt></dl></dd><dt>initial RAM disk
image</dt><dd><dl><dt>verifying, <a class="indexterm"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">Verifying the Initial RAM
Disk Image</a></dt><dd><dl><dt>IBM eServer System i, <a
class="indexterm"
href="#sec-Verifying_the_Initial_RAM_Disk_Image">Verifying the Initial RAM
Disk
Image</a></dt></dl></dd></dl></dd><dt>initial
RPM repositories</dt><dd><dl><dt>installable packages, <a
class="indexterm" href="#s2-rpm-finding">Finding RPM
Packages</a></dt></dl></dd><dt> insmod , <a
class="indexterm" href="#sec-Loading_a_Module">Loading a
Module</a></dt><dd><dl><dt>(see also kernel
module)</dt></dl></dd><dt>installing package
groups</dt><dd><dl><dt>installing package groups with Package
Kit, <a class="indexterm"
href="#sec-Installing_and_Removing_Package_Groups">Installing and Removing
Package Groups</a></dt></dl></dd><dt>installing the kernel,
<a class="indexterm"
href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the
Kernel</a></dt></dl></div><div
class="indexdiv"><h3>K</h3><dl><dt>kdump</dt><dd><dl><dt>additional
resources</dt><dd><dl><dt>installed documents, <a
class="indexterm" href="#s2-kdump-resources-installed">Installed
Documentation</a></dt><dt>manual pages, <a
class="indexterm" href="#s2-kdump-resources-installed">Installed
Documentation</a></dt><dt>websites, <a class="indexterm"
href="#s2-kdump-resources-online">Useful
Websites</a></dt></dl></dd><dt>analyzing the dump (see
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>du
mp 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-gui-basic">The Basic Settings Tab</a>,
<a class="indexterm"
href="#s3-kdump-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-gui-enable">Enabling the Service</a>,
<a class="indexterm"
href="#s3-kdump-configuration-cli-enable">Enabling the
Service</a></dt><dt>known
issues</dt><dd><dl><dt>hpsa driver, <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>running the service, <a
class="indexterm"
href="#s3-kdump-configuration-cli-enable">Enabling the
Service</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">Downloading the
Upgraded Kernel</a></dt><dt>installing kernel packages, <a
class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually
Upgrading the Kernel</a></dt><dt>kernel packages, <a
class="indexterm" href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt><dt>package, <a class="indexterm"
href="#ch-Manually_Upgra
ding_the_Kernel">Manually Upgrading the
Kernel</a></dt><dt>performing kernel upgrade, <a
class="indexterm" href="#s1-kernel-perform-upgrade">Performing the
Upgrade</a></dt><dt>RPM package, <a class="indexterm"
href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the
Kernel</a></dt><dt>upgrade kernel available, <a
class="indexterm" href="#s1-kernel-download">Downloading the
Upgraded Kernel</a></dt><dd><dl><dt>Security Advisories,
<a class="indexterm" href="#s1-kernel-download">Downloading the
Upgraded Kernel</a></dt><dt>via Fedora Update System, <a
class="indexterm" href="#s1-kernel-download">Downloading the
Upgraded
Kernel</a></dt></dl></dd><dt>upgrading</dt><dd><dl><dt>preparing,
<a class="indexterm" href="#s1-kernel-preparing">Preparing to
Upgrade</a></dt><dt>working boot media, <a
class="indexterm" href="#s1-kernel-preparing">Preparing to
Upgrade</a></dt></dl></dd><dt>upgrading the kernel, <a
class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually
Upgra
ding the Kernel</a></dt></dl></dd><dt>Kernel Dump
Configuration (see 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-Persistent_Module_Loading">Persistent Module
Loading</a></dt><dt> /lib/modules/kernel_version/kernel/drivers/ , <a
class="indexterm" href="#sec-Loading_a_Module">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
">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">Persistent Module
Loading</a></dt><dt>for the current session, <a
class="indexterm" href="#sec-Loading_a_Module">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_M
odule_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">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">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">Overview of Kernel Packages</a>
</dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel
headers and makefiles, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>kernel-doc</dt><dd><dl><dt>
documentation files, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt>
C header files files, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>linux-firmware</dt><dd><dl><dt>
firmware files, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>perf</dt><dd><dl><dt>firmware
files, <a class="indexterm" href="#s1-kernel-packages">Overview
of Kernel
Packages</a></dt></dl></dd></dl></dd><dt>kernel
upgrading</dt><dd><dl><dt>preparing, <a
class="indexterm" href="#s1-kernel-preparing">Preparing to
Upgrade</a></dt></dl></dd><dt>keyboard configuration (see
Region and Language)</dt></dl></div><div
class="indexdiv"><
h3>L</h3><dl><dt>language configuration (see Region and
Language)</dt><dt>LDAP (see OpenLDAP)</dt><dt> Log File Viewer
</dt><dd><dl><dt>filtering, <a class="indexterm"
href="#s1-logfiles-viewing">Viewing Log
Files</a></dt><dt>monitoring, <a class="indexterm"
href="#s1-logfiles-examining">Monitoring Log
Files</a></dt><dt>searching, <a class="indexterm"
href="#s1-logfiles-viewing">Viewing Log
Files</a></dt></dl></dd><dt>log files, <a
class="indexterm" href="#ch-Viewing_and_Managing_Log_Files">Viewing
and Managing Log Files</a></dt><dd><dl><dt>(see also Log
Viewer )</dt><dt>additional
resources</dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="#s2-log-files-installed-docs">Installed
Documentation</a></dt><dt>useful websites, <a
class="indexterm" href="#s2-log-files-useful-websites">Useful
Websites</a></dt></dl></dd><dt>description, <a
class="indexterm" href="#ch-Viewing_and_Managing_Log_Files">Viewing
and Managing Log Files</a></dt><dt>locating, <a class="ind
exterm" href="#s1-logfiles-locating">Locating Log
Files</a></dt><dt>monitoring, <a class="indexterm"
href="#s1-logfiles-examining">Monitoring Log
Files</a></dt><dt>rotating, <a class="indexterm"
href="#s1-logfiles-locating">Locating Log
Files</a></dt><dt> rsyslogd daemon , <a class="indexterm"
href="#ch-Viewing_and_Managing_Log_Files">Viewing and Managing Log
Files</a></dt><dt>viewing, <a class="indexterm"
href="#s1-logfiles-viewing">Viewing Log
Files</a></dt></dl></dd><dt> Log Viewer
</dt><dd><dl><dt>refresh rate, <a class="indexterm"
href="#s1-logfiles-viewing">Viewing Log
Files</a></dt></dl></dd><dt> logrotate , <a
class="indexterm" href="#s1-logfiles-locating">Locating Log
Files</a></dt><dt> lsmod , <a class="indexterm"
href="#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded
Modules</a></dt><dd><dl><dt>(see also kernel
module)</dt></dl></dd><dt> lspci , <a
class="indexterm" href="#s2-proc-pci"> /proc/bus/pci
</a></dt></dl></div><div
class="indexdiv"><h3>M</
h3><dl><dt>Mail Delivery Agent (see email)</dt><dt>Mail
Transport Agent (see email) (see MTA)</dt><dt> Mail Transport Agent Switcher ,
<a class="indexterm" href="#s2-email-switchmail">Mail Transport
Agent (MTA) Configuration</a></dt><dt>Mail User Agent, <a
class="indexterm" href="#s2-email-switchmail">Mail Transport Agent
(MTA) Configuration</a> (see email)</dt><dt>MDA (see Mail Delivery
Agent)</dt><dt>memory usage, <a class="indexterm"
href="#s1-sysinfo-memory-usage">Memory Usage</a></dt><dt>
modinfo , <a class="indexterm"
href="#sec-Displaying_Information_About_a_Module">Displaying Information
About a Module</a></dt><dd><dl><dt>(see also kernel
module)</dt></dl></dd><dt> modprobe , <a
class="indexterm" href="#sec-Loading_a_Module">Loading a
Module</a>, <a class="indexterm"
href="#sec-Unloading_a_Module">Unloading a
Module</a></dt><dd><dl><dt>(see also kernel
module)</dt></dl></dd><dt>module (see kernel
module)</dt><dt>module parameters (see kernel module)</dt><dt>MTA
(see
Mail Transport Agent)</dt><dd><dl><dt>setting default, <a
class="indexterm" href="#s2-email-switchmail">Mail Transport Agent
(MTA) Configuration</a></dt><dt>switching with Mail Transport Agent
Switcher , <a class="indexterm" href="#s2-email-switchmail">Mail
Transport Agent (MTA)
Configuration</a></dt></dl></dd><dt>MUA, <a
class="indexterm" href="#s2-email-switchmail">Mail Transport Agent
(MTA) Configuration</a> (see Mail User Agent)</dt><dt>Multihomed
DHCP</dt><dd><dl><dt>host configuration, <a
class="indexterm" href="#sect-dns_Host_Configuration">Host
Configuration</a></dt><dt>server configuration, <a
class="indexterm"
href="#sect-Configuring_a_Multihomed_DHCP_Server">Configuring a Multihomed
DHCP Server</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></dl></div><div
class="indexdiv"><h3>N</h3><dl><dt>named (s
ee BIND)</dt><dt>nameserver (see DNS)</dt><dt> net program, <a
class="indexterm" href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>network</dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="#s1-networkscripts-resources">Additional
Resources</a></dt><dt>commands</dt><dd><dl><dt>
/sbin/ifdown , <a class="indexterm"
href="#s1-networkscripts-control">Interface Control
Scripts</a></dt><dt> /sbin/ifup , <a class="indexterm"
href="#s1-networkscripts-control">Interface Control
Scripts</a></dt></dl></dd><dt>configuration, <a
class="indexterm" href="#s1-networkscripts-interfaces">Interface
Configuration Files</a></dt><dt>configuration files, <a
class="indexterm" href="#s1-networkscripts-files">Network
Configuration Files</a></dt><dt>functions, <a
class="indexterm" href="#s1-networkscripts-functions">Network
Function Files</a></dt><dt>interface configuration files, <a
class="indexterm" href="#s1-networkscripts-interfaces">Interface
Configuration Files</a><
/dt><dt>interfaces</dt><dd><dl><dt>alias, <a
class="indexterm" href="#s2-networkscripts-interfaces-alias">Alias
and Clone Files</a></dt><dt>channel bonding, <a
class="indexterm" href="#s2-networkscripts-interfaces-chan">Channel
Bonding Interfaces</a></dt><dt>clone, <a class="indexterm"
href="#s2-networkscripts-interfaces-alias">Alias and Clone
Files</a></dt><dt>dialup, <a class="indexterm"
href="#s2-networkscripts-interfaces-ppp0">Dialup
Interfaces</a></dt><dt>Ethernet, <a class="indexterm"
href="#s2-networkscripts-interfaces-eth0">Ethernet
Interfaces</a></dt></dl></dd><dt>scripts, <a
class="indexterm" href="#ch-Network_Interfaces">Network
Interfaces</a></dt></dl></dd><dt>Network Time Protocol,
<a class="indexterm"
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Configuring
the Network Time Protocol</a></dt><dd><dl><dt>ntpd, <a
class="indexterm"
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol"
Configuring the Network Time
Protocol</a></dt><dt>ntpdate, <a class="indexterm"
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Configuring
the 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> nmblookup program, <a
class="indexterm" href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>NTP (see Network Time
Protocol)</dt><dt>ntpd, <a class="indexterm"
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Configuring
the Network Time Protocol</a></dt><dt>ntpdate, <a
class="indexterm"
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Configuring
the Network Time Protocol</a></dt></dl></div><div
class="indexdiv"><h3>O</h3><dl><dt>OpenLDAP</dt><dd><dl><dt>checking
status, <a class="indexterm" href="#s3-ldap-r
unning-status">Checking the Service Status</a></dt><dt>client
applications, <a class="indexterm"
href="#s3-ldap-packages-applications">Overview of Common LDAP Client
Applications</a></dt><dt>configuration</dt><dd><dl><dt>database,
<a class="indexterm"
href="#s3-ldap-configuration-database">Changing the Database-Specific
Configuration</a></dt><dt>global, <a class="indexterm"
href="#s3-ldap-configuration-global">Changing the Global
Configuration</a></dt><dt>overview, <a class="indexterm"
href="#s3-ldap-setup">OpenLDAP Server
Setup</a></dt></dl></dd><dt>directives</dt><dd><dl><dt>olcAllows,
<a class="indexterm"
href="#s3-ldap-configuration-global">Changing the Global
Configuration</a></dt><dt>olcConnMaxPending, <a
class="indexterm" href="#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcConnMaxPendingAuth, <a
class="indexterm" href="#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcDisallows, <a
class="indexterm" href=
"#s3-ldap-configuration-global">Changing the Global
Configuration</a></dt><dt>olcIdleTimeout, <a
class="indexterm" href="#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcLogFile, <a
class="indexterm" href="#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcReadOnly, <a
class="indexterm" href="#s3-ldap-configuration-database">Changing
the Database-Specific Configuration</a></dt><dt>olcReferral, <a
class="indexterm" href="#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcRootDN, <a
class="indexterm" href="#s3-ldap-configuration-database">Changing
the Database-Specific Configuration</a></dt><dt>olcRootPW, <a
class="indexterm" href="#s3-ldap-configuration-database">Changing
the Database-Specific Configuration</a></dt><dt>olcSuffix, <a
class="indexterm" href="#s3-ldap-configuration-database">Changing
the Database-Specific Configuration</a></dt><dt>olcWriteTimeout, <a
class="indexterm" href="
#s3-ldap-configuration-global">Changing the Global
Configuration</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/openldap/slapd.d/,
<a class="indexterm" href="#s2-ldap-configuration">Configuring
an OpenLDAP
Server</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>features, <a
class="indexterm" href="#s3-ldap-features">OpenLDAP
Features</a></dt><dt>files</dt><dd><dl><dt>/etc/openldap/ldap.conf,
<a class="indexterm" href="#s2-ldap-configuration">Configuring
an OpenLDAP Server</a></dt><dt>/etc/openldap/slapd.d/cn=config.ldif,
<a class="indexterm"
href="#s3-ldap-configuration-global">Changing the Global
Configuration</a></dt><dt>/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif,
<a class="indexterm"
href="#s3-ldap-configuration-database">Changing the Database-Specific
Configuration</a></dt></dl></dd><dt>installation, <a
class="indexterm" href="#s2-ldap-installation
">Installing the OpenLDAP Suite</a></dt><dt>migrating
authentication information, <a class="indexterm"
href="#s3-ldap-migrationtools">Migrating Old Authentication Information to
LDAP Format</a></dt><dt>packages, <a class="indexterm"
href="#s2-ldap-installation">Installing the OpenLDAP
Suite</a></dt><dt>restarting, <a class="indexterm"
href="#s3-ldap-running-restarting">Restarting the
Service</a></dt><dt>running, <a class="indexterm"
href="#s3-ldap-running-starting">Starting the
Service</a></dt><dt>schema, <a class="indexterm"
href="#s3-ldap-configuration-schema">Extending
Schema</a></dt><dt>stopping, <a class="indexterm"
href="#s3-ldap-running-stopping">Stopping the
Service</a></dt><dt>terminology</dt><dd><dl><dt>attribute,
<a class="indexterm" href="#s3-ldap-terminology">LDAP
Terminology</a></dt><dt>entry, <a class="indexterm"
href="#s3-ldap-terminology">LDAP Terminology</a></dt><dt>
LDIF , <a class="indexterm" href="#s3-ldap-terminology">LDAP
Terminology</a></dt></dl></dd>
<dt>utilities, <a class="indexterm"
href="#s3-ldap-packages-openldap-servers">Overview of OpenLDAP Server
Utilities</a>, <a class="indexterm"
href="#s3-ldap-packages-openldap-clients">Overview of OpenLDAP Client
Utilities</a></dt></dl></dd><dt>OpenSSH, <a
class="indexterm" href="#ch-OpenSSH">OpenSSH</a>, <a
class="indexterm" href="#s2-ssh-features">Main
Features</a></dt><dd><dl><dt>(see also
SSH)</dt><dt>additional resources, <a class="indexterm"
href="#s1-openssh-additional-resources">Additional
Resources</a></dt><dt>client, <a class="indexterm"
href="#s1-ssh-clients">OpenSSH
Clients</a></dt><dd><dl><dt> scp , <a
class="indexterm" href="#s2-ssh-clients-scp">Using the scp
Utility</a></dt><dt> sftp , <a class="indexterm"
href="#s2-ssh-clients-sftp">Using the sftp
Utility</a></dt><dt> ssh , <a class="indexterm"
href="#s2-ssh-clients-ssh">Using the ssh
Utility</a></dt></dl></dd><dt>DSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-ge
nerating">Generating Key
Pairs</a></dt></dl></dd><dt>RSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">Generating Key
Pairs</a></dt></dl></dd><dt>RSA Version 1
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">Generating Key
Pairs</a></dt></dl></dd><dt>server, <a
class="indexterm" href="#s2-ssh-configuration-sshd">Starting an
OpenSSH Server</a></dt><dd><dl><dt>starting, <a
class="indexterm" href="#s2-ssh-configuration-sshd">Starting an
OpenSSH Server</a></dt><dt>stopping, <a class="indexterm"
href="#s2-ssh-configuration-sshd">Starting an OpenSSH
Server</a></dt></dl></dd><dt> ssh-add , <a
class="indexterm"
href="#s3-ssh-configuration-keypairs-agent">Configuring
ssh-agent</a></dt><dt> ssh-agent , <a class="indexterm"
href="#s3-ssh-configuration-keypairs-agent">Configuring
ssh-agent</a></dt><dt>ssh-keygen</dt><dd><dl><dt>DSA,
<a class="indexterm" href="#s3-ssh-configura
tion-keypairs-generating">Generating Key Pairs</a></dt><dt>RSA,
<a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">Generating Key
Pairs</a></dt><dt>RSA Version 1, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">Generating Key
Pairs</a></dt></dl></dd><dt>using key-based authentication,
<a class="indexterm" href="#s2-ssh-configuration-keypairs">Using
a Key-Based
Authentication</a></dt></dl></dd><dt>OpenSSL</dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="#s1-openssh-additional-resources">Additional
Resources</a></dt><dt>SSL (see SSL)</dt><dt>TLS (see
TLS)</dt></dl></dd><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>package</dt><dd><
dl><dt>kernel RPM, <a class="indexterm"
href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the
Kernel</a></dt></dl></dd><dt>PackageKit, <a
class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dd><dl><dt>adding
and removing, <a class="indexterm"
href="#sec-Using_Add_Remove_Software">Using Add/Remove
Software</a></dt><dt>architecture, <a class="indexterm"
href="#sec-PackageKit_Architecture">PackageKit
Architecture</a></dt><dt>installing and removing package groups, <a
class="indexterm"
href="#sec-Installing_and_Removing_Package_Groups">Installing and Removing
Package Groups</a></dt><dt>installing packages , <a
class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dt>managing
packages , <a class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dt>PolicyKit</dt><dd><dl><dt>authentication,
<a class="indexterm"
href="#sec-Updating_Packages_with_Software_Update">Updating Packages with
Software Update</a></dt></dl></dd><dt>uninstalling packages
, <a class=
"indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dt>updating
packages , <a class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dt>viewing
packages , <a class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dt>viewing
transaction log, <a class="indexterm"
href="#sec-Viewing_the_Transaction_Log">Viewing the Transaction
Log</a></dt></dl></dd><dt>packages</dt><dd><dl><dt>adding
and removing with PackageKit, <a class="indexterm"
href="#sec-Using_Add_Remove_Software">Using Add/Remove
Software</a></dt><dt>dependencies, <a class="indexterm"
href="#s3-rpm-unresolved-dependency">Unresolved
Dependency</a></dt><dt>determining file ownership with, <a
class="indexterm" href="#s1-rpm-impressing">Practical and Common
Examples of RPM Usage</a></dt><dt>displaying packages with
Yum</dt><dd><dl><dt>yum info, <a class="indexterm"
href="#sec-Displaying_Package_Information">Displaying Package
Information</a></dt></dl></dd><dt>filtering with PackageKit,
<a class="indexterm" href=
"#sec-Finding_Packages_with_Filters">Finding Packages with
Filters</a></dt><dd><dl><dt>Development, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt><dt>Free, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt><dt>Hide Subpackages, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt><dt>Installed, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt><dt>No Filter, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt><dt>Only Available, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt><dt>Only Development, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt><dt>Only End User Files, <a
class="indexterm" href="#sec-Finding_Packages_with
_Filters">Finding Packages with Filters</a></dt><dt>Only
Graphical, <a class="indexterm"
href="#sec-Finding_Packages_with_Filters">Finding Packages with
Filters</a></dt><dt>Only Installed, <a class="indexterm"
href="#sec-Finding_Packages_with_Filters">Finding Packages with
Filters</a></dt><dt>Only Native Packages, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt><dt>Only Newest Packages, <a
class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding
Packages with Filters</a></dt></dl></dd><dt>filtering with
PackageKit for packages, <a class="indexterm"
href="#sec-Finding_Packages_with_Filters">Finding Packages with
Filters</a></dt><dt>finding deleted files from, <a
class="indexterm" href="#s1-rpm-impressing">Practical and Common
Examples of RPM Usage</a></dt><dt>finding RPM packages, <a
class="indexterm" href="#s2-rpm-finding">Finding RPM
Packages</a></dt><dt>iFedora installation media, <a
class="indexterm" href="#s
2-rpm-finding">Finding RPM Packages</a></dt><dt>initial RPM
repositories, <a class="indexterm"
href="#s2-rpm-finding">Finding RPM
Packages</a></dt><dt>installing a package group with Yum, <a
class="indexterm" href="#sec-Installing">Installing
Packages</a></dt><dt>installing and removing package groups, <a
class="indexterm"
href="#sec-Installing_and_Removing_Package_Groups">Installing and Removing
Package Groups</a></dt><dt>installing packages with PackageKit, <a
class="indexterm" href="#ch-PackageKit">PackageKit</a>, <a
class="indexterm"
href="#sec-Installing_and_Removing_Packages_and_Dependencies">Installing and
Removing Packages (and
Dependencies)</a></dt><dd><dl><dt>dependencies, <a
class="indexterm"
href="#sec-Installing_and_Removing_Packages_and_Dependencies">Installing and
Removing Packages (and
Dependencies)</a></dt></dl></dd><dt>installing RPM, <a
class="indexterm" href="#sec-Installing_and_Upgrading">Installing
and Upgrading</a></dt><dt>installing with Yum, <a class
="indexterm" href="#sec-Installing">Installing
Packages</a></dt><dt>kernel</dt><dd><dl><dt>for
single, multicore and multiprocessor systems, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel
headers and makefiles, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>kernel-doc</dt><dd><dl><dt>
documentation files, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt>
C header files files, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>linux-firmware</dt><dd><dl><dt>
firmware files, <a class="indexterm"
href="#s1-kernel-packages">Overview of Kernel
Packages</a></dt></dl></dd><dt>listing packages with
Yum</dt><dd><dl><dt> Glob expressions, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum grou
plist, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum list all, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum list available, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum list installed, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum repolist, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum search, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt></dl></dd><dt>locating documentation for,
<a class="indexterm" href="#s1-rpm-impressing">Practical and
Common Examples of RPM Usage</a></dt><dt>managing packages with
PackageKit, <a class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dt>obtaining list
of files, <a class="indexterm"
href="#s1-rpm-impressing">Practical and Common Examples of RPM
Usage</a></dt><dt>packages and package groups, <a
class="indexterm" href="#sec
-Packages_and_Package_Groups">Packages and Package
Groups</a></dt><dt>perf</dt><dd><dl><dt>
firmware files, <a class="indexterm"
href="#s1-kernel-packages">Overview of 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>removing, <a
class="indexterm"
href="#s2-rpm-uninstalling">Uninstalling</a></dt><dt>removing
package groups with Yum, <a class="indexterm"
href="#sec-Removing">Removing Packages</a></dt><dt>removing
packages with PackageKit, <a class="indexterm"
href="#sec-Installing_and_Removing_Packages_and_Dependencies">Installing and
Removing Packages (and Dependencies)</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">Package
Already Installed</a></dt><dt>configuration file changes, <a
class="indexterm"
href="#sec-Configuration_File_Changes">Configuration File
Changes</a></dt
<dt>conflict, <a class="indexterm"
href="#s3-rpm-conflicting-files">Conflicting
Files</a></dt><dt>failed dependencies, <a class="indexterm"
href="#s3-rpm-unresolved-dependency">Unresolved
Dependency</a></dt><dt>freshening, <a class="indexterm"
href="#s2-rpm-freshening">Freshening</a></dt><dt>pristine
sources, <a class="indexterm" href="#s1-rpm-design">RPM Design
Goals</a></dt><dt>querying, <a class="indexterm"
href="#s2-rpm-querying">Querying</a></dt><dt>removing,
<a class="indexterm"
href="#s2-rpm-uninstalling">Uninstalling</a></dt><dt>source
and binary packages, <a class="indexterm"
href="#ch-RPM">RPM</a></dt><dt>tips, <a
class="indexterm" href="#s1-rpm-impressing">Practical and Common
Examples of RPM Usage</a></dt><dt>uninstalling, <a
class="indexterm"
href="#s2-rpm-uninstalling">Uninstalling</a></dt><dt>verifying,
<a class="indexterm"
href="#s2-rpm-verifying">Verifying</a></dt></dl></dd><dt>searching
packages with Yum</dt><dd><dl><dt>yum search, <a
class="indexterm" hre
f="#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>setting packages with
PackageKit</dt><dd><dl><dt>checking interval, <a
class="indexterm"
href="#sec-Setting_preferences_for_checking_for_updates">Setting the
Update-Checking Interval</a></dt></dl></dd><dt>uninstalling
packages with PackageKit, <a class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dt>uninstalling
packages with Yum, <a class="indexterm"
href="#sec-Removing">Removing
Packages</a></dt><dd><dl><dt>yum remove package_name, <a
class="indexterm" href="#sec-Removing">Removing
Packages</a></dt></dl></dd><dt>updating currently installed
packages</dt><dd><dl><dt>available updates, <a
class="indexterm"
href="#sec-Updating_Packages_with_Software_Update">Updating Packages with
Software Update</a></dt></dl></dd><dt>updating packages with
PackageKit, <a class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dd><dl><dt>PolicyKit,
<a class="indexterm" href="#sec-Updating_Packages_with_Software_U
pdate">Updating Packages with Software
Update</a></dt><dt>Software Update, <a class="indexterm"
href="#sec-Updating_Packages_with_Software_Update">Updating Packages with
Software Update</a></dt></dl></dd><dt>upgrading RPM, <a
class="indexterm" href="#sec-Installing_and_Upgrading">Installing
and Upgrading</a></dt><dt>viewing packages with PackageKit, <a
class="indexterm"
href="#ch-PackageKit">PackageKit</a></dt><dt>viewing
transaction log, <a class="indexterm"
href="#sec-Viewing_the_Transaction_Log">Viewing the Transaction
Log</a></dt><dt>viewing Yum repositories with PackageKit, <a
class="indexterm"
href="#sec-Setting_preferences_for_software_sources">Setting the Software
Sources</a></dt><dt>Yum instead of RPM, <a
class="indexterm"
href="#ch-RPM">RPM</a></dt></dl></dd><dt>password</dt><dd><dl><dt>aging,
<a class="indexterm" href="#s2-users-cmd-line">Command Line
Configuration</a></dt><dt>expire, <a class="indexterm"
href="#s2-users-cmd-line">Command Line Configuration</a></d
t></dl></dd><dt>passwords</dt><dd><dl><dt>shadow,
<a class="indexterm"
href="#s1-users-groups-shadow-utilities">Shadow
Passwords</a></dt></dl></dd><dt> pdbedit program, <a
class="indexterm" href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>PolicyKit, <a class="indexterm"
href="#sec-Updating_Packages_with_Software_Update">Updating Packages with
Software Update</a></dt><dt>Postfix, <a class="indexterm"
href="#s2-email-mta-postfix">Postfix</a></dt><dd><dl><dt>default
installation, <a class="indexterm"
href="#s3-email-mta-postfix-default">The Default Postfix
Installation</a></dt></dl></dd><dt>postfix, <a
class="indexterm" href="#s2-email-switchmail">Mail Transport Agent
(MTA) Configuration</a></dt><dt>primary nameserver (see
BIND)</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> /pro
c/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" href="#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/filesyst
ems , <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 c
lass="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 cl
ass="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>(see also 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 (see 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/sysvipc/ 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">References</a></dt><dd><dl><dt>installed
documentation, <a class="indexterm"
href="#s2-proc-installed-documentation">Installed
Documentation</a></dt><dt>useful websites, <a
class="indexterm" href="#s2-proc-useful-websites">Useful
Websites</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 within, 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>processes, <a
class="indexterm" href="#s1-sysinfo-system-processes">System
Processes</a></dt><dt>Procmail, <a class="indexterm"
href="#s1-email-mda">Mail Delivery
Agents</a></dt><dd><dl><dt>additional resources, <a
class="indexterm" href="#s1-email-additional-resources">Additional
Resources</a></dt><dt>configuration, <a class="indexterm"
h
ref="#s2-email-procmail-configuration">Procmail
Configuration</a></dt><dt>recipes, <a class="indexterm"
href="#s2-email-procmail-recipes">Procmail
Recipes</a></dt><dd><dl><dt>delivering, <a
class="indexterm"
href="#s2-email-procmail-recipes-delivering">Delivering vs. Non-Delivering
Recipes</a></dt><dt>examples, <a class="indexterm"
href="#s3-email-procmail-recipes-examples">Recipe
Examples</a></dt><dt>flags, <a class="indexterm"
href="#s3-email-procmail-recipes-flags">Flags</a></dt><dt>local
lockfiles, <a class="indexterm"
href="#s3-email-procmail-recipes-lockfile">Specifying a Local
Lockfile</a></dt><dt>non-delivering, <a class="indexterm"
href="#s2-email-procmail-recipes-delivering">Delivering vs. Non-Delivering
Recipes</a></dt><dt>SpamAssassin, <a class="indexterm"
href="#s3-email-mda-spam">Spam Filters</a></dt><dt>special
actions, <a class="indexterm"
href="#s3-email-procmail-recipes-special">Special Conditions and
Actions</a></dt><dt>special conditions, <a class="indext
erm" href="#s3-email-procmail-recipes-special">Special Conditions and
Actions</a></dt></dl></dd></dl></dd><dt> ps ,
<a class="indexterm" href="#s1-sysinfo-system-processes">System
Processes</a></dt></dl></div><div
class="indexdiv"><h3>R</h3><dl><dt>RAM, <a
class="indexterm" href="#s1-sysinfo-memory-usage">Memory
Usage</a></dt><dt> rcp , <a class="indexterm"
href="#s2-ssh-clients-scp">Using the scp
Utility</a></dt><dt>recursive nameserver (see
BIND)</dt><dt>Region and
Language</dt><dd><dl><dt>keyboard configuration, <a
class="indexterm"
href="#sect-Language_and_Keyboard_Configuration-Layouts">Changing the
Keyboard Layout</a></dt><dt>language configuration, <a
class="indexterm"
href="#sect-Language_and_Keyboard_Configuration-Language">Changing the
Language</a></dt></dl></dd><dt>removing package
groups</dt><dd><dl><dt>removing package groups with PackageKit,
<a class="indexterm"
href="#sec-Installing_and_Removing_Package_Groups">Installing and Removing
Package Groups</a></dt></
dl></dd><dt>resource record (see BIND)</dt><dt> rmmod , <a
class="indexterm" href="#sec-Unloading_a_Module">Unloading a
Module</a></dt><dd><dl><dt>(see also kernel
module)</dt></dl></dd><dt>rndc (see BIND)</dt><dt>root
nameserver (see BIND)</dt><dt> rpcclient program, <a
class="indexterm" href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>RPM, <a class="indexterm"
href="#ch-RPM">RPM</a></dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="#s1-rpm-additional-resources">Additional
Resources</a></dt><dt>already installed, <a
class="indexterm" href="#s3-rpm-errors">Package Already
Installed</a></dt><dt>basic modes, <a class="indexterm"
href="#s1-rpm-using">Using RPM</a></dt><dt>book about,
<a class="indexterm" href="#s2-rpm-related-books">Related
Books</a></dt><dt>checking package signatures, <a
class="indexterm" href="#s1-check-rpm-sig">Checking a Package's
Signature</a></dt><dt>configuration file changes, <a
class="indexterm" href="#sec-Configuration
_File_Changes">Configuration File
Changes</a></dt><dd><dl><dt>conf.rpmsave, <a
class="indexterm"
href="#sec-Configuration_File_Changes">Configuration File
Changes</a></dt></dl></dd><dt>conflicts, <a
class="indexterm" href="#s3-rpm-conflicting-files">Conflicting
Files</a></dt><dt>dependencies, <a class="indexterm"
href="#s3-rpm-unresolved-dependency">Unresolved
Dependency</a></dt><dt>design goals, <a class="indexterm"
href="#s1-rpm-design">RPM Design
Goals</a></dt><dd><dl><dt>powerful querying, <a
class="indexterm" href="#s1-rpm-design">RPM Design
Goals</a></dt><dt>system verification, <a class="indexterm"
href="#s1-rpm-design">RPM Design
Goals</a></dt><dt>upgradability, <a class="indexterm"
href="#s1-rpm-design">RPM Design
Goals</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>documentation with, <a
class="indexterm" href="#s1-rpm-impressing">Practical and Common
Examp
les of RPM Usage</a></dt><dt>failed dependencies, <a
class="indexterm" href="#s3-rpm-unresolved-dependency">Unresolved
Dependency</a></dt><dt>file
conflicts</dt><dd><dl><dt>resolving, <a
class="indexterm" href="#s3-rpm-conflicting-files">Conflicting
Files</a></dt></dl></dd><dt>file name, <a
class="indexterm" href="#sec-Installing_and_Upgrading">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>finding RPM packages, <a
class="indexterm" href="#s2-rpm-finding">Finding RPM
Packages</a></dt><dt>freshening, <a class="indexterm"
href="#s2-rpm-freshening">Freshening</a></dt><dt>GnuPG,
<a class="indexterm" href="#s1-check-rpm-sig">Checking a
Package's Signature</a></dt><dt>installing, <a
class="indexterm" href="#sec-Installing_and_Upgrading">Installing
and Upgrading</a></dt><dt>md5sum, <a class="indexterm"
href="#s1-check-rpm-sig">Checking a Package's Signature</a></d
t><dt>querying, <a class="indexterm"
href="#s2-rpm-querying">Querying</a></dt><dt>querying for
file list, <a class="indexterm"
href="#s1-rpm-impressing">Practical and Common Examples of RPM
Usage</a></dt><dt>querying uninstalled packages, <a
class="indexterm" href="#s1-rpm-impressing">Practical and Common
Examples of RPM Usage</a></dt><dt>tips, <a
class="indexterm" href="#s1-rpm-impressing">Practical and Common
Examples of RPM Usage</a></dt><dt>uninstalling, <a
class="indexterm"
href="#s2-rpm-uninstalling">Uninstalling</a></dt><dt>upgrading,
<a class="indexterm"
href="#sec-Installing_and_Upgrading">Installing and
Upgrading</a></dt><dt>verifying, <a class="indexterm"
href="#s2-rpm-verifying">Verifying</a></dt><dt>website,
<a class="indexterm" href="#s2-rpm-useful-websites">Useful
Websites</a></dt></dl></dd><dt>RPM Package Manager (see
RPM)</dt><dt>RSA keys</dt><dd><dl><dt>generating,
<a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a
</dt></dl></dd><dt>RSA Version 1
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="#s3-ssh-configuration-keypairs-generating">Generating Key
Pairs</a></dt></dl></dd><dt> rsyslog , <a
class="indexterm" href="#ch-Viewing_and_Managing_Log_Files">Viewing
and Managing Log Files</a></dt></dl></div><div
class="indexdiv"><h3>S</h3><dl><dt>Samba (see
Samba)</dt><dd><dl><dt>Abilities, <a
class="indexterm" href="#s3-samba-abilities">Samba
Features</a></dt><dt>Account Information Databases, <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dd><dl><dt> ldapsam , <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> ldapsam_compat , <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> mysqlsam , <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt>Plain Text, <a
class="indexterm"
href="#s2-samba-account-info-dbs">Samba
Account Information Databases</a></dt><dt> smbpasswd , <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> tdbsam , <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> xmlsam , <a
class="indexterm" href="#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt></dl></dd><dt>Additional
Resources, <a class="indexterm"
href="#s2-samba-resources">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="#s3-samba-resources-installed">Installed
Documentation</a></dt><dt>related books, <a
class="indexterm" href="#s3-samba-resources-published">Related
Books</a></dt><dt>useful websites, <a class="indexterm"
href="#s3-samba-resources-community">Useful
Websites</a></dt></dl></dd><dt>Backward Compatible Database
Back Ends, <a class="indexterm"
href="#s2-samba-account-info-dbs">Samba Account Info
rmation Databases</a></dt><dt>Browsing, <a
class="indexterm" href="#s2-samba-network-browsing">Samba Network
Browsing</a></dt><dt>configuration, <a class="indexterm"
href="#s2-samba-configuring">Configuring a Samba Server</a>, <a
class="indexterm" href="#s3-samba-configuring-cmdline">Command Line
Configuration</a></dt><dd><dl><dt>default, <a
class="indexterm" href="#s2-samba-configuring">Configuring a Samba
Server</a></dt></dl></dd><dt>CUPS Printing Support, <a
class="indexterm" href="#s2-samba-cups">Samba with CUPS Printing
Support</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>daemon, <a
class="indexterm" href="#s2-samba-daemons">Samba Daemons and
Related Services</a></dt><dd><dl><dt>nmbd, <a
class="indexterm" href="#s3-samba-services">Samba
Daemons</a></dt><dt>overview, <a class="indexterm"
href="#s3-samba-services">Samba Daemons</a></dt><dt>smbd,
<a class="indexterm" href="#s3-samba-se
rvices">Samba Daemons</a></dt><dt>winbindd, <a
class="indexterm" href="#s3-samba-services">Samba
Daemons</a></dt></dl></dd><dt>encrypted passwords, <a
class="indexterm" href="#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt><dt> findsmb , <a class="indexterm"
href="#s3-samba-connect-share-cmdline">Command
Line</a></dt><dt>graphical configuration, <a
class="indexterm" href="#s3-samba-configuring-gui">Graphical
Configuration</a></dt><dt>Introduction, <a
class="indexterm" href="#samba-rgs-overview">Introduction to
Samba</a></dt><dt>Network Browsing, <a class="indexterm"
href="#s2-samba-network-browsing">Samba Network
Browsing</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 Account
Information Databases</a></dt
<dt>Programs, <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dd><dl><dt> findsmb , <a
class="indexterm" href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> net , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> nmblookup , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> pdbedit , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> rpcclient , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbcacls , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbclient , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbcontrol , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbpasswd , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution Programs</
a></dt><dt> smbspool , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbstatus , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbtar , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> testparm , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> wbinfo , <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt></dl></dd><dt>Reference, <a
class="indexterm"
href="#s1-Samba">Samba</a></dt><dt>Security Modes, <a
class="indexterm" href="#s2-samba-security-modes">Samba Security
Modes</a></dt><dd><dl><dt>Active Directory Security Mode,
<a class="indexterm" href="#s3-samba-ads-security-mode">Active
Directory Security Mode (User-Level Security)</a></dt><dt>Domain
Security Mode, <a class="indexterm"
href="#s3-samba-domain-security-mode">Domain Security Mode (User-Level
Security)</a></dt><dt>Server Sec
urity Mode, <a class="indexterm"
href="#s3-samba-server-security-mode">Server Security Mode (User-Level
Security)</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">User-Level
Security</a></dt></dl></dd><dt>Server Types, <a
class="indexterm" href="#s2-samba-servers">Samba Server Types and
the smb.conf File</a></dt><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">Domain Member
Server</a></dt><dt>Stand Alone, <a class="indexterm"
href="#s3-samba-standalone">Stand-alone
Server</a></dt></dl></dd><dt>service</dt><dd><dl><dt>conditional
restarting, <a class="indexterm"
href="#s2-samba-startstop">Starting and Stopping
Samba</a></dt><dt>reloading, <a class="indexterm"
href="#s2-samba-startstop">S
tarting and Stopping Samba</a></dt><dt>restarting, <a
class="indexterm" href="#s2-samba-startstop">Starting and Stopping
Samba</a></dt><dt>starting, <a class="indexterm"
href="#s2-samba-startstop">Starting and Stopping
Samba</a></dt><dt>stopping, <a class="indexterm"
href="#s2-samba-startstop">Starting and Stopping
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">Command
Line</a></dt><dt>connecting to with Nautilus, <a
class="indexterm" href="#s2-samba-connect-share">Connecting to a
Samba Share</a></dt><dt>mounting, <a class="indexterm"
href="#s2-samba-mounting">Mounting the
Share</a></dt></dl></dd><dt>smb.conf, <a
class="indexterm" href="#s2-samba-servers">Samba Server Types and
the smb.conf File</a></dt><dd><dl><dt>Active Directory
Member Server example, <a class="indexterm"
href="#s4-samba-domain-member-ads">Active Directory Domain Member
Server</a></dt><dt>Anonymous Print Ser
ver example, <a class="indexterm"
href="#s4-samba-standalone-anonprint">Anonymous Print
Server</a></dt><dt>Anonymous Read Only example, <a
class="indexterm"
href="#s4-samba-standalone-anonreadonly">Anonymous
Read-Only</a></dt><dt>Anonymous Read/Write example, <a
class="indexterm"
href="#s4-samba-standalone-anonreadwrite">Anonymous
Read/Write</a></dt><dt>NT4-style Domain Member example, <a
class="indexterm" href="#s4-samba-domain-member-nt4">Windows
NT4-based Domain Member Server</a></dt><dt>PDC using Active Directory,
<a class="indexterm" href="#samba-rgs-pdc-ads">Primary Domain
Controller (PDC) with Active Directory</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">Secure Read/Write File and Print
Server</a></dt></dl></dd><dt> smbclient , <a
class="indexterm" href="#s3-samba-connect-share-
cmdline">Command Line</a></dt><dt>WINS, <a
class="indexterm" href="#s3-samba-wins">WINS (Windows Internet Name
Server)</a></dt><dt>with Windows NT 4.0, 2000, ME, and XP, <a
class="indexterm" href="#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd><dt> scp (see
OpenSSH)</dt><dt>secondary nameserver (see BIND)</dt><dt> security
plugin (see Security)</dt><dt>Security-Related
Packages</dt><dd><dl><dt>updating security-related packages, <a
class="indexterm" href="#sec-Updating_Packages">Updating
Packages</a></dt></dl></dd><dt>Sendmail, <a
class="indexterm"
href="#s2-email-mta-sendmail">Sendmail</a></dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="#s1-email-additional-resources">Additional
Resources</a></dt><dt>aliases, <a class="indexterm"
href="#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>common
configuration changes, <a class="indexterm"
href="#s3-email-mta-sendmail-changes">Common Sendmail Configuration
Changes</a></dt>
<dt>default installation, <a class="indexterm"
href="#s3-email-mta-sendmail-default">The Default Sendmail
Installation</a></dt><dt>LDAP and, <a class="indexterm"
href="#s3-email-mta-sendmail-ldap">Using Sendmail with
LDAP</a></dt><dt>limitations, <a class="indexterm"
href="#s3-email-mta-sendmail-purpose">Purpose and
Limitations</a></dt><dt>masquerading, <a class="indexterm"
href="#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>purpose,
<a class="indexterm"
href="#s3-email-mta-sendmail-purpose">Purpose and
Limitations</a></dt><dt>spam, <a class="indexterm"
href="#s3-email-sendmail-stopping-spam">Stopping
Spam</a></dt><dt>with UUCP, <a class="indexterm"
href="#s3-email-mta-sendmail-changes">Common Sendmail Configuration
Changes</a></dt></dl></dd><dt>sendmail, <a
class="indexterm" href="#s2-email-switchmail">Mail Transport Agent
(MTA) Configuration</a></dt><dt>services configuration, <a
class="indexterm" href="#ch-Services_and_Daemons">Services and
Daemons</a>
</dt><dd><dl><dt> ssystemctl , <a class="indexterm"
href="#s1-services-running">Running Services</a></dt><dt>
systemctl , <a class="indexterm"
href="#s1-services-configuring">Configuring
Services</a></dt></dl></dd><dt> sftp (see
OpenSSH)</dt><dt>shadow
passwords</dt><dd><dl><dt>overview of, <a
class="indexterm" href="#s1-users-groups-shadow-utilities">Shadow
Passwords</a></dt></dl></dd><dt>slab pools (see
/proc/slabinfo )</dt><dt>slapd (see OpenLDAP)</dt><dt> smbcacls
program, <a class="indexterm" href="#s2-samba-programs">Samba
Distribution Programs</a></dt><dt> smbclient , <a
class="indexterm" href="#s3-samba-connect-share-cmdline">Command
Line</a></dt><dt> smbclient program, <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbcontrol program, <a
class="indexterm" href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbpasswd program, <a
class="indexterm" href="#s2-samba-programs">Samba Distribution
Programs</a></dt><d
t> smbspool program, <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbstatus program, <a
class="indexterm" href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbtar program, <a class="indexterm"
href="#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>SpamAssassin</dt><dd><dl><dt>using
with Procmail, <a class="indexterm"
href="#s3-email-mda-spam">Spam
Filters</a></dt></dl></dd><dt> ssh (see
OpenSSH)</dt><dt>SSH
protocol</dt><dd><dl><dt>authentication, <a
class="indexterm"
href="#s2-ssh-protocol-authentication">Authentication</a></dt><dt>configuration
files, <a class="indexterm"
href="#s2-ssh-configuration-configs">Configuration
Files</a></dt><dd><dl><dt>system-wide configuration files,
<a class="indexterm"
href="#s2-ssh-configuration-configs">Configuration
Files</a></dt><dt>user-specific configuration files, <a
class="indexterm"
href="#s2-ssh-configuration-configs">Configuration
Files</a></dt></dl></dd><dt>c
onnection sequence, <a class="indexterm"
href="#s2-ssh-conn">Event Sequence of an SSH
Connection</a></dt><dt>features, <a class="indexterm"
href="#s2-ssh-features">Main Features</a></dt><dt>insecure
protocols, <a class="indexterm"
href="#s2-ssh-configuration-requiring">Requiring SSH for Remote
Connections</a></dt><dt>layers</dt><dd><dl><dt>channels,
<a class="indexterm"
href="#s2-ssh-protocol-connection">Channels</a></dt><dt>transport
layer, <a class="indexterm"
href="#s2-ssh-protocol-conn-transport">Transport
Layer</a></dt></dl></dd><dt>port forwarding, <a
class="indexterm" href="#s2-ssh-beyondshell-tcpip">Port
Forwarding</a></dt><dt>requiring for remote login, <a
class="indexterm" href="#s2-ssh-configuration-requiring">Requiring
SSH for Remote Connections</a></dt><dt>security risks, <a
class="indexterm" href="#s2-ssh-why">Why Use
SSH?</a></dt><dt>version 1, <a class="indexterm"
href="#s2-ssh-versions">Protocol
Versions</a></dt><dt>version 2, <a class="indexterm"
href="#s2-
ssh-versions">Protocol Versions</a></dt><dt>X11 forwarding,
<a class="indexterm" href="#s2-ssh-beyondshell-x11">X11
Forwarding</a></dt></dl></dd><dt> ssh-add , <a
class="indexterm"
href="#s3-ssh-configuration-keypairs-agent">Configuring
ssh-agent</a></dt><dt> ssh-agent , <a class="indexterm"
href="#s3-ssh-configuration-keypairs-agent">Configuring
ssh-agent</a></dt><dt>SSL, <a class="indexterm"
href="#s2-apache-mod_ssl">Setting Up an SSL
Server</a></dt><dd><dl><dt>(see also Apache HTTP
Server)</dt></dl></dd><dt>SSL server (see 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">Securing Email
Client Communications</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="indexterm" 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/ip6ta
bles-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="#ch-Network_Interfaces">Network
Interfaces</a>, <a class="indexterm"
href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/
Directory</a></dt><dd><dl><dt>(see also
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/sysc
onfig/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 information about, <a
class="indexterm" href="#ch-The_sysconfig_Directory">The sysconfig
Directory</a></dt><dt>additional resources, <a
class="indexterm"
href="#s1-sysconfig-additional-resources">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm"
href="#s2-sysconfig-installed-documentation">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><dt>files found in, <a
class="indexterm" href="#s1-sysconfig-files">Files in the
/etc/sysconfig/ Directory</a></dt></dl></dd><dt> sysctl
</dt><dd><dl><dt>configuring with /etc/sysctl.conf , <a
class="indexterm" href="#s1-proc-s
ysctl">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 (see system
request key)</dt><dt>system
information</dt><dd><dl><dt>file systems, <a
class="indexterm" href="#s1-sysinfo-filesystems">File
Systems</a></dt><dd><dl><dt> /dev/shm , <a
class="indexterm" href="#s1-sysinfo-filesystems">File
Systems</a></dt></dl></dd><dt>gathering, <a
class="indexterm" href="#ch-System_Monitoring_Tools">System
Monitoring Tools</a></dt><dt>hardware, <a class="indexterm"
href="#s1-sysinfo-hardware">Hardware</a></dt><dt>memory
usage, <a class="indexterm"
href="#s1-sysinfo-memory-usage">Memory
Usage</a></dt><dt>processes, <a class="indexterm"
href="#s1-sysinfo-system-processes">System
Processes</a></dt><dd><dl><dt>currently running, <a
class="indexterm" href="#s1-sysinfo-system-processes">System
Processes</a></dt></dl></dd></dl></dd><dt>system
request key</dt><dd><dl><dt>enabling, <a clas
s="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 (see
Authentication Configuration Tool )</dt><dt>system-config-kdump (see
kdump)</dt><dt>system-config-users (see user configuration and group
configuration)</dt><dt> systemctl (see services
configuration)</dt></dl></div><div
class="indexdiv"><h3>T</h3><dl><dt> testparm program,
<a class="indexterm" href="#s2-samba-programs">Samba
Distribution Programs</a></dt><dt>time, <a
class="indexterm"
href="#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time
Configuration Tool</a>, <a class="indexterm"
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">Configuring
the Date and Time</a></dt><dd><dl><dt>(see also Dat
e and Time)</dt></dl></dd><dt>time zone, <a
class="indexterm"
href="#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time
Configuration Tool</a></dt><dd><dl><dt>(see also Date and
Time)</dt></dl></dd><dt>TLB cache (see
hugepages)</dt><dt>TLS, <a class="indexterm"
href="#s2-apache-mod_ssl">Setting Up an SSL
Server</a></dt><dd><dl><dt>(see also Apache HTTP
Server)</dt></dl></dd><dt>tool</dt><dd><dl><dt>
Authentication Configuration Tool , <a class="indexterm"
href="#sect-The_Authentication_Configuration_Tool">The Authentication
Configuration Tool</a></dt></dl></dd><dt> top , <a
class="indexterm" href="#s1-sysinfo-system-processes">System
Processes</a></dt></dl></div><div
class="indexdiv"><h3>U</h3><dl><dt>updating currently
installed packages</dt><dd><dl><dt>available updates, <a
class="indexterm"
href="#sec-Updating_Packages_with_Software_Update">Updating Packages with
Software Update</a></dt></dl></dd><dt>updating packages with
PackageKit</dt><dd><dl><dt>PolicyKit,
<a class="indexterm"
href="#sec-Updating_Packages_with_Software_Update">Updating Packages with
Software Update</a></dt></dl></dd><dt>User Accounts (see
user configuration)</dt><dt>user
configuration</dt><dd><dl><dt>adding users, <a
class="indexterm"
href="#sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">Adding
a New User</a>, <a class="indexterm"
href="#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>changing full name, <a class="indexterm"
href="#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>changing home directory, <a
class="indexterm" href="#s2-redhat-config-users-user-new">Adding a
New User</a></dt><dt>changing login shell, <a
class="indexterm" href="#s2-redhat-config-users-user-new">Adding a
New User</a></dt><dt>changing password, <a
class="indexterm" href="#s2-redhat-config-users-user-new">Adding a
New User</a></dt><dt>command line configuration, <a
class="indexterm" href="#s2-users-cmd-line">Command Line
Configuration</a
</dt><dd><dl><dt>passwd, <a
class="indexterm" href="#s2-users-cmd-line">Command Line
Configuration</a></dt><dt>useradd, <a class="indexterm"
href="#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>filtering list of users,
<a class="indexterm" href="#s1-users-configui">User Manager
Tool</a></dt><dt>modify groups for a user, <a
class="indexterm" href="#s2-redhat-config-users-user-new">Adding a
New User</a></dt><dt>modifying users, <a class="indexterm"
href="#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>password</dt><dd><dl><dt>forcing
expiration of, <a class="indexterm"
href="#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>removing users, <a
class="indexterm"
href="#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">Removing
a User</a></dt><dt>viewing list of users, <a
class="indexterm"
href="#sect-Managing_Users_and_Groups-User_Accounts">User Accounts
Tool</a>, <a class="indexterm" href="#s1-users-configui"
User Manager Tool</a></dt></dl></dd><dt>User Manager (see
user configuration)</dt><dt>user private groups (see
groups)</dt><dd><dl><dt>and shared directories, <a
class="indexterm" href="#s2-users-groups-rationale">Group
Directories</a></dt></dl></dd><dt>useradd
command</dt><dd><dl><dt>user account creation using, <a
class="indexterm" href="#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>users (see user
configuration)</dt><dd><dl><dt>/etc/passwd, <a
class="indexterm" href="#s1-users-groups-standard-users">Standard
Users</a></dt><dt>additional resources, <a
class="indexterm"
href="#s1-users-groups-additional-resources">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="#s2-users-groups-documentation">Installed
Documentation</a></dt></dl></dd><dt>introducing, <a
class="indexterm" href="#ch-Managing_Users_and_Groups">Managing
Users and Groups</a></dt><dt>standard, <a class="indexterm"
href="#s1-users-groups-standard
-users">Standard
Users</a></dt><dt>tools for management
of</dt><dd><dl><dt>User Manager, <a class="indexterm"
href="#s1-users-tools">User and Group Management
Tools</a></dt><dt>useradd, <a class="indexterm"
href="#s1-users-tools">User and Group Management
Tools</a></dt></dl></dd><dt>UID, <a
class="indexterm" href="#ch-Managing_Users_and_Groups">Managing
Users and Groups</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>V</h3><dl><dt>virtual file
system (see proc file system)</dt><dt>virtual files (see proc file
system)</dt><dt>virtual host (see Apache HTTP Server)</dt><dt>
vsftpd , <a class="indexterm" href="#s2-ftp-servers">FTP
Servers</a></dt><dd><dl><dt>(see also
FTP)</dt><dt>additional resources, <a class="indexterm"
href="#s2-ftp-resources">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="#s3-ftp-installed-documentation">Installed
Documentation</a></dt><dt>useful websites, <a
class="indexterm" href="#s3-ftp-useful-websi
tes">Useful
Websites</a></dt></dl></dd><dt>condrestart, <a
class="indexterm" href="#s2-ftp-vsftpd-start">Starting and Stopping
vsftpd </a></dt><dt>configuration
file</dt><dd><dl><dt> /etc/vsftpd/vsftpd.conf , <a
class="indexterm" href="#s2-ftp-vsftpd-conf"> vsftpd Configuration
Options</a></dt><dt>access controls, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-login">Log In Options and Access
Controls</a></dt><dt>anonymous user options, <a
class="indexterm" href="#s3-ftp-vsftpd-conf-opt-anon">Anonymous
User Options</a></dt><dt>daemon options, <a
class="indexterm" href="#s3-ftp-vsftpd-conf-opt-daemon">Daemon
Options</a></dt><dt>directory options, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-dir">Directory
Options</a></dt><dt>file transfer options, <a
class="indexterm" href="#s3-ftp-vsftpd-conf-opt-file">File Transfer
Options</a></dt><dt>format of, <a class="indexterm"
href="#s2-ftp-vsftpd-conf"> vsftpd Configuration
Options</a></dt><dt>local user options, <a class="
indexterm" href="#s3-ftp-vsftpd-conf-opt-usr">Local User
Options</a></dt><dt>logging options, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-log">Logging
Options</a></dt><dt>login options, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-login">Log In Options and Access
Controls</a></dt><dt>network options, <a class="indexterm"
href="#s3-ftp-vsftpd-conf-opt-net">Network
Options</a></dt></dl></dd><dt>multihome configuration, <a
class="indexterm" href="#s3-ftp-vsftpd-start-multi">Starting
Multiple Copies of vsftpd </a></dt><dt>restarting, <a
class="indexterm" href="#s2-ftp-vsftpd-start">Starting and Stopping
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
Servers</a></dt><dt>starting, <a class="indexterm"
href="#s2-ftp-vsftpd-start">Starting and Stopping vsftpd
</a></dt><dt>starting multiple copi
es of, <a class="indexterm"
href="#s3-ftp-vsftpd-start-multi">Starting Multiple Copies of vsftpd
</a></dt><dt>status, <a class="indexterm"
href="#s2-ftp-vsftpd-start">Starting and Stopping vsftpd
</a></dt><dt>stopping, <a class="indexterm"
href="#s2-ftp-vsftpd-start">Starting and Stopping 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
Distribution Programs</a></dt><dt>web server (see Apache HTTP
Server)</dt><dt>Windows
2000</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm" href="#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd><dt>Windows
98</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm" href="#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd><dt>Windows
ME</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm" href="#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></d
l></dd><dt>Windows NT
4.0</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm" href="#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd><dt>Windows
XP</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm" href="#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>X</h3><dl><dt>X.500 (see
OpenLDAP)</dt><dt>X.500 Lite (see
OpenLDAP)</dt></dl></div><div
class="indexdiv"><h3>Y</h3><dl><dt>Yum</dt><dd><dl><dt>Additional
Resources, <a class="indexterm"
href="#sec-Additional_Resources">Additional
Resources</a></dt><dt>configuring plugins, <a
class="indexterm"
href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling,
Configuring and Disabling Yum Plugins</a></dt><dt>configuring Yum and
Yum repositories, <a class="indexterm"
href="#sec-Configuring_Yum_and_Yum_Repositories">Configuring Yum and Yum
Repositories</a></dt><dt>disabling plugins, <a
class="indexterm" href="#s
ec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring and
Disabling Yum Plugins</a></dt><dt>displaying packages with
Yum</dt><dd><dl><dt>yum info, <a class="indexterm"
href="#sec-Displaying_Package_Information">Displaying Package
Information</a></dt></dl></dd><dt>enabling plugins, <a
class="indexterm"
href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling,
Configuring and Disabling Yum Plugins</a></dt><dt>installing a package
group with Yum, <a class="indexterm"
href="#sec-Installing">Installing
Packages</a></dt><dt>installing with Yum, <a
class="indexterm" href="#sec-Installing">Installing
Packages</a></dt><dt>listing packages with
Yum</dt><dd><dl><dt>Glob expressions, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum grouplist, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum list, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum list all, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum list available, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum list installed, <a
class="indexterm" href="#sec-Listing_Packages">Listing
Packages</a></dt><dt>yum repolist, <a class="indexterm"
href="#sec-Listing_Packages">Listing
Packages</a></dt></dl></dd><dt>packages and package groups,
<a class="indexterm"
href="#sec-Packages_and_Package_Groups">Packages and Package
Groups</a></dt><dt>plugins</dt><dd><dl><dt>presto,
<a class="indexterm" href="#sec-Plugin_Descriptions">Plugin
Descriptions</a></dt><dt>refresh-packagekit, <a
class="indexterm" href="#sec-Plugin_Descriptions">Plugin
Descriptions</a></dt><dt>rhnplugin, <a class="indexterm"
href="#sec-Plugin_Descriptions">Plugin
Descriptions</a></dt><dt>security, <a class="indexterm"
href="#sec-Plugin_Descriptions">Plugin
Descriptions</a></dt></dl></dd><dt>repository, <a
class="indexterm" href="#sec-Creating_a_Yum
_Repository">Creating a Yum Repository</a></dt><dt>searching
packages with Yum</dt><dd><dl><dt>yum search, <a
class="indexterm" href="#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>setting [main] options, <a
class="indexterm" href="#sec-Setting_main_Options">Setting [main]
Options</a></dt><dt>setting [repository] options, <a
class="indexterm" href="#sec-Setting_repository_Options">Setting
[repository] Options</a></dt><dt>uninstalling package groups with Yum,
<a class="indexterm" href="#sec-Removing">Removing
Packages</a></dt><dt>uninstalling packages with Yum, <a
class="indexterm" href="#sec-Removing">Removing
Packages</a></dt><dd><dl><dt>yum remove package_name, <a
class="indexterm" href="#sec-Removing">Removing
Packages</a></dt></dl></dd><dt>variables, <a
class="indexterm" href="#sec-Using_Yum_Variables">Using Yum
Variables</a></dt><dt>Yum plugins, <a class="indexterm"
href="#sec-Yum_Plugins">Yum Plugins</a></dt><dt>Yum
repositories</dt><dd><dl><dt>confi
guring Yum and Yum repositories, <a class="indexterm"
href="#sec-Configuring_Yum_and_Yum_Repositories">Configuring Yum and Yum
Repositories</a></dt></dl></dd></dl></dd><dt>Yum
repositories</dt><dd><dl><dt>viewing Yum repositories with
PackageKit, <a class="indexterm"
href="#sec-Setting_preferences_for_software_sources">Setting the Software
Sources</a></dt></dl></dd><dt>Yum
Updates</dt><dd><dl><dt>checking for updates, <a
class="indexterm" href="#sec-Checking_For_Updates">Checking For
Updates</a></dt><dt>updating a single package, <a
class="indexterm" href="#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating all packages and dependencies, <a
class="indexterm" href="#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating packages, <a
class="indexterm" href="#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating security-related packages, <a
class="indexterm" href="#sec-Updating_Packages">Updating
Packages</a></dt></dl></dd></dl></div></div></div></div
</body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/common.css
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..f9603b7
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/common.css
@@ -0,0 +1,1495 @@
+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;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+}
+
+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;
+}
+
+.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;
+ 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;
+}
+
+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*/
+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;
+}
+
+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;
+}
+
+div.section {
+ margin-top:1em;
+}
+
+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;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+}
+
+.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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/default.css
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+@import url("common.css");
+@import url("overrides.css");
+@import url("lang.css");
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/lang.css
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/overrides.css
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/print.css
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+@import url("common.css");
+@import url("overrides.css");
+@import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/1.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/1.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/10.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/10.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/10.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/11.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/11.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/11.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/12.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/12.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/12.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/13.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/13.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/13.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/14.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/14.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/14.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/15.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/15.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/15.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/16.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/16.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/16.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/17.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/17.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/17.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/18.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/18.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/18.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/19.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/19.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/19.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/2.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/2.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/20.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/20.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/20.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/21.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/21.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/21.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/22.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/22.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/22.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/23.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/23.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/23.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/24.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/24.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/24.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/25.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/25.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/25.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/26.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/26.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/26.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/27.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/27.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/27.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/28.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/28.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/28.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/29.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/29.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/29.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/3.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/3.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/30.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/30.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/30.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/31.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/31.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/31.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/32.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/32.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/32.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/33.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/33.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/33.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/34.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/34.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/34.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/35.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/35.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/35.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/36.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/36.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/36.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/37.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/37.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/37.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/38.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/38.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/38.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/39.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/39.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/39.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/4.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/4.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/40.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/40.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/40.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/5.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/5.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/6.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/6.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/7.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/7.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/8.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/8.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/9.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/9.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/bullet_arrowblue.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/bullet_arrowblue.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/documentation.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/documentation.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/dot.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/dot.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/dot2.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/dot2.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/green.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/green.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/h1-bg.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/h1-bg.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/image_left.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/image_left.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/image_right.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..5b67443
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/image_right.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/important.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/important.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/important.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L
78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L
41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882
z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L
55.536215,56.538729 z"
+ id="path6824"
+
style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L
55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L
55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L
55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L
55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L
55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L
55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L
55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new"
/>
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L
55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new"
/>
+ </g>
+</svg>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/logo.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/logo.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/note.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/note.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/note.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L
-2512.4524,4607.3813 L -2512.4524,56.33197 z"
+
transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+
style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1"
/>
+ </g>
+ <g
+
transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928
370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C
154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353
494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+
style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+
style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729
326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C
209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L
509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C
495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+
style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C
253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861
313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345
440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+
style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+
style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625
404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C
280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695
527.8214,324.97052 527.8214,393.1416 z"
+
transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+
style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
+ </g>
+ </g>
+ </g>
+</svg>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/red.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/red.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/shade.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/shade.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/shine.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/shine.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-back.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-back.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-forward.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-forward.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-up.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-go-up.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-home.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/stock-home.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/title_logo.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/title_logo.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/title_logo.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/warning.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/warning.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/warning.svg
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!-- Created with Inkscape (
http://www.inkscape.org/) -->
+<svg
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
+
xmlns:cc="http://creativecommons.org/ns#"
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+
xmlns:svg="http://www.w3.org/2000/svg"
+
xmlns="http://www.w3.org/2000/svg"
+
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&q...
+
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+
inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L
-1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L
-1602.5477,1091.5306 L -1603,1054.4387 z"
+
transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+
style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1"
/>
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L
-1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L
-1602.5477,1091.5306 L -1603,1054.4387 z"
+
transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+
style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1"
/>
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987
-2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C
-2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961
-2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L
-2686.7886,1597.753"
+ id="path8038"
+
style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream
Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346
-2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C
-2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346
-2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+
style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream
Charter" />
+ </g>
+ </g>
+</svg>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/watermark-draft.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/watermark-draft.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/yellow.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/Common_Content/images/yellow.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/abrt-plugins.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/abrt-plugins.html
new file mode 100644
index 0000000..354de1f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/abrt-plugins.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>19.3. ABRT Plugins</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-abrt.html" title="Chapter 19. Automatic Bug-Reporting Tool
(ABRT)" /><link rel="prev" href="ch19s02.html"
title="19.2. Installing and Running ABRT" /><link rel="next"
href="reporter-plugins.html" title="19.3.2. Reporter Plugins"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch19s02.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="report
er-plugins.html"><strong>Next</strong></a></li></ul><div
class="section" id="abrt-plugins"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="abrt-plugins">19.3. ABRT
Plugins</h2></div></div></div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span> offers a
variety of analyzer plugins and reporter plugins. These plugins are described in the
following two sections. Not all of the plugins mentioned in the following sections are
installed by default. To view all available plugins, run the following command:
+<pre class="screen"><code class="command">yum list all |
grep abrt-plugin-*</code></pre>
+
+ </div><div class="section"
id="analyzer-plugins"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="analyzer-plugins">19.3.1. Analyzer
Plugins</h3></div></div></div><div class="para">
+ These plugins serve as analyzers and crash information collectors for specific types
of crashes. For example, the <span
class="application"><strong>Kerneloops</strong></span>
analyzer plugin checks for crashes in the kernel only. These plugins can be
enabled/disabled from loading at start-up in their corresponding configuration files
placed in the <code class="filename">/etc/abrt/plugins/</code>
directory. The following is a list of all analyzer plugins.
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span
class="term">Kerneloops</span></dt><dd><div
class="para">
+ — Checks for crashes in the kernel and consequently collects kernel crash
information. It can be enabled/disabled from loading at start-up in the <code
class="filename">/etc/abrt/plugins/Kerneloops.conf</code> file.
+ </div></dd><dt class="varlistentry"><span
class="term">Python</span></dt><dd><div
class="para">
+ — Checks for crashes in Python programs and consequently collects the crash
information. It can be enabled/disabled from loading at start-up in the <code
class="filename">/etc/abrt/plugins/Python.conf</code> file.
+ </div></dd><dt class="varlistentry"><span
class="term">CCpp</span></dt><dd><div
class="para">
+ — Checks for crashes in C and C++ programs and consequently collects the crash
information. It can be enabled/disabled from loading at start-up in the <code
class="filename">/etc/abrt/plugins/CCpp.conf</code> file.
+ </div></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch19s02.html"><strong>Prev</strong>19.2. Installing and
Running ABRT</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="reporter-plugins.html"><strong>Next</strong>19.3.2. Reporter
Plugins</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/app-Revision_History.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/app-Revision_History.html
new file mode 100644
index 0000000..e035010
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/app-Revision_History.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>Appendix D. Revision History</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="s1-proc-additional-resources.html"
title="C.5. References" /><link rel="next"
href="ix01.html" title="Index" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ix01.html"><strong>Next</strong></a></li></ul><di
v xml:lang="en-US" class="appendix"
id="app-Revision_History" lang="en-US"><div
class="titlepage"><div><div><h1
class="title">Revision
History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table border="0"
width="100%" summary="Revision history"><tr><th
align="left" valign="top"
colspan="3"><strong>Revision
History</strong></th></tr><tr><td
align="left">Revision 1-0</td><td align="left">Tue May
24 2011</td><td align="left"><span
class="author"><span class="firstname">Jaromír</span>
<span
class="surname">Hradílek</span></span></td></tr><tr><td
align="left" colspan="3">
+ <table border="0" summary="Simple list"
class="simplelist"><tr><td>Fedora 15 release of the <em
class="citetitle">Deployment
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>Prev</strong>C.5. References</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ix01.html"><strong>Next</strong>Index</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Automating_System_Tasks.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Automating_System_Tasks.html
new file mode 100644
index 0000000..d1a0d1a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Automating_System_Tasks.html
@@ -0,0 +1,147 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 18. Automating System Tasks</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Monitoring_and_Automation.html" title="Part VI. Monitoring and
Automation" /><link rel="prev"
href="s2-log-files-useful-websites.html" title="17.6.2. Useful
Websites" /><link rel="next"
href="s1-autotasks-at-batch.html" title="18.2. At and 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-useful-websites.html"><strong>Prev</strong></a></li><li
c
lass="next"><a accesskey="n"
href="s1-autotasks-at-batch.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Automating_System_Tasks" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 18. Automating System
Tasks</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">18.1. Cron
and Anacron</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-service">18.1.1.
Starting and Stopping the Service</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.2.
Configuring Anacron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">18.1.3.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">18.1.4. Co
ntrolling Access to Cron</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">18.1.5.
Black/White Listing of Cron
Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-autotasks-at-batch.html">18.2. At
and Batch</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-at-batch.html#s2-autotasks-at-configuring">18.2.1.
Configuring At Jobs</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-batch-configuring.html">18.2.2. Configuring Batch
Jobs</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-viewing.html">18.2.3. Viewing Pending
Jobs</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-commandline-options.html">18.2.4. Additional Command Line
Options</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-controlling-access.html">18.2.5. Controlling
Access to At and Batch</a></span></dt><dt><span
class="section"><a href="s2-
autotasks-at-batch-service.html">18.2.6. Starting and Stopping the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html">18.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">18.3.1.
Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id607789" 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="id600817"
class="indexterm"></a><div class="section"
id="s1-autotasks-cron-anacron"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-autotasks-cron-anacron">18.1. Cron and
Anacron</h2></div></div></div><a id="id619910"
class="indexterm"></a><a id="id594887"
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">Section 18.1.2,
“Configuring Anacron Jobs”</a> or <a class="xref"
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Section 18.1.3,
“Configuring Cron Jobs”</a>. To schedule one-time jobs, refer to <a
class="xref" href="s1-autotasks-at-batch.html">Section 18.2, “At
and 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"
id="s2-autotasks-cron-service">18.1.1. Starting and Stopping the
Service</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">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s2-configuring-anacron-jobs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-configuring-anacron-jobs">18.1.2. Configuring Anacron
Jobs</h3></div></div></div><a id="id422609"
class="indexterm"></a><a id="id553586"
class="indexterm"></a><a id="id624754"
class="indexterm"></a><a id="id532244"
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
+@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"
id="s3-anacron-examples">18.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
+@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"
id="s3-disabling-anacron">18.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"
id="s2-configuring-cron-jobs">18.1.3. Configuring Cron
Jobs</h3></div></div></div><a id="id605580"
class="indexterm"></a><a id="id428583"
class="indexterm"></a><a id="id641408"
class="indexterm"></a><a id="id637704"
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">Section 18.1.2,
“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">
+ For any of the above values, an asterisk (*) can be used to specify all valid values.
For example, an asterisk for the month value means execute the command every month within
the constraints of the other values.
+ </div><div class="para">
+ A hyphen (-) between integers specifies a range of integers. For example, <strong
class="userinput"><code>1-4</code></strong> means the
integers 1, 2, 3, and 4.
+ </div><div class="para">
+ A list of values separated by commas (,) specifies a list. For example, <strong
class="userinput"><code>3, 4, 6, 8</code></strong>
indicates 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"
id="s2-autotasks-cron-access">18.1.4. Controlling Access to
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"
id="s2-black-white-listing-of-cron-jobs">18.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">Section 18.1.4,
“Controlling Access to Cron”</a>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-log-files-useful-websites.html"><strong>Prev</strong>17.6.2. Useful
Websites</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-autotasks-at-batch.html"><strong>Next</strong>18.2. At
and Batch</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Configuring_Authentication.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Configuring_Authentication.html
new file mode 100644
index 0000000..7adc875
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Configuring_Authentication.html
@@ -0,0 +1,429 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 8. Configuring 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Infrastructure_Services.html" title="Part IV. Infrastructure
Services" /><link rel="prev"
href="s2-services-additional-resources-books.html" title="7.3.2. Related
Books" /><link rel="next"
href="chap-SSSD_User_Guide-Introduction.html" title="8.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 accesskey="p"
href="s2-services-additional-res
ources-books.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Introduction.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Configuring_Authentication" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 8. Configuring
Authentication</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">8.1.
The Authentication Configuration
Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1.
Identity & Authentication</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">8.1.2.
Advanced Options</a></span></dt><dt><span
class="section"><a href="ch-Configuring_Authenticat
ion.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3.
Command Line
Version</a></span></dt></dl></dd><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Introduction.html">8.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">8.2.1.
What is SSSD?</a></span></dt><dt><span
class="section"><a
href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html">8.2.2. SSSD
Features</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Setting_Up_SSSD.html">8.2.3. Setting Up
SSSD</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Configuring_Services.html">8.2.4. Configuring
Services</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Configuring_Domains.html">8.2.5. Configuring
Domains</a></span></dt><dt><span
class="section"><a href="sect-SSSD_User_Guide-Configuring
_Domains-Setting_up_Kerberos_Authentication.html">8.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">8.2.7.
Configuring a Proxy Domain</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Troubleshooting.html">8.2.8.
Troubleshooting</a></span></dt><dt><span
class="section"><a
href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">8.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"
id="sect-The_Authentication_Configuration_Tool">8.1. The Authentication
Configuration Tool</h2></div></div></div><a
id="id634794" class="indexterm"></a><a
id="id634783" class="indexterm"></a><div
class="para">
+ When a user logs in to a Fedora system, the username and password combination must be
verified, or <em class="firstterm">authenticated</em>, as a valid
and active user. Sometimes the information to verify the user is located on the local
system, and other times the system defers the authentication to a user database on a
remote system.
+ </div><div class="para">
+ The <span class="application"><strong>Authentication
Configuration Tool</strong></span> provides a graphical interface for
configuring user information retrieval from <em
class="firstterm">Lightweight Directory Access Protocol</em> (LDAP),
<em class="firstterm"> Network Information Service</em> (NIS), and
<em class="firstterm">Winbind</em> user account databases. This tool
also allows you to configure Kerberos to be used as the authentication protocol when using
LDAP or NIS.
+ </div><div class="note"><div
class="admonition_header"><h2>Using a high or medium security
level</h2></div><div class="admonition"><div
class="para">
+ If you configured a medium or high security level during installation (or with the
<span class="application"><strong>Security Level Configuration
Tool</strong></span>), then the firewall will prevent NIS authentication. For
more information about firewalls, refer to the <em
class="citetitle">"Firewalls"</em> section of the Fedora
<em class="citetitle">Security Guide</em>.
+ </div></div></div><a id="id634726"
class="indexterm"></a><a id="id634708"
class="indexterm"></a><div class="para">
+ To start the graphical version of the <span
class="application"><strong>Authentication
Configuration</strong></span> tool from the desktop, select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>Other</strong></span> →
<span
class="guimenuitem"><strong>Authentication</strong></span>
form the <span
class="guimenu"><strong>Activities</strong></span> menu or
type the command <code
class="command">system-config-authentication</code> at a shell prompt
(for example, in an <span
class="application"><strong>XTerm</strong></span> or a
<span class="application"><strong>GNOME</strong></span>
terminal).
+ </div><div class="important"><div
class="admonition_header"><h2>Your changes are immediately
applied</h2></div><div class="admonition"><div
class="para">
+ After exiting the authentication program, any changes you made take effect
immediately.
+ </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"
id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1. Identity
& Authentication</h3></div></div></div><div
class="para">
+ The <span class="guilabel"><strong>Identity &
Authentication</strong></span> tab allows you to configure how users should be
authenticated, and has several options for each method of authentication. To select which
user account database should be used, select an option from the drop-down list.
+ </div><div class="figure"><div
class="figure-contents"><div class="mediaobject"
align="center"><img src="images/authconfig_LDAP_kerb.png"
align="middle" alt="Identity & Authentication; changing the option
in the User Account Database drop-down list changes the contents of the tab"
/></div></div><h6>Figure 8.1. Identity & Authentication;
changing the option in the User Account Database drop-down list changes the contents of
the tab</h6></div><br class="figure-break" /><div
class="para">
+ The following list explains what each option configures:
+ </div><h4 id="id634610">LDAP</h4><a
id="id634616" class="indexterm"></a><div
class="para">
+ The <span
class="guilabel"><strong>LDAP</strong></span> option
instructs the system to retrieve user information via LDAP. It contains the following
specifications:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP Search Base
DN</strong></span> — Specifies that user information should be retrieved using
the listed Distinguished Name (DN).
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>LDAP
Server</strong></span> — Specifies the address of the <code
class="systemitem">LDAP</code> server.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Use TLS to encrypt
connections</strong></span> — When enabled, <code
class="systemitem">Transport Layer Security</code> (TLC) will be used
to encrypt passwords sent to the <code
class="systemitem">LDAP</code> server. The <span
class="guibutton"><strong>Download CA
Certificate</strong></span> option allows you to specify a URL from which to
download a valid <em class="firstterm">Certificate Authority
certificate</em> (CA). A valid CA certificate must be in the <em
class="firstterm">Privacy Enhanced Mail</em> (PEM) format.
+ </div><div class="important"><div
class="admonition_header"><h2>Using ldaps:// in the LDAP Server
field</h2></div><div class="admonition"><div
class="para">
+ The <span class="guilabel"><strong>Use TLS to encrypt
connections</strong></span> option must not be ticked if an <code
class="systemitem">ldaps://</code> server address is specified in the
<span class="guilabel"><strong>LDAP
Server</strong></span> field.
+ </div></div></div><div class="para">
+ For more information about CA Certificates, refer to <a class="xref"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">Section 12.1.8.1,
“An Overview of Certificates and Security”</a>.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">openldap-clients</code> package must
be installed for this option to work.
+ </div><div class="para">
+ For more information about LDAP, refer to <a class="xref"
href="ch-Directory_Servers.html#s1-OpenLDAP">Section 14.1,
“OpenLDAP”</a>.
+ </div><div class="para">
+ LDAP provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><a id="id634379"
class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Kerberos
password</strong></span> — This option enables Kerberos authentication. It
contains the following specifications:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Realm</strong></span> — Configures
the realm for the Kerberos server. The realm is the network that uses Kerberos, composed
of one or more KDCs and a potentially large number of clients.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>KDCs</strong></span> — Defines the
Key Distribution Centers (KDC), which are servers that issue Kerberos tickets.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Admin
Servers</strong></span> — Specifies the administration server(s) running
<code class="command">kadmind</code>.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The <span class="guimenu"><strong>Kerberos
Settings</strong></span> dialog also allows you to use DNS to resolve hosts to
realms and locate KDCs for realms.
+ </div><div class="para">
+ The <code class="filename">krb5-libs</code> and <code
class="filename">krb5-workstation</code> packages must be installed for
this option to work. For more information about Kerberos, refer to section <em
class="citetitle">Using Kerberos</em> of the Fedora 15 <em
class="citetitle">Managing Single Sign-On and Smart Cards</em> guide.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>LDAP
password</strong></span> — This option instructs standard PAM-enabled
applications to use LDAP authentication with options specified in the User Account
Configuration of LDAP. When using this option, you must provide an <code
class="systemitem">ldaps://</code> server address or use TLS for LDAP
authentication.
+ </div></li></ul></div><div
class="note"><div class="admonition_header"><h2>Setting
up the SSSD service</h2></div><div class="admonition"><div
class="para">
+ The SSSD service is used as a client for LDAP and Kerberos servers. Thus, offline
login is enabled and supported by default. No user interaction is needed to set up the
SSSD service with the <span
class="application"><strong>Authentication Configuration
Tool</strong></span>. For more information about the SSSD service, refer to
<a class="xref"
href="chap-SSSD_User_Guide-Introduction.html">Section 8.2, “The System
Security Services Daemon (SSSD)”</a>
+ </div></div></div><h4
id="id634346">NIS</h4><a id="id634335"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>NIS</strong></span> option
configures the system to connect to a NIS server (as an NIS client) for user and password
authentication. To configure this option, specify the NIS domain and NIS server. If the
NIS server is not specified, the daemon attempts to find it via broadcast.
+ </div><div class="para">
+ The <span class="package">ypbind</span> package must be
installed for this option to work. If the NIS user account database is used, the <code
class="systemitem">portmap</code> and <code
class="systemitem">ypbind</code> services are started and are also
enabled to start at boot time.
+ </div><div class="para">
+ For more information about NIS, refer to section <em
class="citetitle">"Securing NIS"</em> of the Fedora <em
class="citetitle">Security Guide</em>.
+ </div><div class="para">
+ NIS provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Kerberos
password</strong></span> — This option enables Kerberos authentication. For
more information about configuration of the Kerberos authentication method, refer to the
previous section on LDAP.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="id634269" class="indexterm"></a>
+ <span class="guilabel"><strong>NIS
password</strong></span> — This option enables NIS authentication. NIS can
provide authentication information to outside processes to authenticate users.
+ </div></li></ul></div><h4
id="id634247">Winbind</h4><a id="id634244"
class="indexterm"></a><div class="para">
+ The <span
class="guilabel"><strong>Winbind</strong></span> option
configures the system to connect to a Windows Active Directory or a Windows domain
controller. User information from the specified directory or domain controller can then be
accessed, and server authentication options can be configured. It contains the following
specifications:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind
Domain</strong></span> — Specifies the Windows Active Directory or domain
controller to connect to.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Security
Model</strong></span> — Allows you to select a security model, which
configures the Samba client mode of operation. The drop-down list allows you to select any
of the following:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>ads</strong></span> — This mode
instructs Samba to act as a domain member in an Active Directory Server (ADS) realm. To
operate in this mode, the <code class="filename">krb5-server</code>
package must be installed, and Kerberos must be configured properly.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>domain</strong></span> — In this
mode, Samba will attempt to validate the username/password by authenticating it through a
Windows NT Primary or Backup Domain Controller, similar to how a Windows NT Server would.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>server</strong></span> — In this
mode, Samba will attempt to validate the username/password by authenticating it through
another SMB server (for example, a Windows NT Server). If the attempt fails, the <span
class="guilabel"><strong>user</strong></span> mode will
take effect instead.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>user</strong></span> — This is the
default mode. With this level of security, a client must first log in with a valid
username and password. Encrypted passwords can also be used in this security mode.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Winbind ADS
Realm</strong></span> — When the <span
class="guilabel"><strong>ads</strong></span> Security Model
is selected, this allows you to specify the ADS Realm the Samba server should act as a
domain member of.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Winbind Domain
Controllers</strong></span> — Use this option to specify which domain
controller <code class="command">winbind</code> should use. For more
information about domain controllers, please refer to <a class="xref"
href="ch-File_and_Print_Servers.html#s3-samba-domain-controller">Section 15.1.6.3,
“Domain Controller”</a>.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Template
Shell</strong></span> — When filling out the user information for a Windows NT
user, the <code class="command">winbindd</code> daemon uses the
value chosen here to specify the login shell for that user.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Allow offline
login</strong></span> — By checking this option, you allow authentication
information to be stored in a local cache (provided by SSSD). This information is then
used when a user attempts to authenticate while offline.
+ </div></li></ul></div><div class="para">
+ For more information about the <code
class="command">winbindd</code> service, refer to <a
class="xref"
href="ch-File_and_Print_Servers.html#s2-samba-daemons">Section 15.1.2, “Samba
Daemons and Related Services”</a>.
+ </div><a id="id633999"
class="indexterm"></a><div class="para">
+ Winbind provides only one method of authentication, <span
class="guilabel"><strong>Winbind password</strong></span>.
This method of authentication uses the options specified in the User Account Configuration
of Winbind to connect to a Windows Active Directory or a Windows domain controller.
+ </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"
id="sect-The_Authentication_Configuration_Tool-Advanced_Options">8.1.2. Advanced
Options</h3></div></div></div><div class="para">
+ This tab allows you to configure advanced options, as listed below.
+ </div><div class="figure"><div
class="figure-contents"><div class="mediaobject"
align="center"><img src="images/authconfig_advanced.png"
align="middle" width="444" alt="Advanced Options"
/></div></div><h6>Figure 8.2. Advanced
Options</h6></div><br class="figure-break" /><h4
id="id633940">Local Authentication Options</h4><div
class="itemizedlist"><ul><li class="listitem"><a
id="id633935" class="indexterm"></a><div
class="para">
+ <span class="guilabel"><strong>Enable fingerprint reader
support</strong></span> — By checking this option, you enable fingerprint
authentication to log in by scanning your finger with the fingerprint reader.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Enable local access
control</strong></span> — When enabled, <code
class="filename">/etc/security/access.conf</code> is consulted for
authorization of a user.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Password Hashing
Algorithm</strong></span> — This option lets you specify which hashing or
cryptographic algorithm should be used to encrypt locally stored passwords.
+ </div></li></ul></div><h4
id="id633847">Other Authentication Options</h4><div
class="para">
+ <span class="guilabel"><strong>Create home directories on the
first login</strong></span> — When enabled, the user's home directory is
automatically created when they log in if it does not already exist.
+ </div><h4 id="id633865">Smart Card Authentication
Options</h4><a id="id633861"
class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Enable smart card
support</strong></span> — This option enables smart card authentication. Smart
card authentication allows you to log in using a certificate and a key associated with a
smart card.
+ </div><div class="para">
+ When the <span class="guilabel"><strong>Enable smart card
support</strong></span> option is checked, the following options can be
specified:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Card Removal
Action</strong></span> — This option defines what action the system performs
when the card is removed from the card reader during an active session. Two alternatives
are available:
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Ignore</strong></span> — The card
removal is ignored and the system continues to function as normal.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Lock</strong></span> — The current
session is immediately locked.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Require smart card
login</strong></span> — Requires the user to login and authenticate with a
smart card. It essentially disables any other type of password authentication. This option
should not be selected until after you have successfully logged in using a smart card.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The <span class="package">pam_pkcs11</span> and the <span
class="package">coolkey</span> packages must be installed for this
option to work. For more information about smart cards, refer to the Red Hat Enterprise
Linux 6 <a
href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/h...
Single Sign-On and Smart Cards Guide</a>.
+ <div class="note"><div
class="admonition_header"><h2>Click Revert to restore the previous
configuration</h2></div><div class="admonition"><div
class="para">
+ You can restore all of the options specified in the <span
class="application"><strong>Authentication Configuration
Tool</strong></span> to the previous configuration setup by clicking <span
class="guibutton"><strong>Revert</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"
id="sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3. Command
Line Version</h3></div></div></div><a id="id633747"
class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Authentication
Configuration</strong></span> tool also supports a command line interface. The
command line version can be used in a configuration script or a kickstart script. The
authentication options are summarized in <a class="xref"
href="ch-Configuring_Authentication.html#tb-authconfig-cmd-line">Table 8.1,
“Command line options”</a>.
+ </div><div class="note"><div
class="admonition_header"><h2>Getting the list of supported
authentication options</h2></div><div
class="admonition"><div class="para">
+ These options can also be found in the <code
class="command">authconfig</code> man page or by typing <code
class="command">authconfig --help</code> at the shell prompt.
+ </div></div></div><div class="table"
id="tb-authconfig-cmd-line"><h6>Table 8.1. Command line
options</h6><div class="table-contents"><table
summary="Command line options" border="1"><colgroup><col
width="60%" class="option" /><col width="40%"
class="description" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">--enableshadow, --useshadow</code>
+ </td><td>
+ Enable shadow passwords
+ </td></tr><tr><td>
+ <code class="command">--disableshadow</code>
+ </td><td>
+ Disable shadow passwords
+ </td></tr><tr><td>
+ <code class="command">--passalgo=<em
class="replaceable"><code>descrypt|bigcrypt|md5|sha256|sha512</code></em></code>
+ </td><td>
+ Hash/crypt algorithm to be used
+ </td></tr><tr><td>
+ <code class="command">--enablenis</code>
+ </td><td>
+ Enable NIS for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disablenis</code>
+ </td><td>
+ Disable NIS for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--nisdomain=<em
class="replaceable"><code>domain</code></em> </code>
+ </td><td>
+ Specify an NIS domain
+ </td></tr><tr><td>
+ <code class="command">--nisserver=<em
class="replaceable"><code>server</code></em> </code>
+ </td><td>
+ Specify an NIS server
+ </td></tr><tr><td>
+ <code class="command">--enableldap</code>
+ </td><td>
+ Enable LDAP for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disableldap</code>
+ </td><td>
+ Disable LDAP for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--enableldaptls</code>
+ </td><td>
+ Enable use of TLS with LDAP
+ </td></tr><tr><td>
+ <code class="command">--disableldaptls</code>
+ </td><td>
+ Disable use of TLS with LDAP
+ </td></tr><tr><td>
+ <code class="command">--enablerfc2307bis</code>
+ </td><td>
+ Enable use of RFC-2307bis schema for LDAP user information lookups
+ </td></tr><tr><td>
+ <code class="command">--disablerfc2307bis</code>
+ </td><td>
+ Disable use of RFC-2307bis schema for LDAP user information lookups
+ </td></tr><tr><td>
+ <code class="command">--enableldapauth</code>
+ </td><td>
+ Enable LDAP for authentication
+ </td></tr><tr><td>
+ <code class="command">--disableldapauth</code>
+ </td><td>
+ Disable LDAP for authentication
+ </td></tr><tr><td>
+ <code class="command">--ldapserver=<em
class="replaceable"><code>server</code></em> </code>
+ </td><td>
+ Specify an LDAP server
+ </td></tr><tr><td>
+ <code class="command">--ldapbasedn=<em
class="replaceable"><code>dn</code></em> </code>
+ </td><td>
+ Specify an LDAP base DN (Distinguished Name)
+ </td></tr><tr><td>
+ <code class="command">--ldaploadcacert=<em
class="replaceable"><code>URL</code></em> </code>
+ </td><td>
+ Load a CA certificate from the specified URL
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5</code>
+ </td><td>
+ Enable Kerberos for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5</code>
+ </td><td>
+ Disable Kerberos for authentication
+ </td></tr><tr><td>
+ <code class="command">--krb5kdc=<em
class="replaceable"><code>server</code></em> </code>
+ </td><td>
+ Specify Kerberos KDC server
+ </td></tr><tr><td>
+ <code class="command">--krb5adminserver=<em
class="replaceable"><code>server</code></em> </code>
+ </td><td>
+ Specify Kerberos administration server
+ </td></tr><tr><td>
+ <code class="command">--krb5realm=<em
class="replaceable"><code>realm</code></em> </code>
+ </td><td>
+ Specify Kerberos realm
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5kdcdns</code>
+ </td><td>
+ Enable use of DNS to find Kerberos KDCs
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5kdcdns</code>
+ </td><td>
+ Disable use of DNS to find Kerberos KDCs
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5realmdns</code>
+ </td><td>
+ Enable use of DNS to find Kerberos realms
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5realmdns</code>
+ </td><td>
+ Disable use of DNS to find Kerberos realms
+ </td></tr><tr><td>
+ <code class="command">--enablewinbind</code>
+ </td><td>
+ Enable winbind for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disablewinbind</code>
+ </td><td>
+ Disable winbind for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindauth</code>
+ </td><td>
+ Enable winbindauth for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindauth</code>
+ </td><td>
+ Disable winbindauth for authentication
+ </td></tr><tr><td>
+ <code class="command">--winbindseparator=<em
class="replaceable"><code>\</code></em> </code>
+ </td><td>
+ Character used to separate the domain and user part of winbind usernames if
<code class="command">winbindusedefaultdomain</code> is not enabled
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplatehomedir=<em
class="replaceable"><code>/home/%D/%U</code></em>
</code>
+ </td><td>
+ Directory that winbind users have as their home
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplateprimarygroup=<em
class="replaceable"><code>nobody</code></em> </code>
+ </td><td>
+ Group that winbind users have as their primary group
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplateshell=<em
class="replaceable"><code>/bin/false</code></em>
</code>
+ </td><td>
+ Shell that winbind users have as their default login shell
+ </td></tr><tr><td>
+ <code
class="command">--enablewinbindusedefaultdomain</code>
+ </td><td>
+ Configures winbind to assume that users with no domain in their usernames are
domain users
+ </td></tr><tr><td>
+ <code
class="command">--disablewinbindusedefaultdomain</code>
+ </td><td>
+ Configures winbind to assume that users with no domain in their usernames are not
domain users
+ </td></tr><tr><td>
+ <code class="command">--winbindjoin=<em
class="replaceable"><code>Administrator</code></em>
</code>
+ </td><td>
+ Joins the winbind domain or ADS realm as the specified administrator
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindoffline</code>
+ </td><td>
+ Configures winbind to allow offline login
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindoffline</code>
+ </td><td>
+ Configures winbind to prevent offline login
+ </td></tr><tr><td>
+ <code class="command">--smbsecurity=<em
class="replaceable"><code>user|server|domain|ads</code></em></code>
+ </td><td>
+ Security mode to use for the Samba and Winbind services
+ </td></tr><tr><td>
+ <code class="command">--smbrealm=<em
class="replaceable"><code>realm</code></em></code>
+ </td><td>
+ Default realm for Samba and Winbind services when <span
class="guilabel"><strong>security</strong></span> is set to
<span class="guimenuitem"><strong>ads</strong></span>
+ </td></tr><tr><td>
+ <code class="command">--enablewins</code>
+ </td><td>
+ Enable Wins for hostname resolution
+ </td></tr><tr><td>
+ <code class="command">--disablewins</code>
+ </td><td>
+ Disable Wins for hostname resolution
+ </td></tr><tr><td>
+ <code class="command">--enablesssd</code>
+ </td><td>
+ Enable SSSD for user information
+ </td></tr><tr><td>
+ <code class="command">--disablesssd</code>
+ </td><td>
+ Disable SSSD for user information
+ </td></tr><tr><td>
+ <code class="command">--enablecache</code>
+ </td><td>
+ Enable <code class="command">nscd</code>
+ </td></tr><tr><td>
+ <code class="command">--disablecache</code>
+ </td><td>
+ Disable <code class="command">nscd</code>
+ </td></tr><tr><td>
+ <code class="command">--enablelocauthorize</code>
+ </td><td>
+ Local authorization is sufficient for local users
+ </td></tr><tr><td>
+ <code class="command">--disablelocauthorize</code>
+ </td><td>
+ Local users are also authorized through a remote service
+ </td></tr><tr><td>
+ <code class="command">--enablesysnetauth</code>
+ </td><td>
+ Authenticate system accounts with network services
+ </td></tr><tr><td>
+ <code class="command">--disablesysnetauth</code>
+ </td><td>
+ Authenticate system accounts with local files only
+ </td></tr><tr><td>
+ <code class="command">--enablepamaccess</code>
+ </td><td>
+ Check <code
class="filename">/etc/security/access.conf</code> during account
authorization
+ </td></tr><tr><td>
+ <code class="command">--disablepamaccess</code>
+ </td><td>
+ Do not check <code
class="filename">/etc/security/access.conf</code> during account
authorization
+ </td></tr><tr><td>
+ <code class="command">--enablemkhomedir</code>
+ </td><td>
+ Create a home directory for a user on the first login
+ </td></tr><tr><td>
+ <code class="command">--disablemkhomedir</code>
+ </td><td>
+ Do not create a home directory for a user on the first login
+ </td></tr><tr><td>
+ <code class="command">--enablesmartcard</code>
+ </td><td>
+ Enable authentication with a smart card
+ </td></tr><tr><td>
+ <code class="command">--disablesmartcard</code>
+ </td><td>
+ Disable authentication with a smart card
+ </td></tr><tr><td>
+ <code class="command">--enablerequiresmartcard</code>
+ </td><td>
+ Require smart card for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablerequiresmartcard</code>
+ </td><td>
+ Do not require smart card for authentication
+ </td></tr><tr><td>
+ <code class="command">--smartcardmodule=<em
class="replaceable"><code>module</code></em></code>
+ </td><td>
+ Default smart card module to use
+ </td></tr><tr><td>
+ <code class="command">--smartcardaction=<em
class="replaceable"><code>0=Lock|1=Ignore</code></em></code>
+ </td><td>
+ Action to be taken when smart card removal is detected
+ </td></tr><tr><td>
+ <code class="command">--enablefingerprint</code>
+ </td><td>
+ Enable fingerprint authentication
+ </td></tr><tr><td>
+ <code class="command">--disablefingerprint</code>
+ </td><td>
+ Disable fingerprint authentication
+ </td></tr><tr><td>
+ <code class="command">--nostart</code>
+ </td><td>
+ Do not start or stop the <code
class="command">portmap</code>, <code
class="command">ypbind</code>, or <code
class="command">nscd</code> services even if they are configured
+ </td></tr><tr><td>
+ <code class="command">--test</code>
+ </td><td>
+ Do not update the configuration files, only print the new settings
+ </td></tr><tr><td>
+ <code class="command">--update, --kickstart</code>
+ </td><td>
+ Opposite of <code class="command">--test</code>, update
configuration files with changed settings
+ </td></tr><tr><td>
+ <code class="command">--updateall</code>
+ </td><td>
+ Update all configuration files
+ </td></tr><tr><td>
+ <code class="command">--probe</code>
+ </td><td>
+ Probe and display network defaults
+ </td></tr><tr><td>
+ <code class="command">--savebackup=<em
class="replaceable"><code>name</code></em></code>
+ </td><td>
+ Save a backup of all configuration files
+ </td></tr><tr><td>
+ <code class="command">--restorebackup=<em
class="replaceable"><code>name</code></em></code>
+ </td><td>
+ Restore a backup of all configuration files
+ </td></tr><tr><td>
+ <code class="command">--restorelastbackup</code>
+ </td><td>
+ Restore the backup of configuration files saved before the previous configuration
change
+ </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>Prev</strong>7.3.2. Related
Books</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Introduction.html"><strong>Next</strong>8.2. The
System Security Services Daemon
(SSSD)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-DHCP_Servers.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-DHCP_Servers.html
new file mode 100644
index 0000000..81c7b79
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-DHCP_Servers.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>Chapter 10. DHCP Servers</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Servers.html" title="Part V. Servers" /><link
rel="prev" href="part-Servers.html" title="Part V. Servers"
/><link rel="next" href="s1-dhcp-configuring-server.html"
title="10.2. Configuring a 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="part-Servers.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-dhcp-configuring-ser
ver.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-DHCP_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 10. DHCP
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-DHCP_Servers.html#s1-dhcp-why">10.1. Why Use
DHCP?</a></span></dt><dt><span
class="section"><a
href="s1-dhcp-configuring-server.html">10.2. Configuring a DHCP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-dhcp-configuring-server.html#config-file">10.2.1. Configuration
File</a></span></dt><dt><span
class="section"><a href="lease-database.html">10.2.2. Lease
Database</a></span></dt><dt><span
class="section"><a href="ch10s02s03.html">10.2.3. Starting
and Stopping the Server</a></span></dt><dt><span
class="section"><a href="dhcp-relay-agent.html">10.2.4. DHCP
Relay Agent</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-dhcp-configuring-client.html">10.3. Configuring a DHCP
Client</a></span></dt><dt><span
class="section"><a
href="sect-Configuring_a_Multihomed_DHCP_Server.html">10.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">10.4.1.
Host
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">10.5.
DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span
class="section"><a
href="s1-dhcp-additional-resources.html">10.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">10.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id418294" class="indexterm"></a><a
id="id461306" class="indexterm"></a><div
class="para">
+ Dynamic Host Configuration Protocol (<acronym
class="acronym">DHCP</acronym>) is a network protocol that
automatically assigns TCP/IP information to client machines. Each DHCP client connects to
the centrally located DHCP server, which returns that client's network configuration
(including the IP address, gateway, and DNS servers).
+ </div><div class="section" id="s1-dhcp-why"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-dhcp-why">10.1. Why Use
DHCP?</h2></div></div></div><a id="id483104"
class="indexterm"></a><div class="para">
+ DHCP is useful for automatic configuration of client network interfaces. When
configuring the client system, the administrator chooses DHCP instead of specifying an IP
address, netmask, gateway, or DNS servers. The client retrieves this information from the
DHCP server. DHCP is also useful if an administrator wants to change the IP addresses of a
large number of systems. Instead of reconfiguring all the systems, he can just edit one
DHCP configuration file on the server for the new set of IP addresses. If the DNS servers
for an organization changes, the changes are made on the DHCP server, not on the DHCP
clients. When the administrator restarts the network or reboots the clients, the changes
will go into effect.
+ </div><div class="para">
+ If an organization has a functional DHCP server properly connected to a network,
laptops and other mobile computer users can move these devices from office to office.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="part-Servers.html"><strong>Prev</strong>Part V. Servers</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-dhcp-configuring-server.html"><strong>Next</strong>10.2. Configuring
a DHCP Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-DNS_Servers.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-DNS_Servers.html
new file mode 100644
index 0000000..fa10a5e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-DNS_Servers.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 11. DNS Servers</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Servers.html" title="Part V. Servers" /><link
rel="prev" href="s1-dhcp-additional-resources.html"
title="10.6. Additional Resources" /><link rel="next"
href="s1-BIND.html" title="11.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-BIND.html"><strong
Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-DNS_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 11. DNS
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-DNS_Servers.html#s1-Introduction_to_DNS">11.1. Introduction to
DNS</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-zones">11.1.1. Nameserver
Zones</a></span></dt><dt><span
class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">11.1.2. Nameserver
Types</a></span></dt><dt><span
class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-bind">11.1.3. BIND as a
Nameserver</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-BIND.html">11.2.
BIND</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-BIND.html#s2-bind-namedconf">11.2.1. Configuring the named
Service</a></span></dt><dt><span
class="section"><a href="s2-bind-zone.html">
11.2.2.
Editing Zone Files</a></span></dt><dt><span
class="section"><a href="s2-bind-rndc.html">11.2.3. Using the
rndc Utility</a></span></dt><dt><span
class="section"><a href="s2-bind-dig.html">11.2.4. Using the
dig Utility</a></span></dt><dt><span
class="section"><a href="s2-bind-features.html">11.2.5.
Advanced Features of BIND</a></span></dt><dt><span
class="section"><a href="s2-bind-mistakes.html">11.2.6.
Common Mistakes to Avoid</a></span></dt><dt><span
class="section"><a
href="s2-bind-additional-resources.html">11.2.7. Additional
Resources</a></span></dt></dl></dd></dl></div><a
id="id647794" class="indexterm"></a><a
id="id647840" class="indexterm"></a><div
class="para">
+ <code class="systemitem">DNS</code> (Domain Name System), also
known as a <em class="firstterm">nameserver</em>, is a network
system that associates hostnames with their respective IP addresses. For users, this has
the advantage that they can refer to machines on the network by names that are usually
easier to remember than the numerical network addresses. For system administrators, using
the nameserver allows them to change the IP address for a host without ever affecting the
name-based queries, or to decide which machines handle these queries.
+ </div><div class="section"
id="s1-Introduction_to_DNS"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-Introduction_to_DNS">11.1. Introduction to
DNS</h2></div></div></div><a id="id647811"
class="indexterm"></a><div class="para">
+ DNS is usually implemented using one or more centralized servers that are
authoritative for certain domains. When a client host requests information from a
nameserver, it usually connects to port 53. The nameserver then attempts to resolve the
name requested. If it does not have an authoritative answer, or does not already have the
answer cached from an earlier query, it queries other nameservers, called <em
class="firstterm">root nameservers</em>, to determine which nameservers
are authoritative for the name in question, and then queries them to get the requested
name.
+ </div><div class="section"
id="s2-dns-introduction-zones"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-dns-introduction-zones">11.1.1. Nameserver
Zones</h3></div></div></div><a id="id647789"
class="indexterm"></a><a id="id647776"
class="indexterm"></a><a id="id647765"
class="indexterm"></a><a id="id647759"
class="indexterm"></a><div class="para">
+ In a DNS server such as BIND, all information is stored in basic data elements called
<em class="firstterm">resource records</em> (RR). The resource
record is usually a <em class="firstterm">fully qualified domain
name</em> (FQDN) of a host, and is broken down into multiple sections organized into
a tree-like hierarchy. This hierarchy consists of a main trunk, primary branches,
secondary branches, and so on. The following is an example of a resource record:
+ </div><pre
class="programlisting">bob.sales.example.com</pre><a
id="id647733" class="indexterm"></a><div
class="para">
+ Each level of the hierarchy is divided by a period (that is, <code
class="literal">.</code>). In the example above, <code
class="literal">com</code> defines the <em
class="firstterm">top-level domain</em>, <code
class="literal">example</code> its subdomain, and <code
class="literal">sales</code> the subdomain of <code
class="literal">example</code>. In this case, <code
class="literal">bob</code> identifies a resource record that is part of
the <code class="systemitem">sales.example.com</code> domain. With
the exception of the part furthest to the left (that is, <code
class="literal">bob</code>), each of these sections is called a <em
class="firstterm">zone</em> and defines a specific <em
class="firstterm">namespace</em>.
+ </div><a id="id647680"
class="indexterm"></a><a id="id647662"
class="indexterm"></a><div class="para">
+ Zones are defined on authoritative nameservers through the use of <em
class="firstterm">zone files</em>, which contain definitions of the
resource records in each zone. Zone files are stored on <em
class="firstterm">primary nameservers</em> (also called <em
class="firstterm">master nameservers</em>), where changes are made to
the files, and <em class="firstterm">secondary nameservers</em>
(also called <em class="firstterm">slave nameservers</em>), which
receive zone definitions from the primary nameservers. Both primary and secondary
nameservers are authoritative for the zone and look the same to clients. Depending on the
configuration, any nameserver can also serve as a primary or secondary server for multiple
zones at the same time.
+ </div></div><div class="section"
id="s2-dns-introduction-nameservers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-dns-introduction-nameservers">11.1.2. Nameserver
Types</h3></div></div></div><div class="para">
+ There are two nameserver configuration types:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id647617" class="indexterm"></a>
+ <a id="id647602" class="indexterm"></a>
+ <a id="id647588" class="indexterm"></a>
+ <a id="id647573" class="indexterm"></a>
+ <a id="id647565" class="indexterm"></a>
+ <a id="id647530" class="indexterm"></a>
+ authoritative </span></dt><dd><div class="para">
+ Authoritative nameservers answer to resource records that are part of their zones
only. This category includes both primary (master) and secondary (slave) nameservers.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id647525"
class="indexterm"></a>
+ <a id="id647510" class="indexterm"></a>
+ recursive </span></dt><dd><div class="para">
+ Recursive nameservers offer resolution services, but they are not authoritative
for any zone. Answers for all resolutions are cached in a memory for a fixed period of
time, which is specified by the retrieved resource record.
+ </div></dd></dl></div><div class="para">
+ Although a nameserver can be both authoritative and recursive at the same time, it is
recommended not to combine the configuration types. To be able to perform their work,
authoritative servers should be available to all clients all the time. On the other hand,
since the recursive lookup takes far more time than authoritative responses, recursive
servers should be available to a restricted number of clients only, otherwise they are
prone to distributed denial of service (DDoS) attacks.
+ </div></div><div class="section"
id="s2-dns-introduction-bind"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-dns-introduction-bind">11.1.3. BIND as a
Nameserver</h3></div></div></div><a id="id647479"
class="indexterm"></a><a id="id647456"
class="indexterm"></a><a id="id647439"
class="indexterm"></a><a id="id647426"
class="indexterm"></a><a id="id647414"
class="indexterm"></a><a id="id647400"
class="indexterm"></a><div class="para">
+ BIND consists of a set of DNS-related programs. It contains a monolithic nameserver
called <code class="systemitem">named</code>, an administration
utility called <code class="command">rndc</code>, and a debugging
tool called <code class="command">dig</code>. Refer to <a
class="xref" href="ch-Services_and_Daemons.html">Chapter 7,
<em>Services and Daemons</em></a> for more information on how to
configure services in Fedora.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-dhcp-additional-resources.html"><strong>Prev</strong>10.6. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-BIND.html"><strong>Next</strong>11.2. BIND</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Date_and_Time_Configuration.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Date_and_Time_Configuration.html
new file mode 100644
index 0000000..7c6c50f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Date_and_Time_Configuration.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>Chapter 2. Date and Time 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Basic_System_Configuration.html" title="Part I. Basic System
Configuration" /><link rel="prev"
href="sect-Language_and_Keyboard_Configuration-Layouts.html"
title="1.2. Changing the Keyboard Layout" /><link rel="next"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"
title="2.2. Command Line 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 accesske
y="p"
href="sect-Language_and_Keyboard_Configuration-Layouts.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Date_and_Time_Configuration" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 2. Date and Time
Configuration</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">2.1.
Date and Time Configuration Tool</a></span></dt><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html">2.2.
Command Line
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">2.2.1.
Configuring the Dat
e and Time</a></span></dt><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">2.2.2.
Configuring the Network Time
Protocol</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Additional_Resources.html">2.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Additional_Resources.html#sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation">2.3.1.
Additional
Resources</a></span></dt></dl></dd></dl></div><div
class="para">
+ This chapter covers setting the system date and time in Fedora, both manually and using
the Network Time Protocol (<abbr class="abbrev">NTP</abbr>), as well
as setting the adequate time zone. Two methods are covered: setting the date and time
using the <span class="application"><strong>Date and
Time</strong></span> configuration tool, and doing so on the command line.
+ </div><div class="section"
id="sect-Date_and_Time_Configuration-Date_and_Time"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Date_and_Time_Configuration-Date_and_Time">2.1. Date and Time
Configuration Tool</h2></div></div></div><div
class="para">
+ The <span class="application"><strong>Date and
Time</strong></span> configuration tool allows a user to change the system
date and time, to configure the time zone used by the system, and to set up the Network
Time Protocol daemon to synchronize the system clock with a time server.
+ </div><div class="para">
+ To start the tool, select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Settings</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu and
click the <span class="guimenuitem"><strong>Date and
Time</strong></span> icon, or click the time in the panel and select <span
class="guibutton"><strong>Date and Time
Settings</strong></span> from the drop-down menu.
+ </div><div class="figure"
id="fig-Date_and_Time_Configuration-Time"><div
class="figure-contents"><div class="mediaobject"><img
src="images/date-and-time-panel.png" alt="Running the Date and Time
configuration tool" /><div class="longdesc"><div
class="para">
+ Running the Date and Time configuration tool
+ </div></div></div></div><h6>Figure 2.1. Running the
Date and Time configuration tool</h6></div><br
class="figure-break" /><div class="para">
+ By default, the tool only allows you to review the current settings. This is because
only <code class="systemitem">root</code> is allowed to set the
system date and time. To unlock the configuration tool for changes, click the <span
class="guibutton"><strong>Unlock</strong></span> button in
the bottom-left corner of the window, and provide the root password when prompted.
+ </div><div class="figure"
id="fig-Date_and_Time_Configuration-Date_and_Time"><div
class="figure-contents"><div class="mediaobject"><img
src="images/date-and-time-settings.png" alt="The Date and Time
configuration tool" /><div class="longdesc"><div
class="para">
+ The Date and Time configuration tool
+ </div></div></div></div><h6>Figure 2.2. The Date and
Time configuration tool</h6></div><br class="figure-break"
/><div class="para">
+ As you can see in <a class="xref"
href="ch-Date_and_Time_Configuration.html#fig-Date_and_Time_Configuration-Date_and_Time">Figure 2.2,
“The Date and Time configuration tool”</a>, the main window of the <span
class="application"><strong>Date and Time</strong></span>
configuration tool is divided into two parts: while the left side of the window is
dedicated to the time zone settings, the right part allows you to configure the date and
time itself.
+ </div><a id="id461171"
class="indexterm"></a><a id="id461184"
class="indexterm"></a><div class="para">
+ To change the time zone, click on the map, or select the region and city from the
<span class="guilabel"><strong>Region</strong></span>
and <span class="guilabel"><strong>City</strong></span>
drop-down lists.
+ </div><a id="id540835"
class="indexterm"></a><a id="id540848"
class="indexterm"></a><div class="para">
+ To change the current time of your system, either configure the system to synchronize
it over the network by clicking the <span
class="guilabel"><strong>Network Time</strong></span>
switch, or set it manually by clicking the up and down arrows above and below the numbers.
Use the <span class="guilabel"><strong>24-Hour
Time</strong></span> switch to enable or disable the 24-hour time format.
+ </div><a id="id540874"
class="indexterm"></a><a id="id483736"
class="indexterm"></a><div class="para">
+ To change the current date of your system, select a month from the drop-down list
below the time, and use the up and down arrows to choose the day and year.
+ </div><div class="para">
+ The changes take effect immediately.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Language_and_Keyboard_Configuration-Layouts.html"><strong>Prev</strong>1.2. Changing
the Keyboard Layout</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Next</strong>2.2. Command
Line Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Directory_Servers.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Directory_Servers.html
new file mode 100644
index 0000000..140b3fd
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Directory_Servers.html
@@ -0,0 +1,485 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 14. Directory Servers</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Servers.html" title="Part V. Servers" /><link
rel="prev" href="s2-email-related-books.html"
title="13.6.3. Related Books" /><link rel="next"
href="ch-File_and_Print_Servers.html" title="Chapter 15. File Servers"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-related-books.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="ch-Fi
le_and_Print_Servers.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-Directory_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 14. Directory
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Directory_Servers.html#s1-OpenLDAP">14.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-introduction">14.1.1. Introduction to
LDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-installation">14.1.2. Installing the
OpenLDAP Suite</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-configuration">14.1.3. Configuring an
OpenLDAP Server</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-running">14.1.4. Running an OpenLDAP
Server</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-pam">14.1.5. C
onfiguring a System to Authenticate Using
OpenLDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-resources">14.1.6. Additional
Resources</a></span></dt></dl></dd></dl></div><div
xml:lang="en-US" class="section" id="s1-OpenLDAP"
lang="en-US"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-OpenLDAP">14.1. OpenLDAP</h2></div></div></div><a
id="id674601" class="indexterm"></a><a
id="id674572" class="indexterm"></a><a
id="id674575" class="indexterm"></a><a
id="id674564" 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"
id="s2-ldap-introduction">14.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>Using Mozilla
NSS</h2></div><div class="admonition"><div
class="para">
+ The OpenLDAP suite in Fedora 15 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"
id="s3-ldap-terminology">14.1.1.1. LDAP
Terminology</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><dt
class="varlistentry"><span class="term"> <a
id="id674435" class="indexterm"></a>
+ entry </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="id674400"
class="indexterm"></a>
+ attribute </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="id674344"
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"
id="s3-ldap-features">14.1.1.2. OpenLDAP
Features</h4></div></div></div><a id="id674258"
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"
id="s3-ldap-setup">14.1.1.3. OpenLDAP Server
Setup</h4></div></div></div><a id="id674160"
class="indexterm"></a><div class="para">
+ The typical steps to set up an LDAP server on Fedora are as follows:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Install the OpenLDAP suite. Refer to <a class="xref"
href="ch-Directory_Servers.html#s2-ldap-installation">Section 14.1.2,
“Installing the OpenLDAP Suite”</a> for more information on required packages.
+ </div></li><li class="step"><div
class="para">
+ Customize the configuration as described in <a class="xref"
href="ch-Directory_Servers.html#s2-ldap-configuration">Section 14.1.3,
“Configuring an OpenLDAP Server”</a>.
+ </div></li><li class="step"><div
class="para">
+ Start the <code class="systemitem">slapd</code> service as
described in <a class="xref"
href="ch-Directory_Servers.html#s2-ldap-running">Section 14.1.4, “Running an
OpenLDAP Server”</a>.
+ </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"
id="s2-ldap-installation">14.1.2. Installing the OpenLDAP
Suite</h3></div></div></div><a id="id674076"
class="indexterm"></a><a id="id674051"
class="indexterm"></a><div class="para">
+ The suite of OpenLDAP libraries and tools is provided by the following packages:
+ </div><div class="table"
id="table-ldap-packages-openldap"><h6>Table 14.1. List of OpenLDAP
packages</h6><div class="table-contents"><table
summary="List of OpenLDAP packages"
border="1"><colgroup><col width="33%"
class="package" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Package
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="package">openldap</span>
+ </td><td>
+ A package containing the libraries necessary to run the OpenLDAP server and client
applications.
+ </td></tr><tr><td>
+ <span class="package">openldap-clients</span>
+ </td><td>
+ A package containing the command line utilities for viewing and modifying
directories on an LDAP server.
+ </td></tr><tr><td>
+ <span class="package">openldap-servers</span>
+ </td><td>
+ A package containing both the services and utilities to configure and run an LDAP
server. This includes the <em class="firstterm">Standalone LDAP
Daemon</em>, <code class="systemitem">slapd</code>.
+ </td></tr><tr><td>
+ <span class="package">openldap-servers-sql</span>
+ </td><td>
+ A package containing the SQL support module.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Additionally, the following packages are commonly used along with the LDAP server:
+ </div><div class="table"
id="table-ldap-packages-additional"><h6>Table 14.2. List of commonly
installed additional LDAP packages</h6><div
class="table-contents"><table summary="List of commonly installed
additional LDAP packages" border="1"><colgroup><col
width="33%" class="package" /><col width="67%"
class="description" /></colgroup><thead><tr><th>
+ Package
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="package">nss-pam-ldapd</span>
+ </td><td>
+ 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>
+ <span class="package">mod_authz_ldap</span>
+ </td><td>
+ <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">
+ To install these packages, use the <code
class="command">yum</code> command in the following form:
+ </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">
+ For example, to perform the basic LDAP server installation, 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
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">Section 4.2.4, “Installing
Packages”</a>.
+ </div><div class="section"
id="s3-ldap-packages-openldap-servers"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-packages-openldap-servers">14.1.2.1. Overview of OpenLDAP Server
Utilities</h4></div></div></div><a id="id673779"
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>Table 14.3. List of
OpenLDAP server utilities</h6><div class="table-contents"><table
summary="List of OpenLDAP server utilities"
border="1"><colgroup><col width="33%"
class="command" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">slapacl</code>
+ </td><td>
+ Allows you to check the access to a list of attributes.
+ </td></tr><tr><td>
+ <code class="command">slapadd</code>
+ </td><td>
+ Allows you to add entries from an LDIF file to an LDAP directory.
+ </td></tr><tr><td>
+ <code class="command">slapauth</code>
+ </td><td>
+ Allows you to check a list of IDs for authentication and authorization
permissions.
+ </td></tr><tr><td>
+ <code class="command">slapcat</code>
+ </td><td>
+ Allows you to pull entries from an LDAP directory in the default format and save
them in an LDIF file.
+ </td></tr><tr><td>
+ <code class="command">slapdn</code>
+ </td><td>
+ Allows you to check a list of Distinguished Names (DNs) based on available schema
syntax.
+ </td></tr><tr><td>
+ <code class="command">slapindex</code>
+ </td><td>
+ 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>
+ <code class="command">slappasswd</code>
+ </td><td>
+ 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>
+ <code class="command">slapschema</code>
+ </td><td>
+ Allows you to check the compliance of a database with the corresponding schema.
+ </td></tr><tr><td>
+ <code class="command">slaptest</code>
+ </td><td>
+ Allows you to check the LDAP server configuration.
+ </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">Section 14.1.6.1,
“Installed Documentation”</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">slapd</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>Stop
slapd before using these utilities</h2></div><div
class="admonition"><div class="para">
+ To preserve the data integrity, stop the <code
class="systemitem">slapd</code> service before using <code
class="command">slapadd</code>, <code
class="command">slapcat</code>, or <code
class="command">slapindex</code>. You can do so by typing 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">
+ For more information on how to start, stop, restart, and check the current status of
the <code class="systemitem">slapd</code> service, refer to <a
class="xref"
href="ch-Directory_Servers.html#s2-ldap-running">Section 14.1.4, “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"
id="s3-ldap-packages-openldap-clients">14.1.2.2. Overview of OpenLDAP Client
Utilities</h4></div></div></div><a id="id673474"
class="indexterm"></a><div class="para">
+ The <span class="package">openldap-clients</span> package
installs the following utilities which can be used to add, modify, and delete entries in
an LDAP directory:
+ </div><div class="table"
id="table-ldap-packages-openldap-clients"><h6>Table 14.4. List of
OpenLDAP client utilities</h6><div class="table-contents"><table
summary="List of OpenLDAP client utilities"
border="1"><colgroup><col width="33%"
class="command" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">ldapadd</code>
+ </td><td>
+ Allows you to add entries to an LDAP directory, either from a file, or from
standard input. It is a symbolic link to <code class="command">ldapmodify
-a</code>.
+ </td></tr><tr><td>
+ <code class="command">ldapcompare</code>
+ </td><td>
+ Allows you to compare given attribute with an LDAP directory entry.
+ </td></tr><tr><td>
+ <code class="command">ldapdelete</code>
+ </td><td>
+ Allows you to delete entries from an LDAP directory.
+ </td></tr><tr><td>
+ <code class="command">ldapexop</code>
+ </td><td>
+ Allows you to perform extended LDAP operations.
+ </td></tr><tr><td>
+ <code class="command">ldapmodify</code>
+ </td><td>
+ Allows you to modify entries in an LDAP directory, either from a file, or from
standard input.
+ </td></tr><tr><td>
+ <code class="command">ldapmodrdn</code>
+ </td><td>
+ Allows you to modify the RDN value of an LDAP directory entry.
+ </td></tr><tr><td>
+ <code class="command">ldappasswd</code>
+ </td><td>
+ Allows you to set or change the password for an LDAP user.
+ </td></tr><tr><td>
+ <code class="command">ldapsearch</code>
+ </td><td>
+ Allows you to search LDAP directory entries.
+ </td></tr><tr><td>
+ <code class="command">ldapurl</code>
+ </td><td>
+ Allows you to compose or decompose LDAP URLs.
+ </td></tr><tr><td>
+ <code class="command">ldapwhoami</code>
+ </td><td>
+ Allows you to perform a <code class="option">whoami</code>
operation on an LDAP server.
+ </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"
id="s3-ldap-packages-applications">14.1.2.3. Overview of Common LDAP Client
Applications</h4></div></div></div><a id="id673258"
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"
id="s2-ldap-configuration">14.1.3. Configuring an OpenLDAP
Server</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>Table 14.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>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id673179" class="indexterm"></a>
+ <code class="filename">/etc/openldap/ldap.conf</code>
+ </td><td>
+ 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>
+ <a id="id673132" class="indexterm"></a>
+ <code class="filename">/etc/openldap/slapd.d/</code>
+ </td><td>
+ 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">Section 14.1.2.1,
“Overview of OpenLDAP Server Utilities”</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"
id="s3-ldap-configuration-global">14.1.3.1. Changing the Global
Configuration</h4></div></div></div><a id="id673045"
class="indexterm"></a><a id="id673033"
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><dt
class="varlistentry"><span class="term"> <a
id="id673010" 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">Table 14.6,
“Available olcAllows options”</a>. The default option is <code
class="option">bind_v2</code>.
+ </div><div class="table"
id="table-ldap-configuration-olcallows"><h6>Table 14.6. Available
olcAllows options</h6><div class="table-contents"><table
summary="Available olcAllows options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">bind_v2</code>
+ </td><td>
+ Enables the acceptance of LDAP version 2 bind requests.
+ </td></tr><tr><td>
+ <code class="option">bind_anon_cred</code>
+ </td><td>
+ Enables an anonymous bind when the Distinguished Name (DN) is empty.
+ </td></tr><tr><td>
+ <code class="option">bind_anon_dn</code>
+ </td><td>
+ Enables an anonymous bind when the Distinguished Name (DN) is <span
class="emphasis"><em>not</em></span> empty.
+ </td></tr><tr><td>
+ <code class="option">update_anon</code>
+ </td><td>
+ Enables processing of anonymous update operations.
+ </td></tr><tr><td>
+ <code class="option">proxy_authz_anon</code>
+ </td><td>
+ 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>Example 14.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="id672822"
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">
+ The default option is <code class="option">100</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcconnmaxpending"><h6>Example 14.2. Using
the olcConnMaxPending directive</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="id672763"
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">
+ The default option is <code class="option">1000</code>.
+ </div><div class="example"
id="example-ldap-configuration-olcconnmaxpendingauth"><h6>Example 14.3. Using
the olcConnMaxPendingAuth directive</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="id672709"
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">Table 14.7,
“Available olcDisallows options”</a>. No features are disabled by default.
+ </div><div class="table"
id="table-ldap-configuration-olcdisallows"><h6>Table 14.7. Available
olcDisallows options</h6><div class="table-contents"><table
summary="Available olcDisallows options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">bind_anon</code>
+ </td><td>
+ Disables the acceptance of anonymous bind requests.
+ </td></tr><tr><td>
+ <code class="option">bind_simple</code>
+ </td><td>
+ Disables the simple bind authentication mechanism.
+ </td></tr><tr><td>
+ <code class="option">tls_2_anon</code>
+ </td><td>
+ Disables the enforcing of an anonymous session when the STARTTLS command is
received.
+ </td></tr><tr><td>
+ <code class="option">tls_authc</code>
+ </td><td>
+ 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>Example 14.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="id672536"
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">
+ This option is disabled by default (that is, set to <code
class="option">0</code>).
+ </div><div class="example"
id="example-ldap-configuration-olcidletimeout"><h6>Example 14.5. Using
the olcIdleTimeout directive</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="id672468"
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>Example 14.6. Using the
olcLogFile directive</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="id672402" 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">
+ This option is disabled by default.
+ </div><div class="example"
id="example-ldap-configuration-olcreferral"><h6>Example 14.7. Using the
olcReferral directive</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="id672354" 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">
+ This option is disabled by default (that is, set to <code
class="option">0</code>).
+ </div><div class="example"
id="example-ldap-configuration-olcwritetimeout"><h6>Example 14.8. Using
the olcWriteTimeout directive</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"
id="s3-ldap-configuration-database">14.1.3.2. Changing the Database-Specific
Configuration</h4></div></div></div><a id="id672281"
class="indexterm"></a><a id="id672272"
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><dt
class="varlistentry"><span class="term"> <a
id="id672247" 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>Example 14.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="id672183"
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>Example 14.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="id672110" 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>Example 14.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="id672030" 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>Example 14.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"
id="s3-ldap-configuration-schema">14.1.3.3. Extending
Schema</h4></div></div></div><a id="id671958"
class="indexterm"></a><a id="id671948"
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://...;.
+ </div></div></div><div class="section"
id="s2-ldap-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ldap-running">14.1.4. Running an OpenLDAP
Server</h3></div></div></div><a id="id671901"
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">Chapter 7, <em>Services and
Daemons</em></a>.
+ </div><div class="section"
id="s3-ldap-running-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-running-starting">14.1.4.1. Starting the
Service</h4></div></div></div><a id="id671873"
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">
+ If you want the service to start automatically at the boot time, use the following
command:
+ </div><pre class="screen"><code
class="command">systemctl enable
slapd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-ldap-running-stopping"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-running-stopping">14.1.4.2. Stopping the
Service</h4></div></div></div><a id="id671816"
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">
+ To prevent the service from starting automatically at the boot time, type:
+ </div><pre class="screen"><code
class="command">systemctl disable
slapd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-ldap-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-running-restarting">14.1.4.3. Restarting the
Service</h4></div></div></div><a id="id671768"
class="indexterm"></a><div class="para">
+ To restart 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 restart
slapd.service</code></pre><div class="para">
+ This stops the service, and then starts it again. Use this command to reload the
configuration.
+ </div></div><div class="section"
id="s3-ldap-running-status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ldap-running-status">14.1.4.4. Checking the Service
Status</h4></div></div></div><a id="id671722"
class="indexterm"></a><div class="para">
+ To check whether the service is running, type the following at a shell prompt:
+ </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"
id="s2-ldap-pam">14.1.5. Configuring a System to Authenticate Using
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">Section 14.1.2,
“Installing the OpenLDAP Suite”</a> and <a class="xref"
href="ch-Directory_Servers.html#s2-ldap-configuration">Section 14.1.3,
“Configuring an OpenLDAP Server”</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">Chapter 8, <em>Configuring
Authentication</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"
id="s3-ldap-migrationtools">14.1.5.1. Migrating Old Authentication
Information to LDAP Format</h4></div></div></div><a
id="id671662" 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">Table 14.8,
“Commonly used LDAP migration scripts”</a>.
+ </div><div class="table"
id="table-ldap-migrationtools"><h6>Table 14.8. Commonly used LDAP
migration scripts</h6><div class="table-contents"><table
summary="Commonly used LDAP migration scripts"
border="1"><colgroup><col width="30%"
class="existing" /><col width="20%" class="running"
/><col width="50%" class="use"
/></colgroup><thead><tr><th>
+ Existing Name Service
+ </th><th>
+ Is LDAP Running?
+ </th><th>
+ Script to Use
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc</code> flat files
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_online.sh</code>
+ </td></tr><tr><td>
+ <code class="filename">/etc</code> flat files
+ </td><td>
+ no
+ </td><td>
+ <code class="filename">migrate_all_offline.sh</code>
+ </td></tr><tr><td>
+ NetInfo
+ </td><td>
+ yes
+ </td><td>
+ <code
class="filename">migrate_all_netinfo_online.sh</code>
+ </td></tr><tr><td>
+ NetInfo
+ </td><td>
+ no
+ </td><td>
+ <code
class="filename">migrate_all_netinfo_offline.sh</code>
+ </td></tr><tr><td>
+ NIS (YP)
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_nis_online.sh</code>
+ </td></tr><tr><td>
+ NIS (YP)
+ </td><td>
+ no
+ </td><td>
+ <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"
id="s2-ldap-resources">14.1.6. Additional
Resources</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"
id="s3-ldap-installed-docs">14.1.6.1. Installed
Documentation</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><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><dt
class="varlistentry"><span class="term">Client
Applications</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">Server
Applications</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">Administrative
Applications</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">Configuration
Files</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"
id="s3-ldap-additional-resources-web">14.1.6.2. Useful
Websites</h4></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://www.openldap.org/doc/admin24/">http://www.openl...
class="para">
+ The current version of the <em class="citetitle">OpenLDAP Software
Administrator's Guide</em>.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.kingsmountain.com/ldapRoadmap.shtml">http:/...
class="para">
+ Jeff Hodges' <em class="citetitle">LDAP Roadmap &
FAQ</em> containing links to several useful resources and emerging news concerning
the LDAP protocol.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.ldapman.org/articles/">http://www.ldapman.o...
class="para">
+ A collection of articles that offer a good introduction to LDAP, including methods
to design a directory tree and customizing directory structures.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.padl.com/">http://www.padl.com/</a>&l...
class="para">
+ A website of developers of several useful LDAP tools.
+ </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"
id="s3-ldap-related-books">14.1.6.3. Related
Books</h4></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><em
class="citetitle">OpenLDAP by Example</em> by John Terpstra and
Benjamin Coles; Prentice Hall.</span></dt><dd><div
class="para">
+ A collection of practical exercises in the OpenLDAP deployment.
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">Implementing
LDAP</em> by Mark Wilcox; Wrox Press, Inc.</span></dt><dd><div
class="para">
+ A book covering LDAP from both the system administrator's and software
developer's perspective.
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">Understanding and
Deploying LDAP Directory Services</em> by Tim Howes et al.; Macmillan Technical
Publishing.</span></dt><dd><div class="para">
+ A book covering LDAP design principles, as well as its deployment in a production
environment.
+ </div></dd></dl></div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-email-related-books.html"><strong>Prev</strong>13.6.3. Related
Books</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-File_and_Print_Servers.html"><strong>Next</strong>Chapter 15. File
Servers</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-File_and_Print_Servers.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-File_and_Print_Servers.html
new file mode 100644
index 0000000..72c817c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-File_and_Print_Servers.html
@@ -0,0 +1,661 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 15. File Servers</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Servers.html" title="Part V. Servers" /><link
rel="prev" href="ch-Directory_Servers.html"
title="Chapter 14. Directory Servers" /><link rel="next"
href="s1-FTP.html" title="15.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-FTP.html"><strong>Next</strong><
/a></li></ul><div xml:lang="en-US" class="chapter"
id="ch-File_and_Print_Servers" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 15. File
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-File_and_Print_Servers.html#s1-Samba">15.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#samba-rgs-overview">15.1.1. Introduction
to Samba</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-daemons">15.1.2. Samba Daemons
and Related Services</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-connect-share">15.1.3.
Connecting to a Samba Share</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-configuring">15.1.4.
Configuring a Samba Server</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-startstop">15.1.5. Starting and
Sto
pping Samba</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-servers">15.1.6. Samba Server
Types and the <code class="filename">smb.conf</code>
File</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">15.1.7. Samba
Security Modes</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">15.1.8. Samba
Account Information Databases</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">15.1.9. Samba
Network Browsing</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-cups">15.1.10. Samba with CUPS
Printing Support</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-programs">15.1.11. Samba
Distribution Programs</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-resource
s">15.1.12. Additional
Resources</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-FTP.html">15.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-FTP.html#s2-ftp-protocol">15.2.1.
The File Transfer Protocol</a></span></dt><dt><span
class="section"><a href="s2-ftp-servers.html">15.2.2. FTP
Servers</a></span></dt><dt><span
class="section"><a href="s3-ftp-vsftpd-conf.html">15.2.3.
Files Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-start.html">15.2.4. Starting and Stopping <code
class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-conf.html">15.2.5. <code
class="command">vsftpd</code> Configuration
Options</a></span></dt><dt><span
class="section"><a href="s2-ftp-resources.html">15.2.6.
Additional
Resources</a></span></dt></dl></dd></dl></div><div
xml:lang="en-US" class="section" id="s1-Samba"
lang="en-US"><div class="titlepage"><div><di
v keep-together.within-column="always"><h2 class="title"
id="s1-Samba">15.1. Samba</h2></div></div></div><a
id="id678658" class="indexterm"></a><a
id="id678640" 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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="section"
id="samba-rgs-overview"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="samba-rgs-overview">15.1.1. Introduction to
Samba</h3></div></div></div><a id="id678552"
class="indexterm"></a><div class="para">
+ The third major release of Samba, version 3.0.0, introduced numerous improvements from
prior versions, including:
+ </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">
+ Built in Unicode support for internationalization
+ </div></li><li class="listitem"><div
class="para">
+ Support for all recent Microsoft Windows server and client versions to connect to
Samba servers without needing local registry hacking
+ </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">Section 15.1.12.2,
“Related Books”</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"
id="s3-samba-abilities">15.1.1.1. Samba
Features</h4></div></div></div><a id="id678457"
class="indexterm"></a><div class="para">
+ Samba is a powerful and versatile server application. Even seasoned system
administrators must know its abilities and limitations before attempting installation and
configuration.
+ </div><div class="para">
+ What Samba can do:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Serve directory trees and printers to Linux, UNIX, and Windows clients
+ </div></li><li class="listitem"><div
class="para">
+ Assist in network browsing (with or without NetBIOS)
+ </div></li><li class="listitem"><div
class="para">
+ Authenticate Windows domain logins
+ </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">
+ Act as an Active Directory domain member server
+ </div></li><li class="listitem"><div
class="para">
+ Join a Windows NT/2000/2003/2008 PDC
+ </div></li></ul></div><div class="para">
+ What Samba cannot do:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Act as a BDC for a Windows PDC (and vice versa)
+ </div></li><li class="listitem"><div
class="para">
+ Act as an Active Directory domain controller
+ </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"
id="s2-samba-daemons">15.1.2. Samba Daemons and Related
Services</h3></div></div></div><a id="id678303"
class="indexterm"></a><div class="para">
+ The following is a brief introduction to the individual Samba daemons and services.
+ </div><div class="section"
id="s3-samba-services"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-services">15.1.2.1. Samba
Daemons</h4></div></div></div><a id="id678273"
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> <code class="command">smbd</code>
</h5><a id="id678215" 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">
+ The <code class="command">smbd</code> daemon is controlled by
the <code class="command">smb</code> service.
+ </div><h5> <code class="command">nmbd</code>
</h5><a id="id678140" 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">
+ The <code class="command">nmbd</code> daemon is controlled by
the <code class="command">nmb</code> service.
+ </div><h5> <code class="command">winbindd</code>
</h5><a id="id678060" 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">Section 15.1.11,
“Samba Distribution Programs”</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"
id="s2-samba-connect-share">15.1.3. Connecting to a Samba
Share</h3></div></div></div><a id="id677951"
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>Figure 15.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"
id="s3-samba-connect-share-cmdline">15.1.3.1. Command
Line</h4></div></div></div><a id="id677804"
class="indexterm"></a><a id="id677789"
class="indexterm"></a><a id="id677770"
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="id677736"
class="indexterm"></a><a id="id677716"
class="indexterm"></a><div class="para">
+ To connect to a Samba share from a shell prompt, type the following command:
+ </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"
id="s2-samba-mounting">15.1.3.2. Mounting the
Share</h4></div></div></div><a id="id677257"
class="indexterm"></a><div class="para">
+ Sometimes it is useful to mount a Samba share to a directory so that the files in the
directory can be treated as if they are part of the local file system.
+ </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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div><div class="para">
+ Note that the <span class="package">cifs-utils</span> package
also contains the <span
class="application"><strong>cifs.upcall</strong></span>
binary called by the kernel in order to perform kerberized CIFS mounts. For more
information on <span
class="application"><strong>cifs.upcall</strong></span>,
refer to <code class="command">man cifs.upcall</code>.
+ </div></div></div><div class="para">
+ For more information about mounting a samba share, refer to <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"
id="s2-samba-configuring">15.1.4. Configuring a Samba
Server</h3></div></div></div><a id="id677418"
class="indexterm"></a><a id="id677403"
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"
id="s3-samba-configuring-gui">15.1.4.1. Graphical
Configuration</h4></div></div></div><a id="id677368"
class="indexterm"></a><div class="para">
+ To configure Samba using a graphical interface, use one of the available Samba
graphical user interfaces. A list of available GUIs can be found at <a
href="http://www.samba.org/samba/GUI/">http://www.samba.org/...;.
+ </div></div><div class="section"
id="s3-samba-configuring-cmdline"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-configuring-cmdline">15.1.4.2. Command Line
Configuration</h4></div></div></div><a id="id562183"
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">
+ Replace <em
class="replaceable"><code>WORKGROUPNAME</code></em> with
the name of the Windows workgroup to which this machine should belong. The <em
class="replaceable"><code>BRIEF COMMENT ABOUT
SERVER</code></em> is optional and is used as the Windows comment about the
Samba system.
+ </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"
id="s3-samba-encrypted-passwords">15.1.4.3. Encrypted
Passwords</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="id562936"
class="indexterm"></a><a id="id599310"
class="indexterm"></a><a id="id619059"
class="indexterm"></a><a id="id553962"
class="indexterm"></a><a id="id671122"
class="indexterm"></a><a id="id481400"
class="indexterm"></a><a id="id557138"
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"
id="s2-samba-startstop">15.1.5. Starting and Stopping
Samba</h3></div></div></div><a id="id678542"
class="indexterm"></a><a id="id469097"
class="indexterm"></a><a id="id536840"
class="indexterm"></a><a id="id509786"
class="indexterm"></a><a id="id505581"
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>Setting up a domain member
server</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">
+ To stop the server, type the following command in a shell prompt, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl stop smb.service</code></pre><div
class="para">
+ The <code class="option">restart</code> option is a quick way of
stopping and then starting Samba. This is the most reliable way to make configuration
changes take effect after editing the configuration file for Samba. Note that the restart
option starts the daemon even if it was not running originally.
+ </div><div class="para">
+ To restart the server, type the following command in a shell prompt, as <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">Chapter 7,
<em>Services and Daemons</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"
id="s2-samba-servers">15.1.6. Samba Server Types and the <code
class="filename">smb.conf</code>
File</h3></div></div></div><a id="id562323"
class="indexterm"></a><a id="id428260"
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"
id="s3-samba-standalone">15.1.6.1. Stand-alone
Server</h4></div></div></div><a id="id677292"
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">Section 15.1.7,
“Samba Security Modes”</a>.
+ </div><div class="section"
id="s4-samba-standalone-anonreadonly"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s4-samba-standalone-anonreadonly">15.1.6.1.1. Anonymous
Read-Only</h5></div></div></div><a id="id584504"
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"
id="s4-samba-standalone-anonreadwrite">15.1.6.1.2. Anonymous
Read/Write</h5></div></div></div><a id="id562933"
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"
id="s4-samba-standalone-anonprint">15.1.6.1.3. Anonymous Print
Server</h5></div></div></div><a id="id596953"
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"
id="s4-samba-standalone-readwriteall">15.1.6.1.4. Secure Read/Write File and
Print Server</h5></div></div></div><a id="id621215"
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"
id="s3-samba-domain-member">15.1.6.2. Domain Member
Server</h4></div></div></div><a id="id543682"
class="indexterm"></a><div class="para">
+ A domain member, while similar to a stand-alone server, is logged into a domain
controller (either Windows or Samba) and is subject to the domain's security rules. An
example of a domain member server would be a departmental server running Samba that has a
machine account on the Primary Domain Controller (PDC). All of the department's
clients still authenticate with the PDC, and desktop profiles and all network policy files
are included. The difference is that the departmental server has the ability to control
printer and network shares.
+ </div><div class="section"
id="s4-samba-domain-member-ads"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s4-samba-domain-member-ads">15.1.6.2.1. Active Directory Domain Member
Server</h5></div></div></div><a id="id643172"
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">
+ In order to join a member server to an Active Directory domain, the following steps
must be completed:
+ </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">
+ Creation of the machine account on the Active Directory domain server
+ </div></li><li class="listitem"><div
class="para">
+ Association of the member server to the Active Directory domain
+ </div></li></ul></div><div class="para">
+ To create the machine account and join the Windows 2000/2003/2008 Active Directory,
Kerberos must first be initialized for the member server wishing to join the Active
Directory domain. To create an administrative Kerberos ticket, type the following command
as <code class="systemitem">root</code> on the member server:
+ </div><pre class="screen"><code
class="command">kinit
administrator(a)EXAMPLE.COM</code></pre><div class="para">
+ The <code class="command">kinit</code> command is a Kerberos
initialization script that references the Active Directory administrator account and
Kerberos realm. Since Active Directory requires Kerberos tickets, <code
class="command">kinit</code> obtains and caches a Kerberos
ticket-granting ticket for client/server authentication. 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"
id="s4-samba-domain-member-nt4">15.1.6.2.2. Windows NT4-based Domain Member
Server</h5></div></div></div><a id="id443467"
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"
id="s3-samba-domain-controller">15.1.6.3. Domain
Controller</h4></div></div></div><a id="id554600"
class="indexterm"></a><div class="para">
+ A domain controller in Windows NT is functionally similar to a Network Information
Service (NIS) server in a Linux environment. Domain controllers and NIS servers both host
user/group information databases as well as related services. Domain controllers are
mainly used for security, including the authentication of users accessing domain
resources. The service that maintains the user/group database integrity is called the
<em class="firstterm">Security Account Manager</em> (SAM). The SAM
database is stored differently between Windows and Linux Samba-based systems, therefore
SAM replication cannot be achieved and platforms cannot be mixed in a PDC/BDC
environment.
+ </div><div class="para">
+ In a Samba environment, there can be only one PDC and zero or more BDCs.
+ </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 cannot exist in a mixed Samba/Windows domain controller environment (Samba
cannot be a BDC of a Windows PDC or vice versa). Alternatively, Samba PDCs and BDCs
<span class="emphasis"><em>can</em></span> coexist.
+ </div></div></div><div class="section"
id="s4-samba-pdc-tdbsam"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s4-samba-pdc-tdbsam">15.1.6.3.1. Primary Domain Controller (PDC) using
<code class="command">tdbsam</code>
</h5></div></div></div><a id="id508439"
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">Section 15.1.8,
“Samba Account Information Databases”</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"
id="samba-rgs-pdc-ads">15.1.6.3.2. Primary Domain Controller (PDC) with
Active Directory</h5></div></div></div><a
id="id670970" class="indexterm"></a><div
class="para">
+ Although it is possible for Samba to be a member of an Active Directory, it is not
possible for Samba to operate as an Active Directory domain controller.
+ </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"
id="s2-samba-security-modes">15.1.7. Samba Security
Modes</h3></div></div></div><a id="id609451"
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"
id="s3-samba-user-level">15.1.7.1. User-Level
Security</h4></div></div></div><a id="id424402"
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">
+ The following sections describe other implementations of user-level security.
+ </div><div class="section"
id="s3-samba-domain-security-mode"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s3-samba-domain-security-mode">15.1.7.1.1. Domain Security Mode
(User-Level Security)</h5></div></div></div><a
id="id437200" 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"
id="s3-samba-ads-security-mode">15.1.7.1.2. Active Directory Security Mode
(User-Level Security)</h5></div></div></div><a
id="id555117" class="indexterm"></a><div
class="para">
+ If you have an Active Directory environment, it is possible to join the domain as a
native Active Directory member. Even if a security policy restricts the use of
NT-compatible authentication protocols, the Samba server can join an ADS using Kerberos.
Samba in Active Directory member mode can accept Kerberos tickets.
+ </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"
id="s3-samba-server-security-mode">15.1.7.1.3. Server Security Mode
(User-Level Security)</h5></div></div></div><a
id="id621811" class="indexterm"></a><div
class="para">
+ Server security mode was previously used when Samba was not capable of acting as a
domain member server.
+ </div><div class="note"><div
class="admonition_header"><h2>Avoid using the server security
mode</h2></div><div class="admonition"><div
class="para">
+ It is highly recommended to <span
class="emphasis"><em>not</em></span> use this mode since
there are numerous security drawbacks.
+ </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"
id="s3-samba-share-level">15.1.7.2. Share-Level
Security</h4></div></div></div><a id="id595860"
class="indexterm"></a><div class="para">
+ With share-level security, the server accepts only a password without an explicit
username from the client. The server expects a password for each share, independent of the
username. There have been recent reports that Microsoft Windows clients have compatibility
issues with share-level security servers. Samba developers strongly discourage use of
share-level security.
+ </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"
id="s2-samba-account-info-dbs">15.1.8. Samba Account Information
Databases</h3></div></div></div><a id="id480293"
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="id464322"
class="indexterm"></a><a id="id612994"
class="indexterm"></a><a id="id449892"
class="indexterm"></a><a id="id562534"
class="indexterm"></a><a id="id420942"
class="indexterm"></a><a id="id621818"
class="indexterm"></a><a id="id624165"
class="indexterm"></a><a id="id560754"
class="indexterm"></a><a id="id558321"
class="indexterm"></a><div
class="variablelist"><dl><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">Section 14.1,
“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">Section 14.1.3.3,
“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"
id="s2-samba-network-browsing">15.1.9. Samba Network
Browsing</h3></div></div></div><a id="id553682"
class="indexterm"></a><a id="id549481"
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">
+ A domain master browser collates the browse lists from local master browsers on all
subnets so that browsing can occur between workgroups and subnets. Also, the domain master
browser should preferably be the local master browser for its own subnet.
+ </div><div class="section"
id="s3-samba-domain-browsing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-domain-browsing">15.1.9.1. Domain
Browsing</h4></div></div></div><a id="id552311"
class="indexterm"></a><div class="para">
+ By default, a Windows server PDC for a domain is also the domain master browser for
that domain. A Samba server must <span
class="emphasis"><em>not</em></span> be set up as a domain
master server in this type of situation
+ </div><div class="para">
+ For subnets that do not include the Windows server PDC, a Samba server can be
implemented as a local master browser. Configuring the <code
class="filename">/etc/samba/smb.conf</code> file for a local master
browser (or no browsing at all) in a domain controller environment is the same as
workgroup configuration.
+ </div></div><div class="section"
id="s3-samba-wins"><div class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-wins">15.1.9.2. WINS (Windows Internet Name
Server)</h4></div></div></div><a id="id432025"
class="indexterm"></a><a id="id535382"
class="indexterm"></a><div class="para">
+ Either a Samba server or a Windows NT server can function as a WINS server. When a
WINS server is used with NetBIOS enabled, UDP unicasts can be routed which allows name
resolution across networks. Without a WINS server, the UDP broadcast is limited to the
local subnet and therefore cannot be routed to other subnets, workgroups, or domains. If
WINS replication is necessary, do not use Samba as your primary WINS server, as Samba does
not currently support WINS replication.
+ </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>Using WINS</h2></div><div
class="admonition"><div class="para">
+ All servers (including Samba) should connect to a WINS server to resolve NetBIOS
names. Without WINS, browsing only occurs on the local subnet. Furthermore, even if a
domain-wide list is somehow obtained, hosts cannot be resolved for the client without
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"
id="s2-samba-cups">15.1.10. Samba with CUPS Printing
Support</h3></div></div></div><a id="id506935"
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"
id="s3-samba-cups-smb.conf">15.1.10.1. Simple <code
class="filename">smb.conf</code>
Settings</h4></div></div></div><a id="id621268"
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">
+ Other printing configurations are also possible. To add additional security and
privacy for printing confidential documents, users can have their own print spooler not
located in a public path. If a job fails, other users would not have access to the file.
+ </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"
id="s2-samba-programs">15.1.11. Samba Distribution
Programs</h3></div></div></div><a id="id478810"
class="indexterm"></a><h4> <code
class="filename">findsmb</code> </h4><a
id="id505945" class="indexterm"></a><a
id="id625862" 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> <code
class="filename">net</code> </h4><a id="id591765"
class="indexterm"></a><a id="id638434"
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> <code
class="filename">nmblookup</code> </h4><a
id="id555486" class="indexterm"></a><a
id="id631583" 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">
+ Here is an example:
+ </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> <code
class="filename">pdbedit</code> </h4><a
id="id594959" class="indexterm"></a><a
id="id638751" 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">
+ The following are examples of adding, deleting, and listing users:
+ </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> <code
class="filename">rpcclient</code> </h4><a
id="id562181" class="indexterm"></a><a
id="id506220" 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> <code class="filename">smbcacls</code>
</h4><a id="id553672" class="indexterm"></a><a
id="id608018" 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> <code class="filename">smbclient</code>
</h4><a id="id506311" class="indexterm"></a><a
id="id639196" 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> <code class="filename">smbcontrol</code>
</h4><a id="id544344" class="indexterm"></a><a
id="id564263" 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> <code class="filename">smbpasswd</code>
</h4><a id="id477965" class="indexterm"></a><a
id="id590497" 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> <code class="filename">smbspool</code>
</h4><a id="id445370" class="indexterm"></a><a
id="id469446" 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> <code class="filename">smbstatus</code>
</h4><a id="id635008" class="indexterm"></a><a
id="id610762" 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> <code class="filename">smbtar</code>
</h4><a id="id555348" class="indexterm"></a><a
id="id444606" 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> <code class="filename">testparm</code>
</h4><a id="id616908" class="indexterm"></a><a
id="id478322" 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">
+ For example:
+ </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> <code
class="filename">wbinfo</code> </h4><a id="id639960"
class="indexterm"></a><a id="id649253"
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"
id="s2-samba-resources">15.1.12. Additional
Resources</h3></div></div></div><a id="id583751"
class="indexterm"></a><div class="para">
+ The following sections give you the means to explore Samba in greater detail.
+ </div><div class="section"
id="s3-samba-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-samba-resources-installed">15.1.12.1. Installed
Documentation</h4></div></div></div><a id="id563378"
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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</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"
id="s3-samba-resources-published">15.1.12.2. Related
Books</h4></div></div></div><a id="id509961"
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"
id="s3-samba-resources-community">15.1.12.3. Useful
Websites</h4></div></div></div><a id="id421416"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.samba.org/">http://www.samba.org/</a> —
Homepage for the Samba distribution and all official documentation created by the Samba
development team. Many resources are available in HTML and PDF formats, while others are
only available for purchase. Although many of these links are not Fedora specific, some
concepts may apply.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://us1.samba.org/samba/archives.html">http://samba...
</a> — Active email lists for the Samba community. Enabling digest mode is
recommended due to high levels of list activity.
+ </div></li><li class="listitem"><div
class="para">
+ Samba newsgroups — Samba threaded newsgroups, such as
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>Prev</strong>Chapter 14. Directory
Servers</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-FTP.html"><strong>Next</strong>15.2. FTP</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html
new file mode 100644
index 0000000..cf60b5f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.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>5.4. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-PackageKit.html" title="Chapter 5. PackageKit" /><link
rel="prev" href="sec-PackageKit_Architecture.html"
title="5.3. PackageKit Architecture" /><link rel="next"
href="part-Networking.html" title="Part III. Networking"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" h
ref="part-Networking.html"><strong>Next</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"
id="ch-Graphical_Package_Management-sec-Additional_Resources">5.4. Additional
Resources</h2></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <span
class="application"><strong>PackageKit</strong></span> home
page — <a
href="http://www.packagekit.org/index.html">http://www.packa...
</span></dt><dd><div class="para">
+ Information about and mailing lists for <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.pack...
</span></dt><dd><div class="para">
+ An informative list of Frequently Asked Questions for the <span
class="application"><strong>PackageKit</strong></span>
software suite.
+ </div></dd><dt class="varlistentry"><span
class="term"> <span
class="application"><strong>PackageKit</strong></span>
Feature Matrix — <a
href="http://www.packagekit.org/pk-matrix.html">http://www.p...
</span></dt><dd><div class="para">
+ Cross-reference <span
class="application"><strong>PackageKit</strong></span>-provided
features with the long list of package manager back ends.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-PackageKit_Architecture.html"><strong>Prev</strong>5.3. PackageKit
Architecture</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="part-Networking.html"><strong>Next</strong>Part III. Networking</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Language_and_Keyboard_Configuration.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Language_and_Keyboard_Configuration.html
new file mode 100644
index 0000000..4e10942
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Language_and_Keyboard_Configuration.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>Chapter 1. Language and Keyboard Configuration</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Basic_System_Configuration.html" title="Part I. Basic System
Configuration" /><link rel="prev"
href="part-Basic_System_Configuration.html" title="Part I. Basic System
Configuration" /><link rel="next"
href="sect-Language_and_Keyboard_Configuration-Layouts.html"
title="1.2. Changing the Keyboard Layout" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="part-Basic_S
ystem_Configuration.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Language_and_Keyboard_Configuration-Layouts.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Language_and_Keyboard_Configuration" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 1. Language and Keyboard
Configuration</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Language_and_Keyboard_Configuration.html#sect-Language_and_Keyboard_Configuration-Language">1.1.
Changing the Language</a></span></dt><dt><span
class="section"><a
href="sect-Language_and_Keyboard_Configuration-Layouts.html">1.2. Changing
the Keyboard Layout</a></span></dt></dl></div><div
class="para">
+ This chapter describes how to change the language of your desktop, configure the
keyboard layout, and allow a user to switch between different keyboard layouts using the
<span class="application"><strong>Region and
Language</strong></span> configuration tool.
+ </div><div class="section"
id="sect-Language_and_Keyboard_Configuration-Language"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Language_and_Keyboard_Configuration-Language">1.1. Changing the
Language</h2></div></div></div><a id="id508088"
class="indexterm"></a><a id="id506268"
class="indexterm"></a><div class="para">
+ To configure the language of your desktop, open the <span
class="application"><strong>System Settings</strong></span>
dialog window by selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Settings</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu,
click <span class="guimenuitem"><strong>Region and
Language</strong></span>, and select the <span
class="guilabel"><strong>Language</strong></span> tab. You
will be presented with a list of available languages.
+ </div><div class="figure"
id="fig-Language_and_Keyboard_Configuration-Language"><div
class="figure-contents"><div class="mediaobject"><img
src="images/region-and-language-language.png" alt="Changing the
language" /><div class="longdesc"><div
class="para">
+ Changing the language
+ </div></div></div></div><h6>Figure 1.1. Changing the
language</h6></div><br class="figure-break" /><div
class="para">
+ To choose a particular language, select it from the list and either close the window,
or click the <span class="guibutton"><strong>All
Settings</strong></span> button in the upper-left corner of the window to
return to the <span class="application"><strong>System
Settings</strong></span> window. The changes will take effect the next time
you log in to your system.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="part-Basic_System_Configuration.html"><strong>Prev</strong>Part I. Basic
System Configuration</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Language_and_Keyboard_Configuration-Layouts.html"><strong>Next</strong>1.2. Changing
the Keyboard Layout</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Mail_Servers.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Mail_Servers.html
new file mode 100644
index 0000000..1cecc9a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Mail_Servers.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>Chapter 13. Mail Servers</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Servers.html" title="Part V. Servers" /><link
rel="prev" href="ch-Web_Servers.html" title="Chapter 12. Web
Servers" /><link rel="next" href="s1-email-types.html"
title="13.2. Email Program Classifications" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s1-email-types.html
"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-Mail_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 13. Mail
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Mail_Servers.html#s1-email-protocols">13.1. Email
Protocols</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-send">13.1.1. Mail Transport
Protocols</a></span></dt><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-client">13.1.2. Mail Access
Protocols</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-types.html">13.2. Email
Program
Classifications</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-types.html#s2-email-types-mta">13.2.1. Mail Transport
Agent</a></span></dt><dt><span
class="section"><a href="s2-email-types-mda.html">13.2.2.
Mail Delivery Agent</a></span></dt><dt><span
class="section"><a href=
"s2-email-types-mua.html">13.2.3. Mail User
Agent</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mta.html">13.3. Mail
Transport Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mta.html#s2-email-mta-postfix">13.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="s2-email-mta-sendmail.html">13.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="s2-email-mta-fetchmail.html">13.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="s2-email-switchmail.html">13.3.4.
Mail Transport Agent (MTA)
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mda.html">13.4. Mail
Delivery Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mda.html#s2-email-procmail-configuration">13.4.1. Procmail
Configuration</a></span></dt><dt><span
class="section"><a
href="s2-email-procmail-recipes.html">13.4.2. Procmail
Recipes</a></span></dt></dl></dd><dt><span
class="sectio
n"><a href="s1-email-mua.html">13.5. Mail User
Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mua.html#s2-email-security">13.5.1. Securing
Communication</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-email-additional-resources.html">13.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-additional-resources.html#s2-email-installed-docs">13.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-email-useful-websites.html">13.6.2. Useful
Websites</a></span></dt><dt><span
class="section"><a href="s2-email-related-books.html">13.6.3.
Related
Books</a></span></dt></dl></dd></dl></div><a
id="id431423" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Email</em> was born in the 1960s. The
mailbox was a file in a user's home directory that was readable only by that user.
Primitive mail applications appended new text messages to the bottom of the file, making
the user wade through the constantly growing file to find any particular message. This
system was only capable of sending messages to users on the same system.
+ </div><div class="para">
+ The first network transfer of an electronic mail message file took place in 1971 when a
computer engineer named Ray Tomlinson sent a test message between two machines via
ARPANET—the precursor to the Internet. Communication via email soon became very popular,
comprising 75 percent of ARPANET's traffic in less than two years.
+ </div><div class="para">
+ Today, email systems based on standardized network protocols have evolved into some of
the most widely used services on the Internet. Fedora offers many advanced applications to
serve and access email.
+ </div><div class="para">
+ This chapter reviews modern email protocols in use today, and some of the programs
designed to send and receive email.
+ </div><div class="section"
id="s1-email-protocols"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-email-protocols">13.1. Email
Protocols</h2></div></div></div><a id="id541370"
class="indexterm"></a><div class="para">
+ Today, email is delivered using a client/server architecture. An email message is
created using a mail client program. This program then sends the message to a server. The
server then forwards the message to the recipient's email server, where the message is
then supplied to the recipient's email client.
+ </div><div class="para">
+ To enable this process, a variety of standard network protocols allow different
machines, often running different operating systems and using different email programs, to
send and receive email.
+ </div><div class="para">
+ The following protocols discussed are the most commonly used in the transfer of
email.
+ </div><div class="section"
id="s2-email-protocols-send"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-protocols-send">13.1.1. Mail Transport
Protocols</h3></div></div></div><div
class="para">
+ Mail delivery from a client application to the server, and from an originating server
to the destination server, is handled by the <em class="firstterm">Simple
Mail Transfer Protocol</em> (<em
class="firstterm">SMTP</em>).
+ </div><div class="section"
id="s3-email-protocols-smtp"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-protocols-smtp">13.1.1.1. SMTP</h4></div></div></div><a
id="id441144" class="indexterm"></a><div
class="para">
+ The primary purpose of SMTP is to transfer email between mail servers. However, it
is critical for email clients as well. To send email, the client sends the message to an
outgoing mail server, which in turn contacts the destination mail server for delivery. For
this reason, it is necessary to specify an SMTP server when configuring an email client.
+ </div><div class="para">
+ Under Fedora, a user can configure an SMTP server on the local machine to handle
mail delivery. However, it is also possible to configure remote SMTP servers for outgoing
mail.
+ </div><div class="para">
+ One important point to make about the SMTP protocol is that it does not require
authentication. This allows anyone on the Internet to send email to anyone else or even to
large groups of people. It is this characteristic of SMTP that makes junk email or <em
class="firstterm">spam</em> possible. Imposing relay restrictions
limits random users on the Internet from sending email through your SMTP server, to other
servers on the internet. Servers that do not impose such restrictions are called <em
class="firstterm">open relay</em> servers.
+ </div><div class="para">
+ Fedora provides the Postfix and Sendmail SMTP programs.
+ </div></div></div><div class="section"
id="s2-email-protocols-client"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-protocols-client">13.1.2. Mail Access
Protocols</h3></div></div></div><div
class="para">
+ There are two primary protocols used by email client applications to retrieve email
from mail servers: the <em class="firstterm">Post Office
Protocol</em> (<em class="firstterm">POP</em>) and the <em
class="firstterm">Internet Message Access Protocol</em> (<em
class="firstterm">IMAP</em>).
+ </div><div class="section"
id="s3-email-protocols-pop"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-protocols-pop">13.1.2.1. POP</h4></div></div></div><a
id="id431242" class="indexterm"></a><div
class="para">
+ The default POP server under Fedora is <span
class="application"><strong>Dovecot</strong></span> and is
provided by the <span class="package">dovecot</span> package.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the dovecot
package</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>Dovecot</strong></span>, first
ensure the <code class="command">dovecot</code> package is installed
on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">yum install dovecot</code></pre><div
class="para">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ When using a <code class="systemitem">POP</code> server, email
messages are downloaded by email client applications. By default, most <code
class="systemitem">POP</code> email clients are automatically
configured to delete the message on the email server after it has been successfully
transferred, however this setting usually can be changed.
+ </div><div class="para">
+ <code class="systemitem">POP</code> is fully compatible with
important Internet messaging standards, such as <em
class="firstterm">Multipurpose Internet Mail Extensions</em> (<em
class="firstterm">MIME</em>), which allow for email attachments.
+ </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">
+ The most current version of the standard <code
class="systemitem">POP</code> protocol is <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> with Kerberos authentication.
+ </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">Section 13.5.1, “Securing
Communication”</a>.
+ </div></div><div class="section"
id="s3-email-protocols-imap"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-protocols-imap">13.1.2.2. IMAP</h4></div></div></div><a
id="id449334" class="indexterm"></a><div
class="para">
+ The default <code class="systemitem">IMAP</code> server under
Fedora is <span
class="application"><strong>Dovecot</strong></span> and is
provided by the <span class="package">dovecot</span> package. Refer
to <a class="xref"
href="ch-Mail_Servers.html#s3-email-protocols-pop">Section 13.1.2.1,
“POP”</a> for information on how to install <span
class="application"><strong>Dovecot</strong></span>.
+ </div><div class="para">
+ When using an <code class="systemitem">IMAP</code> mail
server, email messages remain on the server where users can read or delete them. <code
class="systemitem">IMAP</code> also allows client applications to
create, rename, or delete mail directories on the server to organize and store email.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code> is particularly useful
for users who access their email using multiple machines. The protocol is also convenient
for users connecting to the mail server via a slow connection, because only the email
header information is downloaded for messages until opened, saving bandwidth. The user
also has the ability to delete messages without viewing or downloading them.
+ </div><div class="para">
+ For convenience, <code class="systemitem">IMAP</code> client
applications are capable of caching copies of messages locally, so the user can browse
previously read messages when not directly connected to the <code
class="systemitem">IMAP</code> server.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code>, like <code
class="systemitem">POP</code>, is fully compatible with important
Internet messaging standards, such as MIME, which allow for email attachments.
+ </div><div class="para">
+ For added security, it is possible to use <code
class="systemitem">SSL</code> encryption for client authentication and
data transfer sessions. This can be enabled by using the <code
class="command">imaps</code> service, or by using the <code
class="command">/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">Section 13.5.1, “Securing
Communication”</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"
id="s3-mail-server-dovecot">13.1.2.3. Dovecot</h4></div></div></div><a
id="id437724" 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">
+ Make that change operational after the next reboot by running the command:
+ </div><pre class="screen"><code
class="command">systemctl enable
dovecot.service</code></pre><div class="note"><div
class="admonition_header"><h2>The dovecot service starts the POP3
server</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>Prev</strong>Chapter 12. Web
Servers</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-types.html"><strong>Next</strong>13.2. Email
Program Classifications</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Managing_Users_and_Groups.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Managing_Users_and_Groups.html
new file mode 100644
index 0000000..4717b4f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Managing_Users_and_Groups.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>Chapter 3. Managing Users and Groups</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Basic_System_Configuration.html" title="Part I. Basic System
Configuration" /><link rel="prev"
href="sect-Date_and_Time_Configuration-Additional_Resources.html"
title="2.3. Additional Resources" /><link rel="next"
href="s1-users-configui.html" title="3.2. User Manager 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="sect-Date_and_Time_Configuration-Additiona
l_Resources.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-configui.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Managing_Users_and_Groups" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 3. Managing Users and
Groups</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts">3.1.
User Accounts Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.1.1.
Configuring an Account</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">3.1.2.
Adding a New User</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_A
ccounts-Removing_a_User">3.1.3. Removing a
User</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-configui.html">3.2. User
Manager Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-configui.html#s2-redhat-config-users-user-new">3.2.1. Adding a
New User</a></span></dt><dt><span
class="section"><a
href="s2-redhat-config-users-group-new.html">3.2.2. Adding a New
Group</a></span></dt><dt><span
class="section"><a
href="s2-redhat-config-users-group-properties.html">3.2.3. Modifying Group
Properties</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-tools.html">3.3. User and
Group Management
Tools</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-tools.html#s2-users-cmd-line">3.3.1. Command Line
Configuration</a></span></dt><dt><span
class="section"><a
href="s2-redhat-config-users-process.html">3.3.2. Explaining the
Process</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-groups-standard
-users.html">3.4. Standard
Users</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-standard-groups.html">3.5. Standard
Groups</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-private-groups.html">3.6. User Private
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-groups-private-groups.html#s2-users-groups-rationale">3.6.1.
Group
Directories</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-users-groups-shadow-utilities.html">3.7. Shadow
Passwords</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-additional-resources.html">3.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">3.8.1.
Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id441488" class="indexterm"></a><a
id="id505804" class="indexterm"></a><a
id="id482511" class="indexterm"></a><a
id="id506490" class="indexterm"
</a><div class="para">
+ The control of
<em class="firstterm">users</em> and <em
class="firstterm">groups</em> is a core element of Fedora system
administration. Users can be either people (meaning accounts tied to physical users) or
accounts which exist for specific applications to use. Groups are logical expressions of
organization, tying users together for a common purpose. Users within a group can read,
write, or execute files owned by that group.
+ </div><div class="para">
+ Each user is associated with a unique numerical identification number called a <em
class="firstterm">userid</em> (<em
class="firstterm">UID</em>); likewise, each group is associated with a
<em class="firstterm">groupid</em> (<em
class="firstterm">GID</em>).
+ </div><div class="para">
+ A user who creates a file is also the owner and group owner of that file. The file is
assigned separate read, write, and execute permissions for the owner, the group, and
everyone else. The file owner can be changed only by the <code
class="systemitem">root</code> user, and access permissions can be
changed by both the <code class="systemitem">root</code> user and
file owner.
+ </div><div class="para">
+ Fedora also supports <em class="firstterm">access control
lists</em> (<em class="firstterm">ACLs</em>) for files and
directories which allow permissions for specific users outside of the owner to be set. For
more information about ACLs, refer to the <em class="citetitle">Access
Control Lists</em> chapter of the Fedora <em
class="citetitle">Storage Administration Guide</em>.
+ </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"
id="sect-Managing_Users_and_Groups-User_Accounts">3.1. User Accounts
Tool</h2></div></div></div><a id="id424578"
class="indexterm"></a><a id="id463408"
class="indexterm"></a><a id="id442771"
class="indexterm"></a><div class="para">
+ The <span class="application"><strong>User
Accounts</strong></span> configuration tool allows you to view, modify, add,
and delete local users. To run the utility, either select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Settings</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu and
click the <span class="guimenu"><strong>User
Accounts</strong></span> icon, or click your name on the panel and choose
<span class="guimenuitem"><strong>My
Account</strong></span> from the drop-down menu.
+ </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="The User Accounts configuration
tool" /><div class="longdesc"><div class="para">
+ The User Accounts configuration tool
+ </div></div></div></div><h6>Figure 3.1. The User
Accounts configuration tool</h6></div><br class="figure-break"
/><div class="para">
+ The main window of the <span class="application"><strong>User
Accounts</strong></span> configuration tool is divided into two parts: The
left side of the window contains a list of available user accounts. The right side
provides details on a particular account.
+ </div><div class="para">
+ By default, the tool only allows you to change certain settings regarding your
account. This is because only <code class="systemitem">root</code>
is allowed to configure users and groups. To unlock the configuration tool for all kinds
of changes, click the <span
class="guibutton"><strong>Unlock</strong></span> button in
the bottom-left corner of the window, and provide the root password when prompted.
+ </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"
id="sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.1.1. Configuring
an Account</h3></div></div></div><div
class="para">
+ To change the image associated with an account, click the icon next to the account
name and either select a picture from the drop-down list, or click <span
class="guimenuitem"><strong>Browse for more
pictures...</strong></span> to use an image from your local drive.
+ </div><div class="para">
+ To change the name associated with an account, click the name next to the icon to
edit it.
+ </div><div class="para">
+ To change the account type, use the <span
class="guimenu"><strong>Account type</strong></span>
drop-down list. However, this change requires the configuration tool to be unlocked even
if it is your account.
+ </div><div class="para">
+ To change the default language for an account, click the button next to the <span
class="guilabel"><strong>Language</strong></span> label,
and select the desired language from the list.
+ </div><div class="para">
+ To change the password, click the button next to the <span
class="guilabel"><strong>Password</strong></span> label. A
dialog box will appear, allowing you to set the new password. Note that the current
password must be provided in order to confirm the change. Once done, click the <span
class="guibutton"><strong>Change</strong></span> button to
save the change.
+ </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="Changing the
password" /><div class="longdesc"><div
class="para">
+ Changing the password
+ </div></div></div></div><h6>Figure 3.2. Changing the
password</h6></div><br class="figure-break" /><div
class="note"><div
class="admonition_header"><h2>Password security
advice</h2></div><div class="admonition"><div
class="para">
+ It is advisable to use a much longer password, as this makes it more difficult for
an intruder to guess it and access the account without permission. It is also recommended
that the password not be based on a dictionary term: use a combination of letters, numbers
and special characters.
+ </div></div></div><div class="para">
+ Finally, to set up automatic login for a particular account, enable the <span
class="guilabel"><strong>Automatic Login</strong></span>
switch. The configuration tool must be unlocked to make this change.
+ </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"
id="sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">3.1.2. Adding
a New User</h3></div></div></div><a id="id444250"
class="indexterm"></a><div class="para">
+ To add a new user, make sure the configuration tool is unlocked, and click the
<span class="guibutton"><strong>+</strong></span> button
(that is, the plus sign) below the account list. A dialog box as shown in <a
class="xref"
href="ch-Managing_Users_and_Groups.html#fig-Managing_Users_and_Groups-User_Accounts-Adding_an_Account">Figure 3.3,
“Creating a new account”</a> will appear.
+ </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="Creating a new account"
/><div class="longdesc"><div class="para">
+ Creating a new account
+ </div></div></div></div><h6>Figure 3.3. Creating a
new account</h6></div><br class="figure-break" /><div
class="para">
+ Take the followign steps to create an account:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Select an account type from the <span
class="guimenu"><strong>Account type</strong></span>
drop-down list. Available account types are <code
class="option">Administrator</code> and <code
class="option">Standard</code> (the default option).
+ </div></li><li class="step"><div
class="para">
+ Fill in the <span class="guilabel"><strong>Full
name</strong></span> input field to set the name associated with the account.
This name will be used by the login manager, and will be displayed on the panel.
+ </div></li><li class="step"><div
class="para">
+ Either select a suggested username from the <span
class="guilabel"><strong>Username</strong></span> drop-down
list, or fill in the corresponding input field.
+ </div></li><li class="step"><div
class="para">
+ Click the <span
class="guibutton"><strong>Create</strong></span> button to
confirm the settings.
+ </div></li></ol></div><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em>
(UPG) scheme. The UPG scheme does not add or change anything in the standard UNIX way of
handling groups; it offers a new convention. Whenever you create a new user, a unique
group with the same name as the user is created.
+ </div><div class="para">
+ When a new account is created, default configuration files are copied from the
<code class="filename">/etc/skel/</code> directory into the new home
directory.
+ </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"
id="sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.1.3. Removing
a User</h3></div></div></div><a id="id507916"
class="indexterm"></a><div class="para">
+ To remove a user, make sure the configuration tool is unlocked, select the desired
account from the account list, and click the <span
class="guibutton"><strong>−</strong></span> button (that
is, the minus sign) below the account list. A dialog box as shown in <a
class="xref"
href="ch-Managing_Users_and_Groups.html#fig-Managing_Users_and_Groups-User_Accounts-Removing_an_Account">Figure 3.4,
“Removing an account”</a> will appear.
+ </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="Removing an account"
/><div class="longdesc"><div class="para">
+ Removing an account
+ </div></div></div></div><h6>Figure 3.4. Removing an
account</h6></div><br class="figure-break" /><div
class="para">
+ To delete files and directories that belong to the user (that is, the home directory,
mail spool, and temporary files), click the <span
class="guibutton"><strong>Delete Files</strong></span>
button. To keep these files intact and only delete the user account, click <span
class="guibutton"><strong>Keep Files</strong></span>. To
abort the deletion, click <span
class="guibutton"><strong>Cancel</strong></span>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Date_and_Time_Configuration-Additional_Resources.html"><strong>Prev</strong>2.3. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-configui.html"><strong>Next</strong>3.2. User
Manager Tool</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.html
new file mode 100644
index 0000000..80ed14f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.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>Chapter 20. Manually Upgrading the Kernel</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="Part VII. Kernel, Module and Driver Configuration" /><link
rel="prev" href="part-Kernel_Module_and_Driver_Configuration.html"
title="Part VII. Kernel, Module and Driver Configuration" /><link
rel="next" href="s1-kernel-preparing.html" title="20.2. Preparing
to Upgrade" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-Kernel_Module_and_Driver_Configuration.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-preparing.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Manually_Upgrading_the_Kernel" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 20. Manually Upgrading the
Kernel</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">20.1.
Overview of Kernel Packages</a></span></dt><dt><span
class="section"><a href="s1-kernel-preparing.html">20.2.
Preparing to Upgrade</a></span></dt><dt><span
class="section"><a href="s1-kernel-download.html">20.3.
Downloading the Upgraded Kernel</a></span></dt><dt><span
class="section"><a
href="s1-kernel-perform-upgrade.html">20.4. Performing the
Upgrade</a></span></dt><dt><span
class="section"><a
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">20.5. Verifying the
Init
ial RAM Disk Image</a></span></dt><dt><span
class="section"><a href="s1-kernel-boot-loader.html">20.6.
Verifying the Boot
Loader</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">20.6.1.
Configuring the GRUB Boot Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-iseries.html">20.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-pseries.html">20.6.3. Configuring the YABOOT Boot
Loader</a></span></dt></dl></dd></dl></div><a
id="id598932" class="indexterm"></a><a
id="id624365" class="indexterm"></a><a
id="id541709" class="indexterm"></a><a
id="id421058" 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">
+ This chapter is therefore <span
class="emphasis"><em>only</em></span> useful for users who
need to manually update a kernel package using the <code
class="command">rpm</code> command instead of <code
class="command">yum</code>.
+ </div><a id="id482137" class="indexterm"></a><a
id="id574287" 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="id566934"
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">Section 4.1.2, “Updating
Packages”</a>.
+ </div><div class="section"
id="s1-kernel-packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kernel-packages">20.1. Overview of Kernel
Packages</h2></div></div></div><a id="id564507"
class="indexterm"></a><a id="id564519"
class="indexterm"></a><a id="id589554"
class="indexterm"></a><a id="id444552"
class="indexterm"></a><a id="id574732"
class="indexterm"></a><a id="id449798"
class="indexterm"></a><a id="id550028"
class="indexterm"></a><a id="id432615"
class="indexterm"></a><a id="id613229"
class="indexterm"></a><a id="id589514"
class="indexterm"></a><a id="id622362"
class="indexterm"></a><a id="id533825"
class="indexterm"></a><a id="id592569"
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>Prev</strong>Part VII. Kernel,
Module and Driver Configuration</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-preparing.html"><strong>Next</strong>20.2. Preparing
to Upgrade</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Network_Interfaces.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Network_Interfaces.html
new file mode 100644
index 0000000..e104428
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Network_Interfaces.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 6. Network Interfaces</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Networking.html" title="Part III. Networking" /><link
rel="prev" href="part-Networking.html"
title="Part III. Networking" /><link rel="next"
href="s1-networkscripts-interfaces.html" title="6.2. Interface
Configuration 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="part-Networking.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href=
"s1-networkscripts-interfaces.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-Network_Interfaces"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 6. Network
Interfaces</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Network_Interfaces.html#s1-networkscripts-files">6.1. Network
Configuration Files</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-interfaces.html">6.2. Interface Configuration
Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">6.2.1.
Ethernet Interfaces</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-chan.html">6.2.2. Channel Bonding
Interfaces</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-alias.html">6.2.3. Alias and Clone
Files</a></span></dt><dt><span
class="section"><a href="s2-networkscripts-interfac
es-ppp0.html">6.2.4. Dialup
Interfaces</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-other.html">6.2.5. Other
Interfaces</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-networkscripts-control.html">6.3.
Interface Control Scripts</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-static-routes.html">6.4. Configuring Static
Routes</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-functions.html">6.5. Network Function
Files</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-resources.html">6.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-networkscripts-resources.html#s2-networkscripts-docs-inst">6.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></div><a
id="id616983" class="indexterm"></a><a
id="id442482" class="indexterm"></a><div
class="para">
+ Under Fedora, all network communications occur between configured software <em
class="firstterm">interfaces</em> and <em
class="firstterm">physical networking devices</em> connected to the
system.
+ </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">Interface configuration files</em>
+ </div></li><li class="listitem"><div
class="para">
+ <em class="firstterm">Interface control scripts</em>
+ </div></li><li class="listitem"><div
class="para">
+ <em class="firstterm">Network function files</em>
+ </div></li></ol></div><div class="para">
+ The files in each of these categories work together to enable various network devices.
+ </div><div class="para">
+ This chapter explores the relationship between these files and how they are used.
+ </div><div class="section"
id="s1-networkscripts-files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-files">6.1. Network Configuration
Files</h2></div></div></div><a id="id528998"
class="indexterm"></a><div class="para">
+ Before delving into the interface configuration files, let us first itemize the
primary configuration files used in network configuration. Understanding the role these
files play in setting up the network stack can be helpful when customizing a Fedora
system.
+ </div><div class="para">
+ The primary network configuration files are as follows:
+ </div><div class="variablelist"><dl><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="command">127.0.0.1</code>) as <code
class="command">localhost.localdomain</code>. For more information,
refer to the <code class="filename">hosts</code> man 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 <code
class="filename">resolv.conf</code> man page.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="filename">/etc/sysconfig/network</code>
</span></dt><dd><div class="para">
+ 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">Section B.1.13, “
/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">
+ For each network interface, there is a corresponding interface configuration
script. Each of these files provide information specific to a particular network
interface. Refer to <a class="xref"
href="s1-networkscripts-interfaces.html">Section 6.2, “Interface
Configuration Files”</a> for more information on this type of file and the
directives it accepts.
+ </div></dd></dl></div><div
class="warning"><div
class="admonition_header"><h2>Warning</h2></div><div
class="admonition"><div class="para">
+ The <code class="filename">/etc/sysconfig/networking/</code>
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
<span class="bold bold"><strong>not</strong></span> be
edited manually. Using only one method for network configuration is strongly encouraged,
due to the risk of configuration deletion.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Networking.html"><strong>Prev</strong>Part III. Networking</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-networkscripts-interfaces.html"><strong>Next</strong>6.2. Interface
Configuration Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-OpenSSH.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-OpenSSH.html
new file mode 100644
index 0000000..6643361
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-OpenSSH.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>Chapter 9. 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Infrastructure_Services.html" title="Part IV. Infrastructure
Services" /><link rel="prev"
href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"
title="8.2.9. SSSD Configuration File Format" /><link rel="next"
href="s1-ssh-configuration.html" title="9.2. An OpenSSH 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="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-configuration.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-OpenSSH"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 9. OpenSSH</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-OpenSSH.html#s1-ssh-protocol">9.1. The SSH
Protocol</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-why">9.1.1.
Why Use SSH?</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-features">9.1.2. Main
Features</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-versions">9.1.3. Protocol
Versions</a></span></dt><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">9.1.4.
Event Sequence of an SSH
Connection</a></span></dt></dl></dd><dt><span
class="sectio
n"><a href="s1-ssh-configuration.html">9.2. An OpenSSH
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">9.2.1.
Configuration Files</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-sshd.html">9.2.2. Starting an OpenSSH
Server</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-requiring.html">9.2.3. Requiring SSH for Remote
Connections</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-keypairs.html">9.2.4. Using a Key-Based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-clients.html">9.3. OpenSSH
Clients</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-clients.html#s2-ssh-clients-ssh">9.3.1. Using the ssh
Utility</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-scp.html">9.3.2.
Using the <code class="command">scp</code>
Utility</a></span></dt><dt><span
class="section"><a
href="s2-ssh-clients-sftp.html">9.3.3. Using the <code
class="command">sftp</code>
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-beyondshell.html">9.4. More
Than a Secure
Shell</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">9.4.1. X11
Forwarding</a></span></dt><dt><span
class="section"><a
href="s2-ssh-beyondshell-tcpip.html">9.4.2. Port
Forwarding</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-openssh-additional-resources.html">9.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-openssh-additional-resources.html#s2-openssh-installed-docs">9.5.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-openssh-useful-websites.html">9.5.2. Useful
Websites</a></span></dt></dl></dd></dl></div><a
id="id430707" class="indexterm"></a><div
class="para">
+ <code class="systemitem">SSH</code> (Secure Shell) is a protocol
which facilitates secure communications between two systems using a client/server
architecture and allows users to log into server host systems remotely. Unlike other
remote communication protocols, such as <code
class="systemitem">FTP</code> or <code
class="systemitem">Telnet</code>, SSH encrypts the login session,
rendering the connection difficult for intruders to collect unencrypted passwords.
+ </div><div class="para">
+ The <span
class="application"><strong>ssh</strong></span> program is
designed to replace older, less secure terminal applications used to log into remote
hosts, such as <code class="command">telnet</code> or <code
class="command">rsh</code>. A related program called <code
class="command">scp</code> replaces older programs designed to copy
files between hosts, such as <code class="command">rcp</code>.
Because these older applications do not encrypt passwords transmitted between the client
and the server, avoid them whenever possible. Using secure methods to log into remote
systems decreases the risks for both the client system and the remote host.
+ </div><div class="para">
+ Fedora includes the general OpenSSH package (<span
class="package">openssh</span>) as well as the OpenSSH server (<span
class="package">openssh-server</span>) and client (<span
class="package">openssh-clients</span>) packages. Note that the OpenSSH
packages require the OpenSSL package (<span
class="package">openssl</span>), which installs several important
cryptographic libraries, enabling OpenSSH to provide encrypted communications.
+ </div><div class="section" id="s1-ssh-protocol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-ssh-protocol">9.1. The SSH
Protocol</h2></div></div></div><div class="section"
id="s2-ssh-why"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-why">9.1.1. Why Use
SSH?</h3></div></div></div><a id="id429007"
class="indexterm"></a><div class="para">
+ Potential intruders have a variety of tools at their disposal enabling them to
disrupt, intercept, and re-route network traffic in an effort to gain access to a system.
In general terms, these threats can be categorized as follows:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">Interception of
communication between two systems</span></dt><dd><div
class="para">
+ The attacker can be somewhere on the network between the communicating parties,
copying any information passed between them. He may intercept and keep the information, or
alter the information and send it on to the intended recipient.
+ </div><div class="para">
+ This attack is usually performed using a <em
class="firstterm">packet sniffer</em>, a rather common network utility
that captures each packet flowing through the network, and analyzes its content.
+ </div></dd><dt class="varlistentry"><span
class="term">Impersonation of a particular
host</span></dt><dd><div class="para">
+ Attacker's system is configured to pose as the intended recipient of a
transmission. If this strategy works, the user's system remains unaware that it is
communicating with the wrong host.
+ </div><div class="para">
+ This attack can be performed using a technique known as <em
class="firstterm">DNS poisoning</em>, or via so-called <em
class="firstterm">IP spoofing</em>. In the first case, the intruder
uses a cracked DNS server to point client systems to a maliciously duplicated host. In the
second case, the intruder sends falsified network packets that appear to be from a trusted
host.
+ </div></dd></dl></div><div class="para">
+ Both techniques intercept potentially sensitive information and, if the interception
is made for hostile reasons, the results can be disastrous. If SSH is used for remote
shell login and file copying, these security threats can be greatly diminished. This is
because the SSH client and server use digital signatures to verify their identity.
Additionally, all communication between the client and server systems is encrypted.
Attempts to spoof the identity of either side of a communication does not work, since each
packet is encrypted using a key known only by the local and remote systems.
+ </div></div><div class="section"
id="s2-ssh-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-features">9.1.2. Main
Features</h3></div></div></div><a id="id568397"
class="indexterm"></a><a id="id568409"
class="indexterm"></a><div class="para">
+ The SSH protocol provides the following safeguards:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">No one can pose as
the intended server</span></dt><dd><div class="para">
+ After an initial connection, the client can verify that it is connecting to the
same server it had connected to previously.
+ </div></dd><dt class="varlistentry"><span
class="term">No one can capture the authentication
information</span></dt><dd><div class="para">
+ The client transmits its authentication information to the server using strong,
128-bit encryption.
+ </div></dd><dt class="varlistentry"><span
class="term">No one can intercept the
communication</span></dt><dd><div class="para">
+ All data sent and received during a session is transferred using 128-bit
encryption, making intercepted transmissions extremely difficult to decrypt and read.
+ </div></dd></dl></div><div class="para">
+ Additionally, it also offers the following options:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">It provides secure
means to use graphical applications over a
network</span></dt><dd><div class="para">
+ Using a technique called <em class="firstterm">X11
forwarding</em>, the client can forward <em
class="firstterm">X11</em> (<em class="firstterm">X
Window System</em>) applications from the server.
+ </div></dd><dt class="varlistentry"><span
class="term">It provides a way to secure otherwise insecure
protocols</span></dt><dd><div class="para">
+ The SSH protocol encrypts everything it sends and receives. Using a technique
called <em class="firstterm">port forwarding</em>, an SSH server can
become a conduit to securing otherwise insecure protocols, like <acronym
class="acronym">POP</acronym>, and increasing overall system and data
security.
+ </div></dd><dt class="varlistentry"><span
class="term">It can be used to create a secure
channel</span></dt><dd><div class="para">
+ The OpenSSH server and client can be configured to create a tunnel similar to a
virtual private network for traffic between server and client machines.
+ </div></dd><dt class="varlistentry"><span
class="term">It supports the Kerberos
authentication</span></dt><dd><div class="para">
+ OpenSSH servers and clients can be configured to authenticate using the
<acronym class="acronym">GSSAPI</acronym> (Generic Security Services
Application Program Interface) implementation of the Kerberos network authentication
protocol.
+ </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"
id="s2-ssh-versions">9.1.3. Protocol
Versions</h3></div></div></div><a id="id425766"
class="indexterm"></a><a id="id425778"
class="indexterm"></a><div class="para">
+ Two varieties of SSH currently exist: version 1, and newer version 2. The OpenSSH
suite under Fedora uses SSH version 2, which has an enhanced key exchange algorithm not
vulnerable to the known exploit in version 1. However, for compatibility reasons, the
OpenSSH suite does support version 1 connections as well.
+ </div><div class="important"><div
class="admonition_header"><h2>Avoid using SSH version
1</h2></div><div class="admonition"><div
class="para">
+ To ensure maximum security for your connection, it is recommended that only SSH
version 2-compatible servers and clients are used whenever possible.
+ </div></div></div></div><div class="section"
id="s2-ssh-conn"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-conn">9.1.4. Event Sequence of an SSH
Connection</h3></div></div></div><a id="id464799"
class="indexterm"></a><div class="para">
+ The following series of events help protect the integrity of SSH communication
between two hosts.
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ A cryptographic handshake is made so that the client can verify that it is
communicating with the correct server.
+ </div></li><li class="listitem"><div
class="para">
+ The transport layer of the connection between the client and remote host is
encrypted using a symmetric cipher.
+ </div></li><li class="listitem"><div
class="para">
+ The client authenticates itself to the server.
+ </div></li><li class="listitem"><div
class="para">
+ The remote client interacts with the remote host over the encrypted connection.
+ </div></li></ol></div><div class="section"
id="s2-ssh-protocol-conn-transport"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s2-ssh-protocol-conn-transport">9.1.4.1. Transport
Layer</h4></div></div></div><a id="id621368"
class="indexterm"></a><div class="para">
+ The primary role of the transport layer is to facilitate safe and secure
communication between the two hosts at the time of authentication and during subsequent
communication. The transport layer accomplishes this by handling the encryption and
decryption of data, and by providing integrity protection of data packets as they are sent
and received. The transport layer also provides compression, speeding the transfer of
information.
+ </div><div class="para">
+ Once an SSH client contacts a server, key information is exchanged so that the two
systems can correctly construct the transport layer. The following steps occur during this
exchange:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Keys are exchanged
+ </div></li><li class="listitem"><div
class="para">
+ The public key encryption algorithm is determined
+ </div></li><li class="listitem"><div
class="para">
+ The symmetric encryption algorithm is determined
+ </div></li><li class="listitem"><div
class="para">
+ The message authentication algorithm is determined
+ </div></li><li class="listitem"><div
class="para">
+ The hash algorithm is determined
+ </div></li></ul></div><div class="para">
+ During the key exchange, the server identifies itself to the client with a unique
<em class="firstterm">host key</em>. If the client has never
communicated with this particular server before, the server's host key is unknown to
the client and it does not connect. OpenSSH gets around this problem by accepting the
server's host key. This is done after the user is notified and has both accepted and
verified the new host key. In subsequent connections, the server's host key is checked
against the saved version on the client, providing confidence that the client is indeed
communicating with the intended server. If, in the future, the host key no longer matches,
the user must remove the client's saved version before a connection can occur.
+ </div><div class="warning"><div
class="admonition_header"><h2>Always verify the integrity of a new SSH
server</h2></div><div class="admonition"><div
class="para">
+ It is possible for an attacker to masquerade as an SSH server during the initial
contact since the local system does not know the difference between the intended server
and a false one set up by an attacker. To help prevent this, verify the integrity of a new
SSH server by contacting the server administrator before connecting for the first time or
in the event of a host key mismatch.
+ </div></div></div><div class="para">
+ SSH is designed to work with almost any kind of public key algorithm or encoding
format. After an initial key exchange creates a hash value used for exchanges and a shared
secret value, the two systems immediately begin calculating new keys and algorithms to
protect authentication and future data sent over the connection.
+ </div><div class="para">
+ After a certain amount of data has been transmitted using a given key and algorithm
(the exact amount depends on the SSH implementation), another key exchange occurs,
generating another set of hash values and a new shared secret value. Even if an attacker
is able to determine the hash and shared secret value, this information is only useful for
a limited period of time.
+ </div></div><div class="section"
id="s2-ssh-protocol-authentication"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s2-ssh-protocol-authentication">9.1.4.2. Authentication</h4></div></div></div><a
id="id424849" class="indexterm"></a><div
class="para">
+ Once the transport layer has constructed a secure tunnel to pass information between
the two systems, the server tells the client the different authentication methods
supported, such as using a private key-encoded signature or typing a password. The client
then tries to authenticate itself to the server using one of these supported methods.
+ </div><div class="para">
+ SSH servers and clients can be configured to allow different types of
authentication, which gives each side the optimal amount of control. The server can decide
which encryption methods it supports based on its security model, and the client can
choose the order of authentication methods to attempt from the available options.
+ </div></div><div class="section"
id="s2-ssh-protocol-connection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s2-ssh-protocol-connection">9.1.4.3. Channels</h4></div></div></div><a
id="id424884" class="indexterm"></a><div
class="para">
+ After a successful authentication over the SSH transport layer, multiple channels
are opened via a technique called <em
class="firstterm">multiplexing</em><sup>[<a
id="id550431" href="#ftn.id550431"
class="footnote">2</a>]</sup>. Each of these channels handles
communication for different terminal sessions and for forwarded X11 sessions.
+ </div><div class="para">
+ Both clients and servers can create a new channel. Each channel is then assigned a
different number on each end of the connection. When the client attempts to open a new
channel, the clients sends the channel number along with the request. This information is
stored by the server and is used to direct communication to that channel. This is done so
that different types of sessions do not affect one another and so that when a given
session ends, its channel can be closed without disrupting the primary SSH connection.
+ </div><div class="para">
+ Channels also support <em class="firstterm">flow-control</em>,
which allows them to send and receive data in an orderly fashion. In this way, data is not
sent over the channel until the client receives a message that the channel is open.
+ </div><div class="para">
+ The client and server negotiate the characteristics of each channel automatically,
depending on the type of service the client requests and the way the user is connected to
the network. This allows great flexibility in handling different types of remote
connections without having to change the basic infrastructure of the protocol.
+ </div></div></div></div><div
class="footnotes"><br /><hr /><div
class="footnote"><div class="para"><sup>[<a
id="ftn.id550431" href="#id550431"
class="para">2</a>] </sup>
+ A multiplexed connection consists of several signals being sent over a shared,
common medium. With SSH, different channels are sent over a common secure connection.
+ </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>Prev</strong>8.2.9. SSSD
Configuration File Format</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-configuration.html"><strong>Next</strong>9.2. An
OpenSSH Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-PackageKit.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-PackageKit.html
new file mode 100644
index 0000000..13c2387
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-PackageKit.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>Chapter 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Package_Management.html" title="Part II. Package
Management" /><link rel="prev"
href="sec-Additional_Resources.html" title="4.5. Additional Resources"
/><link rel="next" href="sec-Using_Add_Remove_Software.html"
title="5.2. Using Add/Remove Software" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
c
lass="next"><a accesskey="n"
href="sec-Using_Add_Remove_Software.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-PackageKit"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 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.
Updating Packages with Software
Update</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-PackageKit.html#sec-Setting_preferences_for_checking_for_updates">5.1.1.
Setting the Update-Checking Interval</a></span></dt><dt><span
class="section"><a
href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">5.1.2.
Setting the Software
Sources</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Using_Add_Remove_Software.html">5.2. Using Add/Remove
Software</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Using_Add_Remove_Software.html#sec-Refresh
ing_Software_Sources_Yum_Repositories">5.2.1. Refreshing Software Sources (Yum
Repositories)</a></span></dt><dt><span
class="section"><a
href="sec-Finding_Packages_with_Filters.html">5.2.2. Finding Packages with
Filters</a></span></dt><dt><span
class="section"><a
href="sec-Installing_and_Removing_Packages_and_Dependencies.html">5.2.3.
Installing and Removing Packages (and
Dependencies)</a></span></dt><dt><span
class="section"><a
href="sec-Installing_and_Removing_Package_Groups.html">5.2.4. Installing and
Removing Package Groups</a></span></dt><dt><span
class="section"><a
href="sec-Viewing_the_Transaction_Log.html">5.2.5. Viewing the Transaction
Log</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-PackageKit_Architecture.html">5.3. PackageKit
Architecture</a></span></dt><dt><span
class="section"><a
href="ch-Graphical_Package_Management-sec-Additional_Resources.html">5.4.
Additional Resources</a></span></dt></dl></div><a
id="id480801" class="indexterm"></a><a id
="id478123" class="indexterm"></a><a
id="id420668" class="indexterm"></a><a
id="id444516" class="indexterm"></a><a
id="id448362" class="indexterm"></a><a
id="id506898" class="indexterm"></a><a
id="id449327" class="indexterm"></a><a
id="id627874" class="indexterm"></a><a
id="id599910" class="indexterm"></a><a
id="id601067" class="indexterm"></a><a
id="id465651" class="indexterm"></a><div
class="para">
+ Fedora provides <span
class="application"><strong>PackageKit</strong></span> for
viewing, managing, updating, installing and uninstalling packages compatible with your
system. <span
class="application"><strong>PackageKit</strong></span>
consists of several graphical interfaces that can be opened from the GNOME panel menu, or
from the Notification Area when <span
class="application"><strong>PackageKit</strong></span>
alerts you that updates are available. For more information on <span
class="application"><strong>PackageKit's</strong></span>
architecture and available front ends, refer to <a class="xref"
href="sec-PackageKit_Architecture.html">Section 5.3, “PackageKit
Architecture”</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"
id="sec-Updating_Packages_with_Software_Update">5.1. Updating Packages with
Software Update</h2></div></div></div><a
id="id427287" class="indexterm"></a><a
id="id427302" class="indexterm"></a><div
class="para">
+ You can open <span class="application"><strong>Software
Updates</strong></span> by clicking <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>Software Update</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
running the <code class="command">gpk-update-viewer</code> command
at the shell prompt. In the <span class="guilabel"><strong>Software
Updates</strong></span> window, all available updates are listed along with
the names of the packages being updated (minus the <code
class="filename">.rpm</code> suffix, but including the CPU
architecture), a short summary of the package, and, usually, short descriptions of the
changes the update provides. Any updates you do not wish to install can be de-selected
here by unchecking the checkbox corresponding to the update.
+ </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="Installing updates with Software
Update" /><div class="longdesc"><div
class="para">
+ installing 56 updates with PackageKit's software update window
+ </div></div></div></div><h6>Figure 5.1. Installing
updates with Software Update</h6></div><br class="figure-break"
/><div class="para">
+ The updates presented in the <span
class="guilabel"><strong>Software Updates</strong></span>
window only represent the currently-installed packages on your system for which updates
are available;
+ <a id="id480925" class="indexterm"></a>
+ <a id="id480940" class="indexterm"></a>
+ dependencies of those packages, whether they are existing packages on your system or
new ones, are not shown until you click <span
class="guibutton"><strong>Install Updates</strong></span>.
+ </div><div class="para">
+ <span
class="application"><strong>PackageKit</strong></span>
<a id="id480965" class="indexterm"></a>
+ <a id="id422104" class="indexterm"></a>
+ <a id="id422116" class="indexterm"></a>
+ utilizes the fine-grained user authentication
+ <a id="id422124" class="indexterm"></a>
+ capabilities provided by the <span
class="application"><strong>PolicyKit</strong></span>
toolkit whenever you request it to make changes to the system. Whenever you instruct
<span
class="application"><strong>PackageKit</strong></span> to
update, install or remove packages, you will be prompted to enter the superuser password
before changes are made to the system.
+ </div><div class="para">
+ If you instruct <span
class="application"><strong>PackageKit</strong></span> to
update the <code class="filename">kernel</code> package, then it
will prompt you after installation, asking you whether you want to reboot the system and
thereby boot into the newly-installed kernel.
+ </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"
id="sec-Setting_preferences_for_checking_for_updates">5.1.1. Setting the
Update-Checking Interval</h3></div></div></div><a
id="id539838" class="indexterm"></a><div
class="para">
+ Selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>Other</strong></span> →
<span class="guimenuitem"><strong>Software
Updates</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu
opens the <span class="guilabel"><strong>Software Update
Preferences</strong></span> window. The <span
class="guilabel"><strong>Update Settings</strong></span>
tab allows you to define the interval at which <span
class="application"><strong>PackageKit</strong></span>
checks for package updates, as well as whether or not to automatically install all updates
or only security updates. Leaving the <span
class="guilabel"><strong>Check for updates when using mobile
broadband</strong></span> box unchecked is handy for avoiding extraneous
bandwidth usage when using a wireless connection on which you are charged for the amount
of data you download.
+ </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="Setting PackageKit's
update-checking interval" /><div class="longdesc"><div
class="para">
+ Setting the update-checking interval for PackageKit
+ </div></div></div></div><h6>Figure 5.2. Setting
PackageKit's update-checking interval</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"
id="sec-Setting_preferences_for_software_sources">5.1.2. Setting the Software
Sources</h3></div></div></div><div class="para">
+ To select which package repositories to use to install software updates, select
<span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>Other</strong></span> →
<span class="guimenuitem"><strong>Software
Updates</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu,
and click the <span class="guilabel"><strong>Software
Sources</strong></span> tab of the <span
class="guilabel"><strong>Software Update
Preferences</strong></span> window.
+ </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="Setting
PackageKit's software sources" /><div class="longdesc"><div
class="para">
+ Setting the software sources for PackageKit
+ </div></div></div></div><h6>Figure 5.3. Setting
PackageKit's software sources</h6></div><br
class="figure-break" /><a id="id505026"
class="indexterm"></a><a id="id505038"
class="indexterm"></a><div class="para">
+ <span
class="application"><strong>PackageKit</strong></span>
refers to <span
class="application"><strong>Yum</strong></span>
repositories as software sources. It obtains all packages from enabled software
sources.The <span class="guilabel"><strong>Software
Sources</strong></span> tab shows the repository name, as written on the
<code class="computeroutput">name=<em
class="replaceable"><code>My Repository
Name</code></em></code> field of all [<em
class="replaceable"><code>repository</code></em>] sections
in the <code class="filename">/etc/yum.conf</code> configuration
file, and in all <code class="filename"><em
class="replaceable"><code>repository</code></em>.repo</code>
files in the <code class="filename">/etc/yum.repos.d/</code>
directory.
+ </div><div class="para">
+ Entries which are checked in the <span
class="guilabel"><strong>Enabled</strong></span> column
indicate that the corresponding repository will be used to locate packages to satisfy all
update and installation requests (including dependency resolution). The <span
class="guilabel"><strong>Enabled</strong></span> column
corresponds to the <code class="computeroutput">enabled=<em
class="replaceable"><code><1 or
0></code></em></code> field in [<em
class="replaceable"><code>repository</code></em>] sections.
Checking an unchecked box enables the Yum repository, and unchecking it disables it.
Performing either function causes <span
class="application"><strong>PolicyKit</strong></span> to
prompt for superuser authentication to enable or disable the repository. <span
class="application"><strong>PackageKit</strong></span>
actually inserts the <code class="literal">enabled=<em
class="replaceable"><code><1 or
0></code></em></code> line into the correct [<em
class="replace
able"><code>repository</code></em>] section if it does not
exist, or changes the value if it does. This means that enabling or disabling a repository
through the <span class="guilabel"><strong>Software
Sources</strong></span> window causes that change to persist after closing the
window or rebooting the system. The ability to quickly enable and disable repositories
based on our needs is a highly-convenient feature of <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Note that it is not possible to add or remove <span
class="application"><strong>Yum</strong></span>
repositories through <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="note"
id="note-Showing_Source_RPM_and_Test_Repositories"><div
class="admonition_header"><h2>Showing source RPM, test, and debuginfo
repositories</h2></div><div class="admonition"><div
class="para">
+ Checking the box at the bottom of the <span
class="guilabel"><strong>Software Sources</strong></span>
tab causes <span
class="application"><strong>PackageKit</strong></span> to
display source RPM, testing and debuginfo repositories as well. This box is unchecked by
default.
+ </div></div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Additional_Resources.html"><strong>Prev</strong>4.5. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_Add_Remove_Software.html"><strong>Next</strong>5.2. Using
Add/Remove Software</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-RPM.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-RPM.html
new file mode 100644
index 0000000..dbfdc47
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-RPM.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>Appendix A. RPM</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="s2-kdump-resources-online.html"
title="22.3.2. Useful Websites" /><link rel="next"
href="s1-rpm-using.html" title="A.2. Using 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="s2-kdump-resources-online.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-rpm-using.html"><strong>Ne
xt</strong></a></li></ul><div xml:lang="en-US"
class="appendix" id="ch-RPM" lang="en-US"><div
class="titlepage"><div><div><h1
class="title">RPM</h1></div></div></div><a
id="id643713" class="indexterm"></a><a
id="id643706" class="indexterm"></a><div
class="para">
+ The <em class="firstterm">RPM Package Manager</em> (RPM) is an
open packaging system
+ <a id="id643693" 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 15. 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="id610173" 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">Chapter 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">Chapter 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="id669454" 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"
id="s1-rpm-design">A.1. RPM Design
Goals</h2></div></div></div><a id="id675555"
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><dt
class="varlistentry"><span class="term">Upgradability
+ <a id="id675533" 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="id568829" 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="id462917" 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="id425499" 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="s2-kdump-resources-online.html"><strong>Prev</strong>22.3.2. Useful
Websites</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-rpm-using.html"><strong>Next</strong>A.2. Using
RPM</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Services_and_Daemons.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Services_and_Daemons.html
new file mode 100644
index 0000000..3c4052e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Services_and_Daemons.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>Chapter 7. Services and Daemons</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Infrastructure_Services.html" title="Part IV. Infrastructure
Services" /><link rel="prev"
href="part-Infrastructure_Services.html" title="Part IV. Infrastructure
Services" /><link rel="next"
href="s1-services-running.html" title="7.2. Running Services"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></l
i><li class="next"><a accesskey="n"
href="s1-services-running.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Services_and_Daemons" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 7. Services and
Daemons</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Services_and_Daemons.html#s1-services-configuring">7.1. Configuring
Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">7.1.1.
Enabling the Service</a></span></dt><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">7.1.2.
Disabling the
Service</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-services-running.html">7.2.
Running Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-running.html#s3-services-running-checking">7.2.1. Checking
the Service Status</a></span><
/dt><dt><span class="section"><a
href="s3-services-running-running.html">7.2.2. Running the
Service</a></span></dt><dt><span
class="section"><a
href="s3-services-running-stopping.html">7.2.3. Stopping the
Service</a></span></dt><dt><span
class="section"><a
href="s3-services-running-restarting.html">7.2.4. Restarting the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-services-additional-resources.html">7.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-additional-resources.html#s2-services-additional-resources-installed">7.3.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-services-additional-resources-books.html">7.3.2. Related
Books</a></span></dt></dl></dd></dl></div><a
id="id463444" class="indexterm"></a><div
class="para">
+ Maintaining security on your system is extremely important, and one approach for this
task is to manage access to system services carefully. Your system may need to provide
open access to particular services (for example, <code
class="systemitem">httpd</code> if you are running a web server).
However, if you do not need to provide a service, you should turn it off to minimize your
exposure to possible bug exploits.
+ </div><div class="para">
+ This chapter 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 <span
class="application"><strong>systemctl</strong></span>
utility.
+ </div><div class="important"><div
class="admonition_header"><h2>Keep the system
secure</h2></div><div class="admonition"><div
class="para">
+ When you allow access for new services, always remember that both the firewall and
<span
class="application"><strong>SELinux</strong></span> need to
be configured as well. One of the most common mistakes committed when configuring a new
service is neglecting to implement the necessary firewall configuration and SELinux
policies to allow access for it. Refer to the Fedora <em
class="citetitle">Security Guide</em> (see <a class="xref"
href="s1-services-additional-resources.html">Section 7.3, “Additional
Resources”</a>) for more information.
+ </div></div></div><div class="section"
id="s1-services-configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-services-configuring">7.1. Configuring
Services</h2></div></div></div><a id="id464895"
class="indexterm"></a><a id="id543338"
class="indexterm"></a><div class="para">
+ To allow you to configure which services are started at boot time, Fedora is shipped
with the <span
class="application"><strong>systemctl</strong></span>
command line tool.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not use the ntsysv and chkconfig
utilities</h2></div><div class="admonition"><div
class="para">
+ Although it is still possible to use the <span
class="application"><strong>ntsysv</strong></span> and
<span
class="application"><strong>chkconfig</strong></span>
utilities to manage services that have init scripts installed in the <code
class="filename">/etc/rc.d/init.d/</code> directory, it is advised that
you use the <span
class="application"><strong>systemctl</strong></span>
utility.
+ </div></div></div><div class="important"><div
class="admonition_header"><h2>Enabling the irqbalance
service</h2></div><div class="admonition"><div
class="para">
+ To ensure optimal performance on POWER architecture, it is recommended that the
<code class="systemitem">irqbalance</code> service is enabled. In
most cases, this service is installed and configured to run during the Fedora 15
installation. To verify that <code
class="systemitem">irqbalance</code> is running, type the following at
a shell prompt:
+ </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"
id="s3-services-configuration-enabling">7.1.1. Enabling the
Service</h3></div></div></div><div class="para">
+ To configure a service to be automatically started at boot time, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to enable the <code
class="systemitem">httpd</code> service, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl enable
httpd.service</code></pre><div class="para">
+ The service will be started the next time you boot the system. If you need to start
the service immediately, use the <code
class="command">systemctl</code> command as described in <a
class="xref" href="s3-services-running-running.html">Section 7.2.2,
“Running the Service”</a>.
+ </div></div><div class="section"
id="s3-services-configuration-disabling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s3-services-configuration-disabling">7.1.2. Disabling the
Service</h3></div></div></div><div class="para">
+ To disable starting a service at boot time, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to disable the <code
class="systemitem">httpd</code> service, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl disable
httpd.service</code></pre><div class="para">
+ The next time you boot the system, the service will <span
class="emphasis"><em>not</em></span> be started. If you
need to stop the service immediately, use the <code
class="command">systemctl</code> command as described in <a
class="xref"
href="s3-services-running-stopping.html">Section 7.2.3, “Stopping the
Service”</a>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Infrastructure_Services.html"><strong>Prev</strong>Part IV. Infrastructure
Services</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-services-running.html"><strong>Next</strong>7.2. Running
Services</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-System_Monitoring_Tools.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-System_Monitoring_Tools.html
new file mode 100644
index 0000000..b18b89d
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-System_Monitoring_Tools.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>Chapter 16. System Monitoring Tools</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Monitoring_and_Automation.html" title="Part VI. Monitoring and
Automation" /><link rel="prev"
href="part-Monitoring_and_Automation.html" title="Part VI. Monitoring and
Automation" /><link rel="next"
href="s1-sysinfo-memory-usage.html" title="16.2. 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_Automation.html"><strong>Prev</str
ong></a></li><li class="next"><a
accesskey="n"
href="s1-sysinfo-memory-usage.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-System_Monitoring_Tools" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 16. System Monitoring
Tools</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">16.1.
System Processes</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-memory-usage.html">16.2.
Memory Usage</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-filesystems.html">16.3.
File Systems</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-hardware.html">16.4.
Hardware</a></span></dt><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html">16.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.5.1.
Inst
alled
Documentation</a></span></dt></dl></dd></dl></div><a
id="id448176" class="indexterm"></a><a
id="id549552" class="indexterm"></a><div
class="para">
+ Before you learn how to configure your system, you should learn how to gather essential
system information. For example, you should know how to find the amount of free memory,
the amount of available hard drive space, how your hard drive is partitioned, and what
processes are running. This chapter discusses how to retrieve this type of information
from your Fedora system using simple commands and a few simple programs.
+ </div><div class="section"
id="s1-sysinfo-system-processes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysinfo-system-processes">16.1. System
Processes</h2></div></div></div><a id="id640512"
class="indexterm"></a><a id="id509278"
class="indexterm"></a><a id="id607810"
class="indexterm"></a><div class="para">
+ The <code class="command">ps ax</code> command displays a list
of current system processes, including processes owned by other users. To display the
owner alongside each process, use the <code class="command">ps
aux</code> command. This list is a static list; in other words, it is a snapshot of
what was running when you invoked the command. If you want a constantly updated list of
running processes, use <code class="command">top</code> as described
below.
+ </div><div class="para">
+ The <code class="command">ps</code> output can be long. To
prevent it from scrolling off the screen, you can pipe it through less:
+ </div><pre class="screen"><code
class="command">ps aux | less</code></pre><div
class="para">
+ You can use the <code class="command">ps</code> command in
combination with the <code class="command">grep</code> command to
see if a process is running. For example, to determine if <span
class="application"><strong>Emacs</strong></span> is
running, use the following command:
+ </div><pre class="screen"><code
class="command">ps ax | grep emacs</code></pre><a
id="id425195" class="indexterm"></a><a
id="id479490" class="indexterm"></a><div
class="para">
+ The <code class="command">top</code> command displays currently
running processes and important information about them including their memory and CPU
usage. The list is both real-time and interactive. An example of output from the <code
class="command">top</code> command is provided as follows:
+ </div><pre class="screen">top - 18:11:48 up 1 min, 1 user, load
average: 0.68, 0.30, 0.11
+Tasks: 122 total, 1 running, 121 sleeping, 0 stopped, 0 zombie
+Cpu(s): 0.0%us, 0.5%sy, 0.0%ni, 93.4%id, 5.7%wa, 0.2%hi, 0.2%si, 0.0
+Mem: 501924k total, 376496k used, 125428k free, 29664k buffers
+Swap: 1015800k total, 0k used, 1015800k free, 189008k cached
+
+ PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+ 1601 root 40 0 20172 1084 920 S 0.3 0.2 0:00.08 hald-addon-sto
+ 1998 silas 40 0 14984 1160 880 R 0.3 0.2 0:00.13 top
+ 1 root 40 0 19160 1412 1156 S 0.0 0.3 0:00.96 init
+ 2 root 40 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
+ 3 root RT 0 0 0 0 S 0.0 0.0 0:00.05 migration/0
+ 4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
+ 5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
+ 6 root RT 0 0 0 0 S 0.0 0.0 0:00.04 migration/1
+ 7 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
+ 8 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
+ 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0
+ 10 root 20 0 0 0 0 S 0.0 0.0 0:00.01 events/1
+ 11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuset
+ 12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre><div class="para">
+ To exit <code class="command">top</code>, press the <span
class="keycap"><strong>q</strong></span> key.
+ </div><div class="para">
+ <a class="xref"
href="ch-System_Monitoring_Tools.html#interactive-top-command">Table 16.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 <code class="command">top</code>(1) manual page.
+ </div><div class="table"
id="interactive-top-command"><h6>Table 16.1. Interactive top
commands</h6><div class="table-contents"><table
summary="Interactive top commands"
border="1"><colgroup><col class="command"
width="50%" /><col class="description" width="50%"
/></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span
class="keycap"><strong>Space</strong></span>
+ </td><td>
+ Immediately refresh the display
+ </td></tr><tr><td>
+ <span class="keycap"><strong>h</strong></span>
+ </td><td>
+ Display a help screen
+ </td></tr><tr><td>
+ <span class="keycap"><strong>k</strong></span>
+ </td><td>
+ Kill a process. You are prompted for the process ID and the signal to send to it.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>n</strong></span>
+ </td><td>
+ Change the number of processes displayed. You are prompted to enter the number.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>u</strong></span>
+ </td><td>
+ Sort by user.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>M</strong></span>
+ </td><td>
+ Sort by memory usage.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>P</strong></span>
+ </td><td>
+ Sort by CPU usage.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="id421923"
class="indexterm"></a><a id="id448189"
class="indexterm"></a><div class="para">
+ If you prefer a graphical interface for <code
class="command">top</code>, you can use the <span
class="application"><strong>GNOME System
Monitor</strong></span>. To start it from the desktop, 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
execute <code class="command">gnome-system-monitor</code> at a shell
prompt. Select the <span
class="guilabel"><strong>Processes</strong></span> tab.
+ </div><div class="para">
+ The <span class="application"><strong>GNOME System
Monitor</strong></span> allows you to search for a process in the list of
running processes. Using the <span class="application"><strong>GNOME
System Monitor</strong></span>, you can also view all processes, your
processes, or active processes.
+ </div><div class="para">
+ The <span
class="guimenuitem"><strong>Edit</strong></span> menu item
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 or start a process.
+ </div></li><li class="listitem"><div
class="para">
+ End a processes.
+ </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.
+ </div></li><li class="listitem"><div
class="para">
+ Edit the System Monitor preferences. These include changing the interval seconds to
refresh the list and selecting process fields to display in the System Monitor window.
+ </div></li></ul></div><div class="para">
+ The <span
class="guimenuitem"><strong>View</strong></span> menu item
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 my 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 the selected process.
+ </div></li><li class="listitem"><div
class="para">
+ Refresh the list of processes.
+ </div></li></ul></div><div class="para">
+ To stop a process, select it and click <span
class="guibutton"><strong>End Process</strong></span>.
Alternatively you can also stop a process by selecting it, clicking <span
class="guimenuitem"><strong>Edit</strong></span> on your
menu and selecting <span class="guimenuitem"><strong>Stop
Process</strong></span>.
+ </div><div class="para">
+ To sort the information by a specific column, click on the name of the column. This
sorts the information by the selected column in ascending order. Click on the name of the
column again to toggle the sort between ascending and descending order.
+ </div><div class="figure"
id="fig-sysinfo-processes"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-processes.png" alt="GNOME System Monitor —
Processes tab" /><div class="longdesc"><div
class="para">
+ Processes tab of the GNOME System Monitor
+ </div></div></div></div><h6>Figure 16.1. GNOME System
Monitor — Processes tab </h6></div><br class="figure-break"
/></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="part-Monitoring_and_Automation.html"><strong>Prev</strong>Part VI. Monitoring
and Automation</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-memory-usage.html"><strong>Next</strong>16.2. Memory
Usage</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-The_sysconfig_Directory.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-The_sysconfig_Directory.html
new file mode 100644
index 0000000..37c67c7
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-The_sysconfig_Directory.html
@@ -0,0 +1,336 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Appendix B. The 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="s2-rpm-related-books.html" title="A.5.3. Related
Books" /><link rel="next"
href="s1-sysconfig-etcsysconf-dir.html" title="B.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-rpm-related-books.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n
"
href="s1-sysconfig-etcsysconf-dir.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="appendix"
id="ch-The_sysconfig_Directory" lang="en-US"><div
class="titlepage"><div><div><h1 class="title">The
sysconfig Directory</h1></div></div></div><a
id="id541984" class="indexterm"></a><a
id="id480225" 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">
+ The actual content of your <code
class="filename">/etc/sysconfig/</code> directory depends on the
programs you have installed on your machine. To find the name of the package the
configuration file belongs to, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">yum provides /etc/sysconfig/<em
class="replaceable"><code>filename</code></em>
</code>
+</pre><div class="para">
+ Refer to <a class="xref"
href="sec-Installing.html">Section 4.2.4, “Installing Packages”</a> for
more information on how to install new packages in Fedora.
+ </div></div></div><div class="section"
id="s1-sysconfig-files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysconfig-files">B.1. Files in the /etc/sysconfig/
Directory</h2></div></div></div><a id="id528671"
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"
id="s2-sysconfig-arpwatch">B.1.1. /etc/sysconfig/arpwatch
</h3></div></div></div><a id="id508155"
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><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"
id="s2-sysconfig-authconfig">B.1.2. /etc/sysconfig/authconfig
</h3></div></div></div><a id="id551881"
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><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">Chapter 8, <em>Configuring
Authentication</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"
id="s2-sysconfig-autofs">B.1.3. /etc/sysconfig/autofs
</h3></div></div></div><a id="id550914"
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><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/"...
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"
id="s2-sysconfig-clock">B.1.4. /etc/sysconfig/clock
</h3></div></div></div><a id="id623413"
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><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-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Section 2.1,
“Date and Time Configuration Tool”</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"
id="s2-sysconfig-dhcpd">B.1.5. /etc/sysconfig/dhcpd
</h3></div></div></div><a id="id464544"
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><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">Chapter 10, <em>DHCP
Servers</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"
id="s2-sysconfig-firewall">B.1.6. /etc/sysconfig/firstboot
</h3></div></div></div><a id="id541097"
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><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"
id="s2-sysconfig-i18n">B.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><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"
id="s2-sysconfig-init">B.1.8. /etc/sysconfig/init
</h3></div></div></div><a id="id423815"
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><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"
id="s2-sysconfig-ip6tables">B.1.9. /etc/sysconfig/ip6tables-config
</h3></div></div></div><a id="id568202"
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><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"
id="s2-sysconfig-kybd">B.1.10. /etc/sysconfig/keyboard
</h3></div></div></div><a id="id440544"
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><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"
id="s2-sysconfig-ldap">B.1.11. /etc/sysconfig/ldap
</h3></div></div></div><a id="id668332"
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><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">Section 14.1,
“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"
id="s2-sysconfig-named">B.1.12. /etc/sysconfig/named
</h3></div></div></div><a id="id600227"
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><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">Section 11.2,
“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"
id="s2-sysconfig-network">B.1.13. /etc/sysconfig/network
</h3></div></div></div><a id="id472104"
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><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"
id="s2-sysconfig-ntpd">B.1.14. /etc/sysconfig/ntpd
</h3></div></div></div><a id="id608308"
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><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-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Section 2.2.2,
“Configuring the 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"
id="s2-sysconfig-quagga">B.1.15. /etc/sysconfig/quagga
</h3></div></div></div><a id="id671009"
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><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"
id="s2-sysconfig-radvd">B.1.16. /etc/sysconfig/radvd
</h3></div></div></div><a id="id503860"
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><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"
id="s2-sysconfig-samba">B.1.17. /etc/sysconfig/samba
</h3></div></div></div><a id="id467612"
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><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">Section 15.1,
“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"
id="s2-sysconfig-selinux">B.1.18. /etc/sysconfig/selinux
</h3></div></div></div><a id="id479139"
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><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"
id="s2-sysconfig-sendmail">B.1.19. /etc/sysconfig/sendmail
</h3></div></div></div><a id="id570229"
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><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">Section 13.3.2, “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"
id="s2-sysconfig-spamd">B.1.20. /etc/sysconfig/spamassassin
</h3></div></div></div><a id="id468249"
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><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">Section 13.4.2.6,
“Spam Filters”</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"
id="s2-sysconfig-squid">B.1.21. /etc/sysconfig/squid
</h3></div></div></div><a id="id597878"
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><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"
id="s2-sysconfig-rcu">B.1.22. /etc/sysconfig/system-config-users
</h3></div></div></div><a id="id475733"
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><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">Section 3.2, “User Manager Tool”</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"
id="s2-sysconfig-vncservers">B.1.23. /etc/sysconfig/vncservers
</h3></div></div></div><a id="id630068"
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><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"
id="s2-sysconfig-xinetd">B.1.24. /etc/sysconfig/xinetd
</h3></div></div></div><a id="id551339"
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><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">Chapter 7, <em>Services and
Daemons</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-rpm-related-books.html"><strong>Prev</strong>A.5.3. Related
Books</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysconfig-etcsysconf-dir.html"><strong>Next</strong>B.2. Directories
in the /etc/sysconfig/
Directory</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Viewing_and_Managing_Log_Files.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Viewing_and_Managing_Log_Files.html
new file mode 100644
index 0000000..0e54bed
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Viewing_and_Managing_Log_Files.html
@@ -0,0 +1,311 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 17. Viewing and Managing Log 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Monitoring_and_Automation.html" title="Part VI. Monitoring and
Automation" /><link rel="prev"
href="s1-sysinfo-additional-resources.html" title="16.5. Additional
Resources" /><link rel="next"
href="s1-logfiles-locating.html" title="17.2. Locating Log 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="s1-sysinfo-additional-resources.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n"
href="s1-logfiles-locating.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Viewing_and_Managing_Log_Files" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 17. Viewing and Managing Log
Files</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s1-configuring-rsyslog">17.1.
Configuring
rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-global-directives">17.1.1.
Global Directives</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-modules">17.1.2.
Modules</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-rules">17.1.3.
Rules</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-rsyslog-cmd-options">17.1.4.
<span class="application"><st
rong>rsyslog</strong></span> Command Line
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-logfiles-locating.html">17.2.
Locating Log Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-logfiles-locating.html#configuring-logrotate">17.2.1. Configuring
logrotate</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-logfiles-viewing.html">17.3.
Viewing Log Files</a></span></dt><dt><span
class="section"><a href="s1-logfiles-adding.html">17.4.
Adding a Log File</a></span></dt><dt><span
class="section"><a href="s1-logfiles-examining.html">17.5.
Monitoring Log Files</a></span></dt><dt><span
class="section"><a
href="s1-log-files-additional-resources.html">17.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-log-files-additional-resources.html#s2-log-files-installed-docs">17.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-log-files-useful-websites.html">17.6.2. Us
eful
Websites</a></span></dt></dl></dd></dl></div><a
id="id425011" class="indexterm"></a><a
id="id599111" class="indexterm"></a><div
class="para">
+ <em class="firstterm">Log files</em> are files that contain
messages about the system, including the kernel, services, and applications running on it.
There are different log files for different information. For example, there is a default
system log file, a log file just for security messages, and a log file for cron tasks.
+ </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="id606435" class="indexterm"></a><a
id="id448963" 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"
id="s1-configuring-rsyslog">17.1. Configuring
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"
id="s2-global-directives">17.1.1. Global
Directives</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"
id="s2-modules">17.1.2. Modules</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">Section 17.1.3.3,
“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/">...
+ </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"
id="s2-rules">17.1.3. Rules</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">Section 17.1.3.1,
“Filter Conditions”</a> and for information on actions, refer to <a
class="xref"
href="ch-Viewing_and_Managing_Log_Files.html#s3-actions">Section 17.1.3.2,
“Actions”</a>.
+ </div><div class="section"
id="s3-filter-conditions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-filter-conditions">17.1.3.1. Filter
Conditions</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><dt
class="varlistentry"><span
class="term">Facility/Priority-based
filters</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">
+ The following are a few examples of simple facility/priority-based filters:
+ </div><pre class="screen">
+kern.* # Selects all kernel syslog messages with any priority
+</pre><pre class="screen">
+mail.crit # Selects all mail syslog messages with priority <code
class="command">crit</code> and higher.
+</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">Property-based filters</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">Section 17.1.3.3.2,
“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">Table 17.1,
“Property-based compare-operations”</a>.
+ </div><div class="table"
id="table-compare-operations"><h6>Table 17.1. Property-based
compare-operations</h6><div class="table-contents"><table
summary="Property-based compare-operations"
border="1"><colgroup><col width="38%"
class="operation" /><col width="63%"
class="description" /></colgroup><thead><tr><th>
+ Compare-operation
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <em
class="parameter"><code>contains</code></em>
+ </td><td>
+ Checks whether the provided string matches any part of the text provided by
the property.
+ </td></tr><tr><td>
+ <em
class="parameter"><code>isequal</code></em>
+ </td><td>
+ Compares the provided string against all of the text provided by the
property.
+ </td></tr><tr><td>
+ <em
class="parameter"><code>startswith</code></em>
+ </td><td>
+ Checks whether the provided string matches a prefix of the text provided by
the property.
+ </td></tr><tr><td>
+ <em
class="parameter"><code>regex</code></em>
+ </td><td>
+ Compares the provided POSIX BRE (Basic Regular Expression) regular expression
against the text provided by the property.
+ </td></tr><tr><td>
+ <em
class="parameter"><code>ereregex</code></em>
+ </td><td>
+ Compares the provided POSIX ERE (Extended Regular Expression) regular
expression against the text provided by the property.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ To define a property-based filter, use the following syntax:
+ </div><pre class="screen">:<em
class="replaceable"><code><PROPERTY></code></em>,
[!]<em
class="replaceable"><code><COMPARE_OPERATION></code></em>,
"<em
class="replaceable"><code><STRING></code></em>"</pre><div
class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="replaceable"><code><PROPERTY></code></em>
attribute specifies the desired property (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">Table 17.1,
“Property-based compare-operations”</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">
+ The following are few examples of property-based filters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The following filter selects syslog messages which contain the string <code
class="literal">error</code> in their message text:
+ </div><pre class="screen">:msg, contains,
"error"</pre></li><li class="listitem"><div
class="para">
+ The following filter selects syslog messages received from the hostname
<code class="literal">host1</code>:
+ </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">Expression-based
filters</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">
+ To define an expression-based filter, use the following syntax:
+ </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>Do not use regular
expressions</h2></div><div class="admonition"><div
class="para">
+ Regular expressions are currently not supported in expression-based filters.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term">BSD-style
blocks</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">Example 17.1,
“BSD-style block”</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>Example 17.1. BSD-style
block</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"
id="s3-actions">17.1.3.2. Actions</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><dt
class="varlistentry"><span class="term">Saving syslog
messages to log files</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">Section 17.1.3.3.1,
“Generating dynamic file names”</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">Sending syslog messages over the
network</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 # Forwards
messages to 192.168.0.1 via the <code class="systemitem">UDP</code>
protocol</pre><pre class="screen">*.* @@example.com:18 # Forwards
messages to "example.com" using port 18 and the <code
class="systemitem">TCP</code> protocol</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">Output
channels</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">Section 17.2.1,
“Configuring 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">Example 17.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>Example 17.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">Section 17.1.3.3,
“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">
+ The <em
class="replaceable"><code><DB_HOST></code></em>
attribute specifies the database hostname.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code><DB_NAME></code></em>
attribute specifies the name of the database.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code><DB_USER></code></em>
attribute specifies the database user.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code><DB_PASSWORD></code></em>
attribute specifies the password used with the aforementioned database user.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="replaceable"><code><TEMPLATE></code></em>
attribute specifies an optional use of a template that modifies the syslog message. For
more information on templates, refer to <a class="xref"
href="ch-Viewing_and_Managing_Log_Files.html#s3-templates">Section 17.1.3.3,
“Templates”</a>.
+ </div></li></ul></div><div
class="important"><div
class="admonition_header"><h2>Using MySQL and
PostgreSQL</h2></div><div class="admonition"><div
class="para">
+ Currently, <span
class="application"><strong>rsyslog</strong></span>
provides support for <code class="systemitem">MySQL</code> (for more
information, refer to <code class="filename">/usr/share/doc/rsyslog-<em
class="replaceable"><code><version-number></code></em>/rsyslog_mysql.html</code>)
and <code class="systemitem">PostgreSQL</code> databases only. In
order to use the <code class="systemitem">MySQL</code> and <code
class="systemitem">PostgreSQL</code> database writer functionality,
install the <span class="package">rsyslog-mysql</span> and <span
class="package">rsyslog-pgsql</span> packages installed, respectively.
Also, make sure you load the appropriate modules in your <code
class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad ommysql # Output module for MySQL support
+$ModLoad ompgsql # Output module for PostgreSQL support
+</pre><div class="para">
+ For more information on <span
class="application"><strong>rsyslog</strong></span>
modules, refer to <a class="xref"
href="ch-Viewing_and_Managing_Log_Files.html#s2-modules">Section 17.1.2,
“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">Discarding syslog
messages</span></dt><dd><div class="para">
+ To discard your selected messages, use the tilde character (<code
class="literal">~</code>). The following rule discards any cron syslog
messages:
+ </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>Using
templates</h2></div><div class="admonition"><div
class="para">
+ A template must be defined before it is used in an action, otherwise, it is
ignored.
+ </div></div></div><div class="para">
+ For more information on templates, refer to <a class="xref"
href="ch-Viewing_and_Managing_Log_Files.html#s3-templates">Section 17.1.3.3,
“Templates”</a>.
+ </div></div><div class="section"
id="s3-templates"><div class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-templates">17.1.3.3. Templates</h4></div></div></div><div
class="para">
+ Any output that is generated by <span
class="application"><strong>rsyslog</strong></span> can be
modified and formatted according to your needs through the use of templates. To create a
template use the following syntax:
+ </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> is the
template directive that indicates that the text following it, defines a template.
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code><TEMPLATE_NAME></code></em>
is the name of the template. Use this name to refer to the template.
+ </div></li><li class="listitem"><div
class="para">
+ Anything between the two quotation marks (<code
class="literal">"</code>…<code
class="literal">"</code>) is the actual template text. Within this
text, 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">Section 17.1.3.3.2,
“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>The sql and stdsql
options</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">Section 17.1.3.2,
“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"
id="s4-generating-dynamic-fnames">17.1.3.3.1. Generating dynamic file
names</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"
id="s4-properties">17.1.3.3.2. Properties</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">
+ The following are some examples of simple properties:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The following property simply obtains the whole message text of a syslog
message:
+ </div><pre class="screen">%msg%</pre></li><li
class="listitem"><div class="para">
+ The following property obtains the first two characters of the message text of a
syslog message:
+ </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"
id="s4-template-examples">17.1.3.3.3. Template
Examples</h5></div></div></div><div class="para">
+ This section presents few examples of <span
class="application"><strong>rsyslog</strong></span>
templates.
+ </div><div class="para">
+ <a class="xref"
href="ch-Viewing_and_Managing_Log_Files.html#example-temp1">Example 17.3, “A
verbose syslog message template”</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>Example 17.3. A verbose syslog message
template</h6><div class="example-contents"><pre
class="screen">$template
verbose,"%syslogseverity%,%syslogfacility%,%timegenerated%,%HOSTNAME%,%syslogtag%,%msg%\n"</pre></div></div><br
class="example-break" /><div class="para">
+ <a class="xref"
href="ch-Viewing_and_Managing_Log_Files.html#example-temp2">Example 17.4, “A
wall message template”</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>Example 17.4. A wall message
template</h6><div class="example-contents"><pre
class="screen">$template wallmsg,"\r\n\7Message from syslogd@%HOSTNAME%
at %timegenerated% ...\r\n %syslogtag%
%msg%\n\r"</pre></div></div><br class="example-break"
/><div class="para">
+ <a class="xref"
href="ch-Viewing_and_Managing_Log_Files.html#example-temp3">Example 17.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>Example 17.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><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:\nFROMHOST:
'%FROMHOST%', fromhost-ip: '%fromhost-ip%', HOSTNAME:
'%HOSTNAME%', PRI: %PRI%,\nsyslogtag '%syslogtag%', programname:
'%programname%', APP-NAME: '%APP-NAME%', PROCID: '%PROCID%',
MSGID: '%MSGID%',\nTIMESTAMP: '%TIMESTAMP%', STRUCTURED-DATA:
'%STRUCTURED-DATA%',\nmsg: '%msg%'\nescaped msg:
'%msg:::drop-cc%'\nrawmsg:
'%rawmsg%'\n\n\"</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%\n\"</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%\n\"</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%\n\"</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 cla
ss="title" id="s2-rsyslog-cmd-options">17.1.4. <span
class="application"><strong>rsyslog</strong></span> Command
Line Configuration</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">
+ For more information on various <code
class="command">rsyslogd</code> options, refer to <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>Prev</strong>16.5. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-logfiles-locating.html"><strong>Next</strong>17.2. Locating
Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Web_Servers.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Web_Servers.html
new file mode 100644
index 0000000..576146a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Web_Servers.html
@@ -0,0 +1,1280 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 12. Web Servers</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Servers.html" title="Part V. Servers" /><link
rel="prev" href="s2-bind-additional-resources.html"
title="11.2.7. Additional Resources" /><link rel="next"
href="ch-Mail_Servers.html" title="Chapter 13. Mail Servers"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-bind-additional-resources.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" hr
ef="ch-Mail_Servers.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-Web_Servers"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 12. Web
Servers</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">12.1. The Apache HTTP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-features">12.1.1. New
Features</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-changes">12.1.2. Notable
Changes</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-migrating">12.1.3. Updating the
Configuration</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-running">12.1.4. Running the httpd
Service</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-editing">12.1.5. Editing the Configura
tion Files</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-dso">12.1.6. Working with
Modules</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-virtualhosts">12.1.7. Setting Up Virtual
Hosts</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-mod_ssl">12.1.8. Setting Up an SSL
Server</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-resources">12.1.9. Additional
Resources</a></span></dt></dl></dd></dl></div><a
id="id661499" class="indexterm"></a><a
id="id661585" class="indexterm"></a><div
class="para">
+ <code class="systemitem">HTTP</code> (Hypertext Transfer
Protocol) server, or a <em class="firstterm">web server</em>, is a
network service that serves content to a client over the web. This typically means web
pages, but any other documents can be served as well.
+ </div><div xml:lang="en-US" class="section"
id="s1-The_Apache_HTTP_Server" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-The_Apache_HTTP_Server">12.1. The Apache HTTP
Server</h2></div></div></div><a id="id661543"
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 15. 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">
+ There are important differences between the Apache HTTP Server 2.2 and version 2.0, and
if you are upgrading from a previous release of Fedora, you will need to update the
<code class="systemitem">httpd</code> service configuration
accordingly. This section reviews some of the newly added features, outlines important
changes, and guides you through the update of older configuration files.
+ </div><div class="section"
id="s2-apache-version2-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-apache-version2-features">12.1.1. New
Features</h3></div></div></div><a id="id661486"
class="indexterm"></a><div class="para">
+ The Apache HTTP Server version 2.2 introduces the following enhancements:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a id="id661455" class="indexterm"></a>
+ <a id="id661430" class="indexterm"></a>
+ Improved caching modules, that is, <code
class="systemitem">mod_cache</code> and <code
class="systemitem">mod_disk_cache</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="id659901" class="indexterm"></a>
+ Support for proxy load balancing, that is, the <code
class="systemitem">mod_proxy_balancer</code> module.
+ </div></li><li class="listitem"><div
class="para">
+ Support for large files on 32-bit architectures, allowing the web server to handle
files greater than 2GB.
+ </div></li><li class="listitem"><div
class="para">
+ A new structure for authentication and authorization support, replacing the
authentication modules provided in previous versions.
+ </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"
id="s2-apache-version2-changes">12.1.2. Notable
Changes</h3></div></div></div><a id="id661291"
class="indexterm"></a><div class="para">
+ Since version 2.0, few changes have been made to the default <code
class="systemitem">httpd</code> service configuration:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <a id="id661280" class="indexterm"></a>
+ <a id="id661225" class="indexterm"></a>
+ The following modules are no longer loaded by default: <code
class="systemitem">mod_cern_meta</code> and <code
class="systemitem">mod_asis</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="id661215" class="indexterm"></a>
+ The following module is newly loaded by default: <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"
id="s2-apache-version2-migrating">12.1.3. Updating the
Configuration</h3></div></div></div><a id="id661179"
class="indexterm"></a><div class="para">
+ To update the configuration files from the Apache HTTP Server version 2.0, take the
following steps:
+ </div><div class="procedure"><ol class="1"><li
class="step"><div class="para">
+ Make sure all module names are correct, since they may have changed. Adjust the
<code class="option">LoadModule</code> directive for each module
that has been renamed.
+ </div></li><li class="step"><div
class="para">
+ Recompile all third party modules before attempting to load them. This typically
means authentication and authorization modules.
+ </div></li><li class="step"><div
class="para">
+ <a id="id661094" class="indexterm"></a>
+ If you use the <code class="systemitem">mod_userdir</code>
module, make sure the <code class="option">UserDir</code> directive
indicating a directory name (typically <code
class="literal">public_html</code>) is provided.
+ </div></li><li class="step"><div
class="para">
+ If you use the Apache HTTP Secure Server, edit the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> to enable the Secure
Sockets Layer (SSL) protocol.
+ </div></li></ol></div><div class="para">
+ Note that you can check the configuration for possible errors by using the following
command:
+ </div><pre class="screen"><code
class="command">service httpd configtest</code></pre><div
class="para">
+ For more information on upgrading the Apache HTTP Server configuration from version
2.0 to 2.2, refer to <a
href="http://httpd.apache.org/docs/2.2/upgrading.html">http:...;.
+ </div></div><div class="section"
id="s2-apache-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-apache-running">12.1.4. Running the httpd
Service</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">Chapter 7, <em>Services and
Daemons</em></a>.
+ </div><div class="section"
id="s3-apache-running-starting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-running-starting">12.1.4.1. Starting the
Service</h4></div></div></div><a id="id660984"
class="indexterm"></a><div class="para">
+ To run the <code class="systemitem">httpd</code> service, type
the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl start httpd.service</code></pre><div
class="para">
+ If you want the service to start automatically at the boot time, use the following
command:
+ </div><pre class="screen"><code
class="command">systemctl enable
httpd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div><div class="note"><div
class="admonition_header"><h2>Using the secure
server</h2></div><div class="admonition"><div
class="para">
+ If running the Apache HTTP Server as a secure server, a password may be required
after the machine boots if using an encrypted private SSL key.
+ </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"
id="s3-apache-running-stopping">12.1.4.2. Stopping the
Service</h4></div></div></div><a id="id660904"
class="indexterm"></a><div class="para">
+ To stop the running <code class="systemitem">httpd</code>
service, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl stop httpd.service</code></pre><div
class="para">
+ To prevent the service from starting automatically at the boot time, type:
+ </div><pre class="screen"><code
class="command">systemctl disable
httpd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-apache-running-restarting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-running-restarting">12.1.4.3. Restarting the
Service</h4></div></div></div><a id="id660833"
class="indexterm"></a><div class="para">
+ There are two different ways to restart the running <code
class="systemitem">httpd</code> service:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ To restart the service completely, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl restart
httpd.service</code></pre><div class="para">
+ This will stop the running <code
class="systemitem">httpd</code> service, and then start it again. Use
this command after installing or removing a dynamically loaded module such as PHP.
+ </div></li><li class="listitem"><div
class="para">
+ To only reload the configuration, as <code
class="systemitem">root</code>, type:
+ </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">
+ To reload the configuration without affecting active requests, run the following
command as <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">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><div class="section"
id="s3-apache-running-status"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-running-status">12.1.4.4. Checking the Service
Status</h4></div></div></div><a id="id660689"
class="indexterm"></a><div class="para">
+ To check whether the service is running, type the following at a shell prompt:
+ </div><pre class="screen"><code
class="command">systemctl is-active
httpd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div></div><div class="section"
id="s2-apache-editing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-apache-editing">12.1.5. Editing the Configuration
Files</h3></div></div></div><div class="para">
+ When the <code class="systemitem">httpd</code> service is
started, by default, it reads the configuration from locations that are listed in <a
class="xref"
href="ch-Web_Servers.html#table-apache-editing-files">Table 12.1, “The httpd
service configuration files”</a>.
+ </div><div class="table"
id="table-apache-editing-files"><h6>Table 12.1. The httpd service
configuration files</h6><div class="table-contents"><table
summary="The httpd service configuration files"
border="1"><colgroup><col width="33%"
class="option" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id660574" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf/httpd.conf</code>
+ </td><td>
+ The main configuration file.
+ </td></tr><tr><td>
+ <a id="id660534" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf.d/</code>
+ </td><td>
+ An auxiliary directory for configuration files that are included in the main
configuration file.
+ </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">Section 12.1.4.3,
“Restarting the Service”</a> for more information on how to restart the <code
class="systemitem">httpd</code> service.
+ </div><a id="id660475"
class="indexterm"></a><div class="para">
+ To check the configuration for possible errors, type the following at a shell prompt:
+ </div><pre class="screen"><code
class="command">service httpd configtest</code></pre><div
class="para">
+ To make the recovery from mistakes easier, it is recommended that you make a copy of
the original file before editing it.
+ </div><div class="section"
id="s3-apache-httpdconf-directives"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-httpdconf-directives">12.1.5.1. Common httpd.conf
Directives</h4></div></div></div><a id="id660440"
class="indexterm"></a><div class="para">
+ The following directives are commonly used in the <code
class="filename">/etc/httpd/conf/httpd.conf</code> configuration file:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id660398" class="indexterm"></a>
+ <code class="option"><Directory></code>
</span></dt><dd><div class="para">
+ The <code class="option"><Directory></code>
directive allows you to apply certain directives to a particular directory only. It takes
the following form:
+ </div><pre class="programlisting"><Directory <em
class="replaceable"><code>directory</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Directory></pre><div class="para">
+ The <em
class="replaceable"><code>directory</code></em> can be
either a full path to an existing directory in the local file system, or a wildcard
expression.
+ </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>Example 12.1. Using the
<Directory> directive</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="id660286" class="indexterm"></a>
+ <code class="option"><IfDefine></code>
</span></dt><dd><div class="para">
+ The <code class="option">IfDefine</code> directive allows
you to use certain directives only when a particular parameter is supplied on the command
line. It takes the following form:
+ </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>Example 12.2. Using the
<IfDefine> directive</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="id660153" class="indexterm"></a>
+ <code class="option"><IfModule></code>
</span></dt><dd><div class="para">
+ The <code class="option"><IfModule></code>
directive allows you to use certain directive only when a particular module is loaded. It
takes the following form:
+ </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>Example 12.3. Using the
<IfModule> directive</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="id660055" class="indexterm"></a>
+ <code class="option"><Location></code>
</span></dt><dd><div class="para">
+ The <code class="option"><Location></code>
directive allows you to apply certain directives to a particular URL only. It takes the
following form:
+ </div><pre class="programlisting"><Location <em
class="replaceable"><code>url</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Location></pre><div class="para">
+ The <em
class="replaceable"><code>url</code></em> can be either a
path relative to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/server-info</code>), or an external URL such as
<code
class="literal">http://example.com/server-info</code>.
+ </div><div class="example"
id="example-apache-httpdconf-location"><h6>Example 12.4. Using the
<Location> directive</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="id659960" class="indexterm"></a>
+ <code class="option"><Proxy></code>
</span></dt><dd><div class="para">
+ The <code class="option"><Proxy></code>
directive allows you to apply certain directives to the proxy server only. It takes the
following form:
+ </div><pre class="programlisting"><Proxy <em
class="replaceable"><code>pattern</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Proxy></pre><div class="para">
+ The <em
class="replaceable"><code>pattern</code></em> can be an
external URL, or a wildcard expression (for example, <code
class="literal">http://example.com/*</code>).
+ </div><div class="example"
id="example-apache-httpdconf-proxy"><h6>Example 12.5. Using the
<Proxy> directive</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="id659871" class="indexterm"></a>
+ <code class="option"><VirtualHost></code>
</span></dt><dd><div class="para">
+ The <code class="option"><VirtualHost></code>
directive allows you apply certain directives to particular virtual hosts only. It takes
the following form:
+ </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">
+ The <em
class="replaceable"><code>address</code></em> can be an IP
address, a fully qualified domain name, or a special form as described in <a
class="xref"
href="ch-Web_Servers.html#table-apache-httpdconf-virtualhost">Table 12.2,
“Available <VirtualHost> options”</a>.
+ </div><div class="table"
id="table-apache-httpdconf-virtualhost"><h6>Table 12.2. Available
<VirtualHost> options</h6><div
class="table-contents"><table summary="Available
<VirtualHost> options" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">*</code>
+ </td><td>
+ Represents all IP addresses.
+ </td></tr><tr><td>
+ <code class="option">_default_</code>
+ </td><td>
+ Represents unmatched IP addresses.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-virtualhost"><h6>Example 12.6. Using the
<VirtualHost> directive</h6><div
class="example-contents"><pre
class="programlisting"><VirtualHost *:80>
+ ServerAdmin webmaster(a)penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName
penguin.example.com
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.example.com-access_log common
+</VirtualHost></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="id659684" 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="id659634" class="indexterm"></a><a
id="id659608" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>filename</code></em> is a name of
the file to look for in the requested directory. By default, the server looks for <code
class="filename">.htaccess</code>.
+ </div><a id="id659544"
class="indexterm"></a><a id="id659553"
class="indexterm"></a><div class="para">
+ For security reasons, the directive is typically followed by the <code
class="literal">Files</code> tag to prevent the files beginning with
<code class="filename">.ht</code> from being accessed by web
clients. This includes the <code class="filename">.htaccess</code>
and <code class="filename">.htpasswd</code> files.
+ </div><div class="example"
id="example-apache-httpdconf-accessfilename"><h6>Example 12.7. Using
the AccessFileName directive</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="id649819" class="indexterm"></a>
+ <code class="option">Action</code>
</span></dt><dd><div class="para">
+ The <code class="option">Action</code> directive allows you
to specify a CGI script to be executed when a certain media type is requested. It takes
the following form:
+ </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>Example 12.8. Using the Action
directive</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="id659399" 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>Example 12.9. Using
the AddDescription directive</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="id659302"
class="indexterm"></a>
+ <code class="option">AddEncoding</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddEncoding</code> directive allows
you to specify an encoding type for a particular file extension. It takes the following
form:
+ </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>Example 12.10. Using the
AddEncoding directive</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="id659184"
class="indexterm"></a>
+ <code class="option">AddHandler</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddHandler</code> directive allows
you to map certain file extensions to a selected handler. It takes the following form:
+ </div><pre class="programlisting">AddHandler <em
class="replaceable"><code>handler</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>handler</code></em> has to be a
name of previously defined handler. 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">.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>Example 12.11. Using the
AddHandler option</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="id659103"
class="indexterm"></a>
+ <code class="option">AddIcon</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddIcon</code> directive allows you
to specify an icon to be displayed for a particular file in server-generated directory
listings. It takes the following form:
+ </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>Table 12.3. Available AddIcon
options</h6><div class="table-contents"><table
summary="Available AddIcon options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">^^DIRECTORY^^</code>
+ </td><td>
+ Represents a directory.
+ </td></tr><tr><td>
+ <code class="option">^^BLANKICON^^</code>
+ </td><td>
+ Represents a blank line.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-addicon"><h6>Example 12.12. Using the
AddIcon directive</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="id658838"
class="indexterm"></a>
+ <code class="option">AddIconByEncoding</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddIconByEncoding</code> directive
allows you to specify an icon to be displayed for a particular encoding type in
server-generated directory listings. It takes the following form:
+ </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>Example 12.13. Using
the AddIconByEncoding directive</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="id658819"
class="indexterm"></a>
+ <code class="option">AddIconByType</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddIconByType</code> directive
allows you to specify an icon to be displayed for a particular media type in
server-generated directory listings. It takes the following form:
+ </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>Example 12.14. Using
the AddIconByType directive</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="id658709"
class="indexterm"></a>
+ <code class="option">AddLanguage</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddLanguage</code> directive allows
you to associate a file extension with a specific language. It takes the following form:
+ </div><pre class="programlisting">AddLanguage <em
class="replaceable"><code>language</code></em> <em
class="replaceable"><code>extension</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>language</code></em> has to be a
valid MIME language such as <code class="literal">cs</code>,
<code class="literal">en</code>, or <code
class="literal">fr</code>. 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="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>Example 12.15. Using the
AddLanguage directive</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="id658608"
class="indexterm"></a>
+ <code class="option">AddType</code>
</span></dt><dd><div class="para">
+ The <code class="option">AddType</code> directive allows you
to define or override the media type for a particular file extension. It takes the
following form:
+ </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>Example 12.16. Using the
AddType directive</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="id658491"
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="id658415"
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>Example 12.17. Using the Alias
directive</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="id658355" 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>Example 12.18. Using the Allow
directive</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="id658273" class="indexterm"></a>
+ <code class="option">AllowOverride</code>
</span></dt><dd><a id="id658240"
class="indexterm"></a><a id="id658205"
class="indexterm"></a><div class="para">
+ The <code class="option">AllowOverride</code> directive
allows you to specify which directives in a <code
class="filename">.htaccess</code> file can override the default
configuration. It takes the following form:
+ </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">Table 12.4,
“Available AllowOverride options”</a>.
+ </div><div class="table"
id="table-apache-httpdconf-allowoverride"><h6>Table 12.4. Available
AllowOverride options</h6><div class="table-contents"><table
summary="Available AllowOverride options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">All</code>
+ </td><td>
+ All directives in <code
class="filename">.htaccess</code> are allowed to override earlier
configuration settings.
+ </td></tr><tr><td>
+ <code class="option">None</code>
+ </td><td>
+ No directive in <code class="filename">.htaccess</code>
is allowed to override earlier configuration settings.
+ </td></tr><tr><td>
+ <code class="option">AuthConfig</code>
+ </td><td>
+ Allows the use of authorization directives such as <code
class="option">AuthName</code>, <code
class="option">AuthType</code>, or <code
class="option">Require</code>.
+ </td></tr><tr><td>
+ <code class="option">FileInfo</code>
+ </td><td>
+ 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>
+ <code class="option">Indexes</code>
+ </td><td>
+ Allows the use of directory indexing directives such as <code
class="option">AddDescription</code>, <code
class="option">AddIcon</code>, or <code
class="option">FancyIndexing</code>.
+ </td></tr><tr><td>
+ <code class="option">Limit</code>
+ </td><td>
+ Allows the use of host access directives, that is, <code
class="option">Allow</code>, <code
class="option">Deny</code>, and <code
class="option">Order</code>.
+ </td></tr><tr><td>
+ <code class="option">Options</code>[<span
class="optional">=<em
class="replaceable"><code>option</code></em>,…</span>]
+ </td><td>
+ Allows the use of the <code
class="option">Options</code> directive. Additionally, you can provide
a comma-separated list of options to customize which options can be set using this
directive.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-allowoverride"><h6>Example 12.19. Using
the AllowOverride directive</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="id657893"
class="indexterm"></a>
+ <code class="option">BrowserMatch</code>
</span></dt><dd><div class="para">
+ The <code class="option">BrowserMatch</code> directive
allows you to modify the server behavior based on the client's web browser type. It
takes the following form:
+ </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>Example 12.20. Using the
BrowserMatch directive</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="id657778"
class="indexterm"></a>
+ <code class="option">CacheDefaultExpire</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheDefaultExpire</code> option
allows you to set how long to cache a document that does not have any expiration date or
the date of its last modification specified. It takes the following form:
+ </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>Example 12.21. Using
the CacheDefaultExpire directive</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="id657708"
class="indexterm"></a>
+ <code class="option">CacheDisable</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheDisable</code> directive
allows you to disable caching of certain URLs. It takes the following form:
+ </div><pre class="programlisting">CacheDisable <em
class="replaceable"><code>path</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>path</code></em> must be relative
to the directory specified by the <code
class="option">DocumentRoot</code> directive (for example, <code
class="literal">/files/</code>).
+ </div><div class="example"
id="example-apache-httpdconf-cachedisable"><h6>Example 12.22. Using the
CacheDisable directive</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="id657625"
class="indexterm"></a>
+ <code class="option">CacheEnable</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheEnable</code> directive allows
you to specify a cache type to be used for certain URLs. It takes the following form:
+ </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">Table 12.5,
“Available cache types”</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>Table 12.5. Available cache
types</h6><div class="table-contents"><table
summary="Available cache types" border="1"><colgroup><col
width="25%" class="type" /><col width="75%"
class="description" /></colgroup><thead><tr><th>
+ Type
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">mem</code>
+ </td><td>
+ The memory-based storage manager.
+ </td></tr><tr><td>
+ <code class="option">disk</code>
+ </td><td>
+ The disk-based storage manager.
+ </td></tr><tr><td>
+ <code class="option">fd</code>
+ </td><td>
+ The file descriptor cache.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-cacheenable"><h6>Example 12.23. Using the
CacheEnable directive</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="id657426"
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>Example 12.24. Using
the CacheLastModifiedFactor directive</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="id657350"
class="indexterm"></a>
+ <code class="option">CacheMaxExpire</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheMaxExpire</code> directive
allows you to specify the maximum amount of time to cache a document. It takes the
following form:
+ </div><pre class="programlisting">CacheMaxExpire <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">86400</code>
(that is, one day).
+ </div><div class="example"
id="example-apache-httpdconf-cachemaxexpire"><h6>Example 12.25. Using
the CacheMaxExpire directive</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="id657248"
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">Table 12.6,
“Available CacheNegotiatedDocs options”</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>Table 12.6. Available
CacheNegotiatedDocs options</h6><div
class="table-contents"><table summary="Available CacheNegotiatedDocs
options" border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables caching the content-negotiated documents.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ 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>Example 12.26. Using
the CacheNegotiatedDocs directive</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="id657073"
class="indexterm"></a>
+ <code class="option">CacheRoot</code>
</span></dt><dd><div class="para">
+ The <code class="option">CacheRoot</code> directive allows
you to specify the directory to store cache files in. It takes the following form:
+ </div><pre class="programlisting">CacheRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="id657027" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>directory</code></em> must be a
full path to an existing directory in the local file system. The default option is
<code class="filename">/var/cache/mod_proxy/</code>.
+ </div><div class="example"
id="example-apache-httpdconf-cacheroot"><h6>Example 12.27. Using the
CacheRoot directive</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="id656966" 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="id656919" 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>Example 12.28. Using the
CustomLog directive</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="id656852"
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>Example 12.29. Using the
DefaultIcon directive</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="id656766" class="indexterm"></a>
+ <code class="option">DefaultType</code>
</span></dt><dd><div class="para">
+ The <code class="option">DefaultType</code> directive allows
you to specify a media type to be used in case the proper MIME type cannot be determined
by the server. It takes the following form:
+ </div><pre class="programlisting">DefaultType <em
class="replaceable"><code>content-type</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>, <code
class="literal">application/pdf</code>, etc.
+ </div><div class="example"
id="example-apache-httpdconf-defaulttype"><h6>Example 12.30. Using the
DefaultType directive</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="id656671"
class="indexterm"></a>
+ <code class="option">Deny</code>
</span></dt><dd><div class="para">
+ The <code class="option">Deny</code> directive allows you to
specify which clients are denied access to a given directory. It takes the following
form:
+ </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>Example 12.31. Using the Deny
directive</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="id656588"
class="indexterm"></a>
+ <code class="option">DirectoryIndex</code>
</span></dt><dd><div class="para">
+ The <code class="option">DirectoryIndex</code> directive
allows you to specify a document to be served to a client when a directory is requested
(that is, when the URL ends with the <code class="literal">/</code>
character). It takes the following form:
+ </div><pre class="programlisting">DirectoryIndex <em
class="replaceable"><code>filename</code></em>…</pre><div
class="para">
+ The <em
class="replaceable"><code>filename</code></em> is a name of
the file to look for in the requested directory. By default, the server looks for <code
class="filename">index.html</code>, and <code
class="filename">index.html.var</code>.
+ </div><div class="example"
id="example-apache-httpdconf-directoryindex"><h6>Example 12.32. Using
the DirectoryIndex directive</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="id656376"
class="indexterm"></a>
+ <code class="option">DocumentRoot</code>
</span></dt><dd><div class="para">
+ The <code class="option">DocumentRoot</code> directive
allows you to specify the main directory from which the content is served. It takes the
following form:
+ </div><pre class="programlisting">DocumentRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="id656464" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>directory</code></em> must be a
full path to an existing directory in the local file system. The default option is
<code class="filename">/var/www/html/</code>.
+ </div><div class="example"
id="example-apache-httpdconf-documentroot"><h6>Example 12.33. Using the
DocumentRoot directive</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="id656404"
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>Example 12.34. Using
the ErrorDocument directive</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="id656288" 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="id656240" 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>Example 12.35. Using the
ErrorLog directive</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="id656178"
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">Table 12.7,
“Available ExtendedStatus options”</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-extendedstatus"><h6>Table 12.7. Available
ExtendedStatus options</h6><div class="table-contents"><table
summary="Available ExtendedStatus options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables generating the detailed server status.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables generating the detailed server status.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-extendedstatus"><h6>Example 12.36. Using
the ExtendedStatus directive</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="id656001"
class="indexterm"></a>
+ <code class="option">Group</code>
</span></dt><dd><div class="para">
+ The <code class="option">Group</code> directive allows you
to specify the group under which the <code
class="systemitem">httpd</code> service will run. It takes the
following form:
+ </div><pre class="programlisting">Group <em
class="replaceable"><code>group</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>group</code></em> has to be an
existing UNIX group. The default option is <code
class="option">apache</code>.
+ </div><div class="para">
+ Note that <code class="option">Group</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-group"><h6>Example 12.37. Using the Group
directive</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="id655917" class="indexterm"></a>
+ <code class="option">HeaderName</code>
</span></dt><dd><div class="para">
+ The <code class="option">HeaderName</code> directive allows
you to specify a file to be prepended to the beginning of the server-generated directory
listing. It takes the following form:
+ </div><pre class="programlisting">HeaderName <em
class="replaceable"><code>filename</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>filename</code></em> is a name of
the file to look for in the requested directory. By default, the server looks for <code
class="filename">HEADER.html</code>.
+ </div><div class="example"
id="example-apache-httpdconf-headername"><h6>Example 12.38. Using the
HeaderName directive</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="id655856"
class="indexterm"></a>
+ <code class="option">HostnameLookups</code>
</span></dt><dd><div class="para">
+ The <code class="option">HostnameLookups</code> directive
allows you to enable automatic resolving of IP addresses. It takes the following form:
+ </div><pre class="programlisting">HostnameLookups <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-hostnamelookup">Table 12.8,
“Available HostnameLookups options”</a>. To conserve resources on the server, the
default option is <code class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-hostnamelookup"><h6>Table 12.8. Available
HostnameLookups options</h6><div class="table-contents"><table
summary="Available HostnameLookups options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables resolving the IP address for each connection so that the hostname can
be logged. However, this also adds a significant processing overhead.
+ </td></tr><tr><td>
+ <code class="option">Double</code>
+ </td><td>
+ Enables performing the double-reverse DNS lookup. In comparison to the above
option, this adds even more processing overhead.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables resolving the IP address for each connection.
+ </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>Example 12.39. Using
the HostnameLookups directive</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="id655707"
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="id655672" 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>Example 12.40. Using the
Include directive</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="id655624"
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">
+ The <em
class="replaceable"><code>filename</code></em> option can
be either a full file name, or a wildcard expression.
+ </div><div class="example"
id="example-apache-httpdconf-indexignore"><h6>Example 12.41. Using the
IndexIgnore directive</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="id655550"
class="indexterm"></a>
+ <code class="option">IndexOptions</code>
</span></dt><dd><div class="para">
+ The <code class="option">IndexOptions</code> directive
allows you to customize the behavior of server-generated directory listings. It takes the
following form:
+ </div><pre class="programlisting">IndexOptions <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-indexoptions">Table 12.9,
“Available directory listing options”</a>. The default options are <code
class="option">Charset=UTF-8</code>, <code
class="option">FancyIndexing</code>, <code
class="option">HTMLTable</code>, <code
class="option">NameWidth=*</code>, and <code
class="option">VersionSort</code>.
+ </div><div class="table"
id="table-apache-httpdconf-indexoptions"><h6>Table 12.9. Available
directory listing options</h6><div class="table-contents"><table
summary="Available directory listing options"
border="1"><colgroup><col width="33%"
class="option" /><col width="67%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Charset</code>=<em
class="replaceable"><code>encoding</code></em>
+ </td><td>
+ 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>
+ <code class="option">Type</code>=<em
class="replaceable"><code>content-type</code></em>
+ </td><td>
+ 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>
+ <code class="option">DescriptionWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td>
+ 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>
+ <code class="option">FancyIndexing</code>
+ </td><td>
+ 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>
+ <code class="option">FolderFirst</code>
+ </td><td>
+ Enables listing directories first, always placing them above files.
+ </td></tr><tr><td>
+ <code class="option">HTMLTable</code>
+ </td><td>
+ Enables the use of HTML tables for directory listings.
+ </td></tr><tr><td>
+ <code class="option">IconsAreLinks</code>
+ </td><td>
+ Enables using the icons as links.
+ </td></tr><tr><td>
+ <code class="option">IconHeight</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies an icon height. The <em
class="replaceable"><code>value</code></em> is a number of
pixels.
+ </td></tr><tr><td>
+ <code class="option">IconWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies an icon width. The <em
class="replaceable"><code>value</code></em> is a number of
pixels.
+ </td></tr><tr><td>
+ <code class="option">IgnoreCase</code>
+ </td><td>
+ Enables sorting files and directories in a case-sensitive manner.
+ </td></tr><tr><td>
+ <code class="option">IgnoreClient</code>
+ </td><td>
+ Disables accepting query variables from a client.
+ </td></tr><tr><td>
+ <code class="option">NameWidth</code>=<em
class="replaceable"><code>value</code></em>
+ </td><td>
+ 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>
+ <code class="option">ScanHTMLTitles</code>
+ </td><td>
+ 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>
+ <code class="option">ShowForbidden</code>
+ </td><td>
+ Enables listing the files with otherwise restricted access.
+ </td></tr><tr><td>
+ <code class="option">SuppressColumnSorting</code>
+ </td><td>
+ Disables re-sorting a directory listing by clicking on a column header.
+ </td></tr><tr><td>
+ <code class="option">SuppressDescription</code>
+ </td><td>
+ Disables reserving a space for file descriptions.
+ </td></tr><tr><td>
+ <code class="option">SuppressHTMLPreamble</code>
+ </td><td>
+ 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>
+ <code class="option">SuppressIcon</code>
+ </td><td>
+ Disables the use of icons in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressLastModified</code>
+ </td><td>
+ Disables displaying the date of the last modification field in directory
listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressRules</code>
+ </td><td>
+ Disables the use of horizontal lines in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressSize</code>
+ </td><td>
+ Disables displaying the file size field in directory listings.
+ </td></tr><tr><td>
+ <code class="option">TrackModified</code>
+ </td><td>
+ Enables returning the <code
class="literal">Last-Modified</code> and <code
class="literal">ETag</code> values in the HTTP header.
+ </td></tr><tr><td>
+ <code class="option">VersionSort</code>
+ </td><td>
+ Enables sorting files that contain a version number in the expected manner.
+ </td></tr><tr><td>
+ <code class="option">XHTML</code>
+ </td><td>
+ Enables the use of XHTML 1.0 instead of the default HTML 3.2.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-indexoptions"><h6>Example 12.42. Using the
IndexOptions directive</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="id655036" 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">Table 12.10,
“Available KeepAlive options”</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-keepalive"><h6>Table 12.10. Available
KeepAlive options</h6><div class="table-contents"><table
summary="Available KeepAlive options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables the persistent connections. In this case, the server will accept more
than one request per connection.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables the keep-alive connections.
+ </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>Example 12.43. Using the
KeepAlive directive</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="id654879"
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">
+ The <em
class="replaceable"><code>time</code></em> is specified in
seconds. The default option is <code class="literal">15</code>.
+ </div><div class="example"
id="example-apache-httpdconf-keepalivetimeout"><h6>Example 12.44. Using
the KeepAliveTimeout directive</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="id654815"
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">
+ The <em
class="replaceable"><code>language</code></em> has to be a
valid MIME language such as <code class="literal">cs</code>,
<code class="literal">en</code>, or <code
class="literal">fr</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-languagepriority"><h6>Example 12.45. Using
the LanguagePriority directive</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="id654742"
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">
+ The <em
class="replaceable"><code>ip-address</code></em> is
optional and unless supplied, the server will accept incoming requests on a given <em
class="replaceable"><code>port</code></em> from all IP
addresses. Since the <em
class="replaceable"><code>protocol</code></em> is
determined automatically from the port number, it can be usually omitted. The default
option is to listen to port <code class="literal">80</code>.
+ </div><div class="para">
+ Note that if the server is configured to listen to a port under 1024, only
superuser will be able to start the <code
class="systemitem">httpd</code> service.
+ </div><div class="example"
id="example-apache-httpdconf-listen"><h6>Example 12.46. Using the
Listen directive</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="id654654" 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="id654610" class="indexterm"></a><a
id="id654592" 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">
+ Refer to <a class="xref"
href="ch-Web_Servers.html#s2-apache-dso">Section 12.1.6, “Working with
Modules”</a> for more information on the Apache HTTP Server's DSO support.
+ </div><div class="example"
id="example-apache-httpdconf-loadmodule"><h6>Example 12.47. Using the
LoadModule directive</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="id654530" 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">Table 12.11,
“Common LogFormat options”</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>Table 12.11. Common LogFormat
options</h6><div class="table-contents"><table
summary="Common LogFormat options"
border="1"><colgroup><col width="13%"
class="option" /><col width="88%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">%b</code>
+ </td><td>
+ Represents the size of the response in bytes.
+ </td></tr><tr><td>
+ <code class="option">%h</code>
+ </td><td>
+ Represents the IP address or hostname of a remote client.
+ </td></tr><tr><td>
+ <code class="option">%l</code>
+ </td><td>
+ Represents the remote log name if supplied. If not, a hyphen (that is,
<code class="literal">-</code>) is used instead.
+ </td></tr><tr><td>
+ <code class="option">%r</code>
+ </td><td>
+ Represents the first line of the request string as it came from the browser or
client.
+ </td></tr><tr><td>
+ <code class="option">%s</code>
+ </td><td>
+ Represents the status code.
+ </td></tr><tr><td>
+ <code class="option">%t</code>
+ </td><td>
+ Represents the date and time of the request.
+ </td></tr><tr><td>
+ <code class="option">%u</code>
+ </td><td>
+ 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>
+ <code class="option">%{<em
class="replaceable"><code>field</code></em>}</code>
+ </td><td>
+ 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>Example 12.48. Using the
LogFormat directive</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="id654288" 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">Table 12.12,
“Available LogLevel options”</a>. The default option is <code
class="option">warn</code>.
+ </div><div class="table"
id="table-apache-httpdconf-loglevel"><h6>Table 12.12. Available
LogLevel options</h6><div class="table-contents"><table
summary="Available LogLevel options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">emerg</code>
+ </td><td>
+ Only the emergency situations when the server cannot perform its work are
logged.
+ </td></tr><tr><td>
+ <code class="option">alert</code>
+ </td><td>
+ All situations when an immediate action is required are logged.
+ </td></tr><tr><td>
+ <code class="option">crit</code>
+ </td><td>
+ All critical conditions are logged.
+ </td></tr><tr><td>
+ <code class="option">error</code>
+ </td><td>
+ All error messages are logged.
+ </td></tr><tr><td>
+ <code class="option">warn</code>
+ </td><td>
+ All warning messages are logged.
+ </td></tr><tr><td>
+ <code class="option">notice</code>
+ </td><td>
+ Even normal, but still significant situations are logged.
+ </td></tr><tr><td>
+ <code class="option">info</code>
+ </td><td>
+ Various informational messages are logged.
+ </td></tr><tr><td>
+ <code class="option">debug</code>
+ </td><td>
+ Various debugging messages are logged.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-loglevel"><h6>Example 12.49. Using the
LogLevel directive</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="id654070"
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>Example 12.50. Using
the MaxKeepAliveRequests option</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="id654006"
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>Using secure HTTP
connections</h2></div><div class="admonition"><div
class="para">
+ Name-based virtual hosts <span
class="emphasis"><em>only</em></span> work with non-secure
HTTP connections. If using virtual hosts with a secure server, use IP address-based
virtual hosts instead.
+ </div></div></div><div class="example"
id="example-apache-httpdconf-namevirtualhost"><h6>Example 12.51. Using
the NameVirtualHost directive</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="id653897"
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">
+ 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-options">Table 12.13,
“Available server features”</a>.
+ </div><div class="table"
id="table-apache-httpdconf-options"><h6>Table 12.13. Available server
features</h6><div class="table-contents"><table
summary="Available server features"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">ExecCGI</code>
+ </td><td>
+ Enables the execution of CGI scripts.
+ </td></tr><tr><td>
+ <code class="option">FollowSymLinks</code>
+ </td><td>
+ Enables following symbolic links in the directory.
+ </td></tr><tr><td>
+ <code class="option">Includes</code>
+ </td><td>
+ Enables server-side includes.
+ </td></tr><tr><td>
+ <code class="option">IncludesNOEXEC</code>
+ </td><td>
+ Enables server-side includes, but does not allow the execution of commands.
+ </td></tr><tr><td>
+ <code class="option">Indexes</code>
+ </td><td>
+ Enables server-generated directory listings.
+ </td></tr><tr><td>
+ <code class="option">MultiViews</code>
+ </td><td>
+ Enables content-negotiated <span class="quote">“<span
class="quote">MultiViews</span>”</span>.
+ </td></tr><tr><td>
+ <code class="option">SymLinksIfOwnerMatch</code>
+ </td><td>
+ Enables following symbolic links in the directory when both the link and the
target file have the same owner.
+ </td></tr><tr><td>
+ <code class="option">All</code>
+ </td><td>
+ Enables all of the features above with the exception of <code
class="option">MultiViews</code>.
+ </td></tr><tr><td>
+ <code class="option">None</code>
+ </td><td>
+ Disables all of the features above.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-options"><h6>Example 12.52. Using the
Options directive</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="id653669"
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">Table 12.14,
“Available Order options”</a>. The default option is <code
class="option">allow,deny</code>.
+ </div><div class="table"
id="table-apache-httpdconf-order"><h6>Table 12.14. Available Order
options</h6><div class="table-contents"><table
summary="Available Order options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow,deny</code>
+ </td><td>
+ <code class="option">Allow</code> directives are
evaluated first.
+ </td></tr><tr><td>
+ <code class="option">deny,allow</code>
+ </td><td>
+ <code class="option">Deny</code> directives are
evaluated first.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-order"><h6>Example 12.53. Using the Order
directive</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="id653508"
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="id653470" 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>Example 12.54. Using the
PidFile directive</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="id653421"
class="indexterm"></a>
+ <code class="option">ProxyRequests</code>
</span></dt><dd><div class="para">
+ The <code class="option">ProxyRequests</code> directive
allows you to enable forward proxy requests. It takes the following form:
+ </div><pre class="programlisting">ProxyRequests <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-proxyrequests">Table 12.15,
“Available ProxyRequests options”</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-proxyrequests"><h6>Table 12.15. Available
ProxyRequests options</h6><div class="table-contents"><table
summary="Available ProxyRequests options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables forward proxy requests.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables forward proxy requests.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="example"
id="example-apache-httpdconf-proxyrequests"><h6>Example 12.55. Using
the ProxyRequests directive</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="id653282"
class="indexterm"></a>
+ <code class="option">ReadmeName</code>
</span></dt><dd><div class="para">
+ The <code class="option">ReadmeName</code> directive allows
you to specify a file to be appended to the end of the server-generated directory listing.
It takes the following form:
+ </div><pre class="programlisting">ReadmeName <em
class="replaceable"><code>filename</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>filename</code></em> is a name of
the file to look for in the requested directory. By default, the server looks for <code
class="filename">README.html</code>.
+ </div><div class="example"
id="example-apache-httpdconf-readmename"><h6>Example 12.56. Using the
ReadmeName directive</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="id653221"
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">Table 12.16,
“Available status options”</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>Table 12.16. Available status
options</h6><div class="table-contents"><table
summary="Available status options"
border="1"><colgroup><col width="25%"
class="status" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Status
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">permanent</code>
+ </td><td>
+ 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>
+ <code class="option">temp</code>
+ </td><td>
+ Indicates that the requested resource has been moved only temporarily. The
<code class="literal">302</code> (Found) status code is returned to
a client.
+ </td></tr><tr><td>
+ <code class="option">seeother</code>
+ </td><td>
+ Indicates that the requested resource has been replaced. The <code
class="literal">303</code> (See Other) status code is returned to a
client.
+ </td></tr><tr><td>
+ <code class="option">gone</code>
+ </td><td>
+ Indicates that the requested resource has been removed permanently. The
<code class="literal">410</code> (Gone) status is returned to a
client.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="id652996"
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>Example 12.57. Using the
Redirect directive</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="id652998" class="indexterm"></a>
+ <code class="option">ScriptAlias</code>
</span></dt><dd><div class="para">
+ The <code class="option">ScriptAlias</code> directive allows
you to specify the location of CGI scripts. It takes the following form:
+ </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="id652946"
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>Example 12.58. Using the
ScriptAlias directive</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="id652873" 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">
+ The default option is <code
class="literal">root@localhost</code>.
+ </div><div class="para">
+ This directive is commonly set to <code
class="literal">webmaster@<em
class="replaceable"><code>hostname</code></em></code>,
where <em class="replaceable"><code>hostname</code></em>
is the address of the server. Once set, alias <code
class="literal">webmaster</code> to the person responsible for the web
server in <code class="filename">/etc/aliases</code>, and as
superuser, run the <code class="command">newaliases</code> command.
+ </div><div class="example"
id="example-apache-httpdconf-serveradmin"><h6>Example 12.59. Using the
ServerAdmin directive</h6><div class="example-contents"><pre
class="programlisting">ServerAdmin
webmaster(a)penguin.example.com</pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="id652806" 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>Example 12.60. Using the
ServerName directive</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="id652720" class="indexterm"></a>
+ <code class="option">ServerRoot</code>
</span></dt><dd><div class="para">
+ The <code class="option">ServerRoot</code> directive allows
you to specify the directory in which the server operates. It takes the following form:
+ </div><pre class="programlisting">ServerRoot <em
class="replaceable"><code>directory</code></em></pre><a
id="id652686" class="indexterm"></a><div
class="para">
+ The <em
class="replaceable"><code>directory</code></em> must be a
full path to an existing directory in the local file system. The default option is
<code class="filename">/etc/httpd/</code>.
+ </div><div class="example"
id="example-apache-httpd-serverroot"><h6>Example 12.61. Using the
ServerRoot directive</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="id652639"
class="indexterm"></a>
+ <code class="option">ServerSignature</code>
</span></dt><dd><div class="para">
+ The <code class="option">ServerSignature</code> directive
allows you to enable displaying information about the server on server-generated
documents. It takes the following form:
+ </div><pre class="programlisting">ServerSignature <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-serversignature">Table 12.17,
“Available ServerSignature options”</a>. The default option is <code
class="option">On</code>.
+ </div><div class="table"
id="table-apache-httpdconf-serversignature"><h6>Table 12.17. Available
ServerSignature options</h6><div class="table-contents"><table
summary="Available ServerSignature options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables appending the server name and version to server-generated pages.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables appending the server name and version to server-generated pages.
+ </td></tr><tr><td>
+ <code class="option">EMail</code>
+ </td><td>
+ 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>Example 12.62. Using
the ServerSignature directive</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="id652480"
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">Table 12.18,
“Available ServerTokens options”</a>. The default option is <code
class="option">OS</code>.
+ </div><div class="table"
id="table-apache-httpdconf-servertokens"><h6>Table 12.18. Available
ServerTokens options</h6><div class="table-contents"><table
summary="Available ServerTokens options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Prod</code>
+ </td><td>
+ Includes the product name only (that is, <code
class="literal">Apache</code>).
+ </td></tr><tr><td>
+ <code class="option">Major</code>
+ </td><td>
+ Includes the product name and the major version of the server (for example,
<code class="literal">2</code>).
+ </td></tr><tr><td>
+ <code class="option">Minor</code>
+ </td><td>
+ Includes the product name and the minor version of the server (for example,
<code class="literal">2.2</code>).
+ </td></tr><tr><td>
+ <code class="option">Min</code>
+ </td><td>
+ Includes the product name and the minimal version of the server (for example,
<code class="literal">2.2.15</code>).
+ </td></tr><tr><td>
+ <code class="option">OS</code>
+ </td><td>
+ Includes the product name, the minimal version of the server, and the type of
the operating system it is running on (for example, <code
class="literal">Red Hat</code>).
+ </td></tr><tr><td>
+ <code class="option">Full</code>
+ </td><td>
+ Includes all the information above along with the list of loaded modules.
+ </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>Example 12.63. Using the
ServerTokens directive</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="id652271"
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>Example 12.64. Using
the SuexecUserGroup directive</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="id652184"
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">
+ The <em
class="replaceable"><code>time</code></em> is specified in
seconds. The default option is <code class="literal">60</code>.
+ </div><div class="example"
id="example-apache-httpdconf-timeout"><h6>Example 12.65. Using the
Timeout directive</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="id652123" class="indexterm"></a>
+ <code class="option">TypesConfig</code>
</span></dt><dd><div class="para">
+ The <code class="option">TypesConfig</code> allows you to
specify the location of the MIME types configuration file. It takes the following form:
+ </div><pre class="programlisting">TypesConfig <em
class="replaceable"><code>path</code></em></pre><a
id="id652091" 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>Example 12.66. Using the
TypesConfig directive</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="id652021"
class="indexterm"></a>
+ <code class="option">UseCanonicalName</code>
</span></dt><dd><div class="para">
+ The <code class="option">UseCanonicalName</code> allows you
to specify the way the server refers to itself. It takes the following form:
+ </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">Table 12.19,
“Available UseCanonicalName options”</a>. The default option is <code
class="option">Off</code>.
+ </div><div class="table"
id="table-apache-httpdconf-usecanonicalname"><h6>Table 12.19. Available
UseCanonicalName options</h6><div class="table-contents"><table
summary="Available UseCanonicalName options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables the use of the name that is specified by the <code
class="option">ServerName</code> directive.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ 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>
+ <code class="option">DNS</code>
+ </td><td>
+ 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>Example 12.67. Using
the UseCanonicalName directive</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="id651875"
class="indexterm"></a>
+ <code class="option">User</code>
</span></dt><dd><div class="para">
+ The <code class="option">User</code> directive allows you to
specify the user under which the <code
class="systemitem">httpd</code> service will run. It takes the
following form:
+ </div><pre class="programlisting">User <em
class="replaceable"><code>user</code></em></pre><div
class="para">
+ The <em
class="replaceable"><code>user</code></em> has to be an
existing UNIX user. The default option is <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>Example 12.68. Using the User
directive</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="id651786" class="indexterm"></a>
+ <code class="option">UserDir</code>
</span></dt><dd><div class="para">
+ The <code class="option">UserDir</code> directive allows you
to enable serving content from users' home directories. It takes the following form:
+ </div><pre class="programlisting">UserDir <em
class="replaceable"><code>option</code></em></pre><a
id="id651741" 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">Table 12.20,
“Available UserDir options”</a>. The default option is <code
class="option">disabled</code>.
+ </div><div class="table"
id="table-apache-httpdconf-userdir"><h6>Table 12.20. Available UserDir
options</h6><div class="table-contents"><table
summary="Available UserDir options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">enabled</code> <em
class="replaceable"><code>user</code></em>…
+ </td><td>
+ Enables serving content from home directories of given <em
class="replaceable"><code>user</code></em>s.
+ </td></tr><tr><td>
+ <code class="option">disabled</code> [<span
class="optional"><em
class="replaceable"><code>user</code></em>…</span>]
+ </td><td>
+ 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>Set the correct
permissions</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>Example 12.69. Using the
UserDir directive</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"
id="s3-apache-sslconf-common">12.1.5.2. Common ssl.conf
Directives</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="id651546"
class="indexterm"></a><div class="para">
+ The following directive is commonly used in <code
class="filename">/etc/httpd/conf.d/ssl.conf</code>:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id651518" 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">Table 12.21,
“Available SetEnvIf options”</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>Table 12.21. Available SetEnvIf
options</h6><div class="table-contents"><table
summary="Available SetEnvIf options"
border="1"><colgroup><col width="25%"
class="option" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Remote_Host</code>
+ </td><td>
+ Refers to the client's hostname.
+ </td></tr><tr><td>
+ <code class="option">Remote_Addr</code>
+ </td><td>
+ Refers to the client's IP address.
+ </td></tr><tr><td>
+ <code class="option">Server_Addr</code>
+ </td><td>
+ Refers to the server's IP address.
+ </td></tr><tr><td>
+ <code class="option">Request_Method</code>
+ </td><td>
+ Refers to the request method (for example, <code
class="literal">GET</code>).
+ </td></tr><tr><td>
+ <code class="option">Request_Protocol</code>
+ </td><td>
+ Refers to the protocol name and version (for example, <code
class="literal">HTTP/1.1</code>).
+ </td></tr><tr><td>
+ <code class="option">Request_URI</code>
+ </td><td>
+ Refers to the requested resource.
+ </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>Example 12.70. Using the
SetEnvIf directive</h6><div class="example-contents"><pre
class="programlisting">SetEnvIf User-Agent ".*MSIE.*" \
+ nokeepalive ssl-unclean-shutdown \
+ downgrade-1.0 force-response-1.0</pre></div></div><br
class="example-break" /></dd></dl></div><div
class="para">
+ Note that for the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> file to be present,
the <span class="package">mod_ssl</span> needs to be installed.
Refer to <a class="xref"
href="ch-Web_Servers.html#s2-apache-mod_ssl">Section 12.1.8, “Setting Up an
SSL Server”</a> for more information on how to install and configure an SSL server.
+ </div></div><div class="section"
id="s3-apache-mpm-common"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-mpm-common">12.1.5.3. Common Multi-Processing Module
Directives</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="id651254"
class="indexterm"></a><div class="para">
+ The following MPM directives are commonly used in <code
class="filename">/etc/httpd/conf/httpd.conf</code>:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id651229" 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>Example 12.71. Using the
MaxClients directive</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="id651013"
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>Example 12.72. Using
the MaxRequestsPerChild directive</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="id651096"
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">
+ This directive is used by the <code
class="systemitem">prefork</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-maxspareservers"><h6>Example 12.73. Using the
MaxSpareServers directive</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="id651025"
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>Example 12.74. Using the
MaxSpareThreads directive</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="id650937"
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>Example 12.75. Using the
MinSpareServers directive</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="id650886"
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">
+ This directive is used by the <code
class="systemitem">worker</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-minsparethreads"><h6>Example 12.76. Using the
MinSpareThreads directive</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="id650825"
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>Example 12.77. Using the
StartServers directive</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="id650772"
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">
+ This directive is used by the <code
class="systemitem">worker</code> MPM only.
+ </div><div class="example"
id="example-apache-mpm-threadsperchild"><h6>Example 12.78. Using the
ThreadsPerChild directive</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"
id="s2-apache-dso">12.1.6. Working with
Modules</h3></div></div></div><a id="id650702"
class="indexterm"></a><a id="id650686"
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"
id="s3-apache-dso-loading">12.1.6.1. Loading a
Module</h4></div></div></div><a id="id650637"
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">Section 12.1.5.1,
“Common httpd.conf Directives”</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>Example 12.79. Loading the 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">Section 12.1.4.3,
“Restarting the Service”</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"
id="s3-apache-dso-writing">12.1.6.2. Writing a
Module</h4></div></div></div><a id="id650576"
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"
id="s2-apache-virtualhosts">12.1.7. Setting Up Virtual
Hosts</h3></div></div></div><a id="id650519"
class="indexterm"></a><a id="id650507"
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">Example 12.80,
“Sample virtual host configuration”</a>.
+ </div><div class="example"
id="example-apache-virtualhosts-config"><h6>Example 12.80. Sample
virtual host configuration</h6><div class="example-contents"><pre
class="programlisting">NameVirtualHost penguin.example.com:80
+
+<VirtualHost penguin.example.com:80>
+ ServerAdmin webmaster(a)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>Changing the port
number</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">Section 12.1.4.3,
“Restarting the Service”</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"
id="s2-apache-mod_ssl">12.1.8. Setting Up an SSL
Server</h3></div></div></div><a id="id650392"
class="indexterm"></a><a id="id650368"
class="indexterm"></a><a id="id650361"
class="indexterm"></a><a id="id650352"
class="indexterm"></a><a id="id650339"
class="indexterm"></a><a id="id650322"
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"
id="s3-apache-mod_ssl-certificates">12.1.8.1. An Overview of Certificates and
Security</h4></div></div></div><a id="id650190"
class="indexterm"></a><a id="id650248"
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="id650217"
class="indexterm"></a><a id="id650203"
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">Table 12.22,
“CA lists for most common web browsers”</a>.
+ </div><div class="table"
id="table-apache-mod_ssl-certificates-authorities"><h6>Table 12.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>
+ Web Browser
+ </th><th>
+ Link
+ </th></tr></thead><tbody><tr><td>
+ <span class="application"><strong>Mozilla
Firefox</strong></span>
+ </td><td>
+ <a
href="http://www.mozilla.org/projects/security/certs/included/"... root
CA list</a>.
+ </td></tr><tr><td>
+ <span
class="application"><strong>Opera</strong></span>
+ </td><td>
+ <a
href="http://my.opera.com/rootstore/blog/">The Opera
Rootstore</a>.
+ </td></tr><tr><td>
+ <span class="application"><strong>Internet
Explorer</strong></span>
+ </td><td>
+ <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"
id="s3-apache-mod_ssl-enabling">12.1.8.2. Enabling the mod_ssl
Module</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="id650035" 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">Section 12.1.4.3,
“Restarting the Service”</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"
id="s3-apache-mod_ssl-keypair">12.1.8.3. Using an Existing Key and
Certificate</h4></div></div></div><a id="id649991"
class="indexterm"></a><a id="id649962"
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">
+ Certificates are issued for a particular IP address and domain name pair. If one of
these values changes, the certificate becomes invalid.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="emphasis"><em>You have a certificate from
VeriSign, and you are changing the server software.</em></span>
+ </div><div class="para">
+ VeriSign, a widely used certificate authority, issues certificates for a particular
software product, IP address, and domain name. Changing the software product renders the
certificate invalid.
+ </div></li></ol></div><div class="para">
+ In either of the above cases, you will need to obtain a new certificate. For more
information on this topic, refer to <a class="xref"
href="ch-Web_Servers.html#s3-apache-mod_ssl-genkey">Section 12.1.8.4,
“Generating a New Key and Certificate”</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">
+ Then add the following lines to the <code
class="filename">/etc/httpd/conf.d/ssl.conf</code> configuration file:
+ </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">
+ To load the updated configuration, restart the <code
class="systemitem">httpd</code> service as described in <a
class="xref"
href="ch-Web_Servers.html#s3-apache-running-restarting">Section 12.1.4.3,
“Restarting the Service”</a>.
+ </div><div class="example"
id="example-apache-mod_ssl-keypair"><h6>Example 12.81. Using a key and
certificate from the Red Hat Secure Web Server</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">mv /etc/httpd/conf/httpsd.key
/etc/pki/tls/private/penguin.example.com.key</code>
+~]# <code class="command">mv /etc/httpd/conf/httpsd.crt
/etc/pki/tls/certs/penguin.example.com.crt</code></pre></div></div><br
class="example-break" /></div><div class="section"
id="s3-apache-mod_ssl-genkey"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-mod_ssl-genkey">12.1.8.4. Generating a New Key and
Certificate</h4></div></div></div><a id="id649804"
class="indexterm"></a><a id="id649789"
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>Replacing an existing
certificate</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>Remove
a previously created key</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">
+ To run the utility, as <code class="systemitem">root</code>,
run the <code class="command">genkey</code> command followed by the
appropriate hostname (for example, <code
class="systemitem">penguin.example.com</code>):
+ </div><pre class="screen"><code
class="command">genkey</code> <em
class="replaceable"><code>hostname</code></em></pre><div
class="para">
+ To complete the key and certificate creation, take the following steps:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Review the target locations in which the key and certificate will be stored.
+ </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="Running the genkey
utility" /><div class="longdesc"><div
class="para">
+ Running the <span
class="application"><strong>genkey</strong></span> utility
+ </div></div></div></div><h6>Figure 12.1. Running
the genkey utility</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 proceed to
the next screen.
+ </div></li><li class="step"><div
class="para">
+ Using the <span
class="keycap"><strong>Up</strong></span> and <span
class="keycap"><strong>down</strong></span> arrow keys,
select the suitable key size. Note that while the large key increases the security, it
also increases the response time of your server. Because of this, the recommended option
is <code class="literal">1024 bits</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="Selecting the key size"
/><div class="longdesc"><div class="para">
+ Selecting the key size
+ </div></div></div></div><h6>Figure 12.2. Selecting
the key size</h6></div><br class="figure-break" /><div
class="para">
+ Once finished, 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 initiate
the random bits generation process. Depending on the selected key size, this may take some
time.
+ </div></li><li class="step"><div
class="para">
+ Decide whether you wish to send a certificate request to a certificate authority.
+ </div><div class="figure"
id="figure-apache-mod_ssl-genkey-03"><div
class="figure-contents"><div class="mediaobject"><img
src="images/apache-mod_ssl-genkey-03.png" alt="Generating a certificate
request" /><div class="longdesc"><div
class="para">
+ Generating a certificate request
+ </div></div></div></div><h6>Figure 12.3. Generating
a certificate request</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>Figure 12.4. Encrypting
the private key</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 proceed to
the next screen.
+ </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>Figure 12.5. Entering a
passphrase</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 proceed to
the next screen.
+ </div><div class="important"><div
class="admonition_header"><h2>Do not forget the
passphrase</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="Specifying certificate
information" /><div class="longdesc"><div
class="para">
+ Specifying certificate information
+ </div></div></div></div><h6>Figure 12.6. Specifying
certificate information</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>Figure 12.7. Instructions
on how to send a certificate request</h6></div><br
class="figure-break" /><div class="para">
+ Press <span
class="keycap"><strong>Enter</strong></span> to return to a
shell prompt.
+ </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">
+ Finally, restart the <code class="systemitem">httpd</code>
service as described in <a class="xref"
href="ch-Web_Servers.html#s3-apache-running-restarting">Section 12.1.4.3,
“Restarting the Service”</a>, so that the updated configuration is loaded.
+ </div></div></div><div class="section"
id="s2-apache-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-apache-resources">12.1.9. Additional
Resources</h3></div></div></div><div
class="para">
+ To learn more about the Apache HTTP Server, refer to the following resources.
+ </div><div class="section"
id="s3-apache-resources-installed"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-apache-resources-installed">12.1.9.1. Installed
Documentation</h4></div></div></div><a id="id590061"
class="indexterm"></a><div
class="variablelist"><dl><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">
+ The manual page for the <code
class="systemitem">httpd</code> service containing the complete list of
its command line options.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
genkey</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">genkey</code>
containing the full documentation on its usage.
+ </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"
id="s3-apache-resources-web">12.1.9.2. Useful
Websites</h4></div></div></div><a id="id594460"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://httpd.apache.org/">http://httpd.apache.org/<...
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&g...
class="para">
+ The official website for the <span
class="application"><strong>mod_ssl</strong></span>
module.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.openssl.org/">http://www.openssl.org/</a...
class="para">
+ The OpenSSL home page containing further documentation, frequently asked
questions, links to the mailing lists, and other useful resources.
+ </div></dd></dl></div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-bind-additional-resources.html"><strong>Prev</strong>11.2.7. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Mail_Servers.html"><strong>Next</strong>Chapter 13. Mail
Servers</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Working_with_Kernel_Modules.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Working_with_Kernel_Modules.html
new file mode 100644
index 0000000..06f7986
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-Working_with_Kernel_Modules.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>Chapter 21. 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="Part VII. Kernel, Module and Driver Configuration" /><link
rel="prev" href="s2-kernel-boot-loader-pseries.html"
title="20.6.3. Configuring the YABOOT Boot Loader" /><link
rel="next" href="sec-Displaying_Information_About_a_Module.html"
title="21.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Displaying_Information_About_a_Module.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter"
id="ch-Working_with_Kernel_Modules" lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 21. 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">21.1.
Listing Currently-Loaded Modules</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Information_About_a_Module.html">21.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="sec-Loading_a_Module.html">21.3.
Loading a Module</a></span></dt><dt><span
class="section"><a href="sec-Unloading_a_Module.html">21.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a href="sec-Settin
g_Module_Parameters.html">21.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="sec-Persistent_Module_Loading.html">21.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="sec-Specific_Kernel_Module_Capabilities.html">21.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">21.7.1.
Using Multiple Ethernet Cards</a></span></dt><dt><span
class="section"><a
href="sec-Using_Channel_Bonding.html">21.7.2. Using Channel
Bonding</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html">21.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html#s2-kernel-modules-additional-resources-installed">21.8.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="s2-kernel-modules-add
itional-resources-websites.html">21.8.2. Useful
Websites</a></span></dt></dl></dd></dl></div><a
id="id505240" class="indexterm"></a><a
id="id642388" class="indexterm"></a><a
id="id635717" 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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="section"
id="sec-Listing_Currently-Loaded_Modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-Listing_Currently-Loaded_Modules">21.1. Listing Currently-Loaded
Modules</h2></div></div></div><a id="id676829"
class="indexterm"></a><a id="id484378"
class="indexterm"></a><a id="id590152"
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">[output
truncated]</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">Section 21.4, “Unloading a
Module”</a>.
+ </div></li></ul></div><a id="id461153"
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>Prev</strong>20.6.3. Configuring
the YABOOT Boot Loader</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Displaying_Information_About_a_Module.html"><strong>Next</strong>21.2. Displaying
Information About a Module</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-abrt.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-abrt.html
new file mode 100644
index 0000000..b331dfa
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-abrt.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>Chapter 19. Automatic Bug-Reporting Tool (ABRT)</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Monitoring_and_Automation.html" title="Part VI. Monitoring and
Automation" /><link rel="prev"
href="s1-autotasks-additional-resources.html" title="18.3. Additional
Resources" /><link rel="next" href="ch19s02.html"
title="19.2. Installing and Running ABRT" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-autotasks-additional-resources.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n"
href="ch19s02.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-abrt"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 19. Automatic Bug-Reporting Tool
(ABRT)</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-abrt.html#id443090">19.1.
Overview</a></span></dt><dt><span
class="section"><a href="ch19s02.html">19.2. Installing and
Running ABRT</a></span></dt><dt><span
class="section"><a href="abrt-plugins.html">19.3. ABRT
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a
href="abrt-plugins.html#analyzer-plugins">19.3.1. Analyzer
Plugins</a></span></dt><dt><span
class="section"><a href="reporter-plugins.html">19.3.2.
Reporter Plugins</a></span></dt><dt><span
class="section"><a
href="configuring-plugins-in-the-gui.html">19.3.3. Plugin Configuration in
the GUI</a></span></dt></dl></dd><dt><span
class="section"><a href="generating-backtrac
e.html">19.4. Generating
Backtraces</a></span></dt><dd><dl><dt><span
class="section"><a
href="generating-backtrace.html#troubleshooting">19.4.1. Troubleshooting
Backtrace
Generation</a></span></dt></dl></dd><dt><span
class="section"><a href="ch19s05.html">19.5. Using the
Command Line
Interface</a></span></dt><dd><dl><dt><span
class="section"><a href="ch19s05.html#id483939">19.5.1.
Viewing Crashes</a></span></dt><dt><span
class="section"><a href="ch19s05s02.html">19.5.2. Reporting
Crashes</a></span></dt><dt><span
class="section"><a href="ch19s05s03.html">19.5.3. Deleting
Crashes</a></span></dt></dl></dd><dt><span
class="section"><a href="configuring.html">19.6. Configuring
ABRT</a></span></dt><dt><span
class="section"><a
href="configuring-centralized-crash-collection.html">19.7. Configuring
Centralized Crash
Collection</a></span></dt><dd><dl><dt><span
class="section"><a
href="configuring-centralized-crash-collection.html#id462013">19.7.1. Testing
ABRT's Crash Detection</a></s
pan></dt><dt><span class="section"><a
href="testing-upload-method.html">19.7.2. Testing the Upload
Method</a></span></dt></dl></dd><dt><span
class="section"><a
href="configuring-automatic-reporting.html">19.8. Configuring Automatic
Reporting</a></span></dt></dl></div><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="id443090">19.1. Overview</h2></div></div></div><div
class="para">
+ <span
class="application"><strong>ABRT</strong></span> is the
<span class="application"><strong>Automatic Bug-Reporting
Tool</strong></span>. <span
class="application"><strong>ABRT</strong></span> consists
of a daemon that runs silently in the background most of the time. It springs into action
when an application crashes. It then collects the relevant crash data such as a core file
if there is one, the crashing application's command line parameters, and other
contextual puzzle pieces of forensic utility. Finally, <span
class="application"><strong>ABRT</strong></span> is capable
of reporting crash data to a relevant issue tracker, such as Red Hat Bugzilla. Reporting
crash data to a relevant issue tracker can be configured to happen automatically at every
detected crash, or crash dumps can be stored locally, reviewed, reported, and deleted
manually by a user. <span
class="application"><strong>ABRT</strong></span>'s
various plugins analyze crash data from applications writ
ten in the C, C++ and Python language, as well as report crashes to relevant issue
trackers.
+ </div><div class="para">
+ The <span
class="application"><strong>ABRT</strong></span> package
consists of:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="systemitem">abrtd</code>, the system service
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="application"><strong>abrt-applet</strong></span>,
which runs in the user's Notification Area
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="application"><strong>abrt-gui</strong></span>, the
GUI application that shows collected crash dumps and allows you to edit, report, and
delete them
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="application"><strong>abrt-cli</strong></span>, the
command line interface with functionality similar to <span
class="application"><strong>abrt-gui</strong></span>.
+ </div></li></ul></div><div class="para">
+ You can open the <span
class="application"><strong>ABRT</strong></span> GUI
application by selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>Automatic Bug Reporting
Tool</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu.
+ </div><div class="figure"
id="fig-ABRT-Main_Window"><div
class="figure-contents"><div class="mediaobject"
align="center"><img src="images/abrt.png"
align="middle" alt="The Automatic Bug Reporting Tool main window"
/><div class="longdesc"><div class="para">
+ The Automatic Bug Reporting Tool main window
+ </div></div></div></div><h6>Figure 19.1. The Automatic
Bug Reporting Tool main window</h6></div><br class="figure-break"
/><div class="para">
+ A number of additional packages can be installed to provide <span
class="application"><strong>ABRT</strong></span> plugins
and addons. To view all the available <span
class="application"><strong>ABRT</strong></span> packages,
type the following command:
+ </div><pre class="screen"><code
class="command">yum list all | grep
abrt</code></pre></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-autotasks-additional-resources.html"><strong>Prev</strong>18.3. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch19s02.html"><strong>Next</strong>19.2. Installing and
Running ABRT</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-kdump.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-kdump.html
new file mode 100644
index 0000000..c011cd7
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-kdump.html
@@ -0,0 +1,230 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Chapter 22. 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="Part VII. Kernel, Module and Driver Configuration" /><link
rel="prev" href="s2-kernel-modules-additional-resources-websites.html"
title="21.8.2. Useful Websites" /><link rel="next"
href="s1-kdump-crash.html" title="22.2. 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-kernel-modules-a
dditional-resources-websites.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kdump-crash.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-kdump"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 22. The kdump Crash Recovery
Service</h2></div></div></div><div
class="toc"><dl><dt><span class="section"><a
href="ch-kdump.html#s1-kdump-configuration">22.1. Configuring the kdump
Service</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-gui">22.1.1. Using the Kernel Dump
Configuration Utility</a></span></dt><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-cli">22.1.2. Configuring kdump on
the Command Line</a></span></dt><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-testing">22.1.3. Testing the
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-kdump-crash.html">22.2. Analyz
ing the Core Dump</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kdump-crash.html#s2-kdump-crash-running">22.2.1. Running the crash
Utility</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-log.html">22.2.2.
Displaying the Message Buffer</a></span></dt><dt><span
class="section"><a
href="s2-kdump-crash-backtrace.html">22.2.3. Displaying a
Backtrace</a></span></dt><dt><span
class="section"><a
href="s2-kdump-crash-processes.html">22.2.4. Displaying a Process
Status</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-memory.html">22.2.5.
Displaying Virtual Memory Information</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-files.html">22.2.6.
Displaying Open Files</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-exit.html">22.2.7.
Exiting the
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-kdump-resources.html">22.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="sectio
n"><a
href="s1-kdump-resources.html#s2-kdump-resources-installed">22.3.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="s2-kdump-resources-online.html">22.3.2. Useful
Websites</a></span></dt></dl></dd></dl></div><div
class="para">
+ <code class="systemitem">kdump</code> is an advanced crash
dumping mechanism. When 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. Since being able to analyze the core dump
helps significantly to determine the exact cause of the system failure, it is strongly
recommended to have this feature enabled.
+ </div><div class="para">
+ 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-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kdump-configuration">22.1. Configuring the kdump
Service</h2></div></div></div><div class="para">
+ This section covers two common means of configuring the <code
class="systemitem">kdump</code> service: using the <span
class="application"><strong>Kernel Dump
Configuration</strong></span> graphical utility, and doing so manually on the
command line. It also describes how to test the configuration to verify that everything
works as expected.
+ </div><a id="id566401"
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="note"><div
class="admonition_header"><h2>Make sure you have relevant packages
installed</h2></div><div class="admonition"><div
class="para">
+ To use the <code class="systemitem">kdump</code> service, you
must have the <span class="package">kexec-tools</span> and <span
class="package">system-config-kdump</span> 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 kexec-tools
system-config-kdump</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">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="section"
id="s2-kdump-configuration-gui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-kdump-configuration-gui">22.1.1. Using the Kernel Dump Configuration
Utility</h3></div></div></div><a id="id571109"
class="indexterm"></a><a id="id444144"
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="ch-kdump.html#fig-kdump-kernel_dump_configuration">Figure 22.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, the utility will not start, and you will be
presented with the following error message:
+ </div><div class="mediaobject" align="center"><img
src="images/kdump-kernel_dump_configuration-not_enough_memory.png"
align="middle" /><div class="longdesc"><div
class="para">
+ The <span class="quote">“<span class="quote">not
enough memory</span>”</span> error
+ </div></div></div><div class="para">
+ For the information on minimum memory requirements, refer to the <em
class="citetitle">Hardware Overview</em> section of the <a
href="http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Not...
class="citetitle">Fedora 15 Release Notes</em></a>. Note that
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 a user, and defaults to 128MB.
+ </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"
id="s3-kdump-configuration-gui-enable">22.1.1.1. Enabling the
Service</h4></div></div></div><a id="id624629"
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 for runlevels <code
class="literal">2</code>, <code
class="literal">3</code>, <code
class="literal">4</code>, and <code
class="literal">5</code>, and start it for the current session.
Similarly, clicking the <span
class="guibutton"><strong>Disable</strong></span> button
will disable it for all runlevels and stop the service immediately.
+ </div><div class="para">
+ For more information on runlevels and configuring services in general, refer to
<a class="xref" href="ch-Services_and_Daemons.html">Chapter 7,
<em>Services and Daemons</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"
id="s3-kdump-configuration-gui-basic">22.1.1.2. The Basic Settings
Tab</h4></div></div></div><a id="id446660"
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>Figure 22.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"
id="s3-kdump-configuration-gui-target">22.1.1.3. The Target Settings
Tab</h4></div></div></div><a id="id563308"
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>Figure 22.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">Chapter 9, <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="id571007"
class="indexterm"></a><div class="para">
+ For a complete list of currently supported targets, see <a class="xref"
href="ch-kdump.html#tab-kdump-supported_targets">Table 22.1, “Supported kdump
targets”</a>.
+ </div><div class="table"
id="tab-kdump-supported_targets"><h6>Table 22.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>
+ Type
+ </th><th>
+ Supported Targets
+ </th><th>
+ Unsupported Targets
+ </th></tr></thead><tbody><tr><td
valign="middle">
+ Raw device
+ </td><td>
+ All locally attached raw disks and partitions.
+ </td><td>
+ —
+ </td></tr><tr><td valign="middle">
+ Local file system
+ </td><td>
+ <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>
+ The <code class="systemitem">eCryptfs</code> file system.
+ </td></tr><tr><td rowspan="7"
valign="middle">
+ Remote directory
+ </td><td>
+ 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>
+ Remote directories on the <code
class="systemitem">rootfs</code> file system accessed using the
<code class="systemitem">NFS</code> protocol.
+ </td></tr><tr><td>
+ Remote directories accessed using the <code
class="systemitem">iSCSI</code> protocol over hardware initiators.
+ </td><td>
+ Remote directories accessed using the <code
class="systemitem">iSCSI</code> protocol over software initiators.
+ </td></tr><tr><td rowspan="5">
+ —
+ </td><td>
+ Remote directories accessed over <code
class="systemitem">IPv6</code>.
+ </td></tr><tr><td>
+ Remote directories accessed using the <code
class="systemitem">SMB</code>/<code
class="systemitem">CIFS</code> protocol.
+ </td></tr><tr><td>
+ Remote directories accessed using the <code
class="systemitem">FCoE</code> (<em
class="firstterm">Fibre Channel over Ethernet</em>) protocol.
+ </td></tr><tr><td>
+ Remote directories accessed using wireless network interfaces.
+ </td></tr><tr><td>
+ Multipath-based storages.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="id612317"
class="indexterm"></a><div class="important"><div
class="admonition_header"><h2>Using the hpsa driver for a
storage</h2></div><div class="admonition"><div
class="para">
+ Due to known issue with the <code
class="systemitem">hpsa</code> driver, <code
class="systemitem">kdump</code> is unable to save the dump to a storage
that uses this driver for HP Smart Array Controllers. If this applies to your machine, it
is advised that you save the dump to a remote system using the NFS or SSH protocol
instead.
+ </div></div></div></div><div class="section"
id="s3-kdump-configuration-gui-filtering"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-kdump-configuration-gui-filtering">22.1.1.4. The Filtering Settings
Tab</h4></div></div></div><a id="id442894"
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>Figure 22.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 check box 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"
id="s3-kdump-configuration-gui-expert">22.1.1.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>Figure 22.4. Expert
Settings</h6></div><br class="figure-break" /><a
id="id612109" 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="id605823"
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="id427773"
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="id642308"
class="indexterm"></a><div class="para">
+ To choose what steps should be taken when the kernel crash is captured, select the
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="id420732"
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="ch-kdump.html#s3-kdump-configuration-cli-filtering">Section 22.1.2.3,
“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"
id="s2-kdump-configuration-cli">22.1.2. Configuring kdump on the Command
Line</h3></div></div></div><div class="para">
+ To perform actions described in this section, you have to be logged in as <code
class="systemitem">root</code>. To do so, run the following command:
+ </div><pre class="screen"><code
class="command">su -</code></pre><div
class="section" id="s3-kdump-configuration-cli-memory"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-kdump-configuration-cli-memory">22.1.2.1. Configuring the Memory
Usage</h4></div></div></div><a id="id507237"
class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code
class="systemitem">kdump</code> kernel, open the <code
class="filename">/boot/grub/grub.conf</code> file in a text editor such
as <span class="application"><strong>vi</strong></span>
or <span
class="application"><strong>nano</strong></span>, and add
the <code class="option">crashkernel=<em
class="replaceable"><code><size></code></em>M</code>
parameter to the list of kernel options as shown in <a class="xref"
href="ch-kdump.html#ex-kdump-configuration-cli-memory-grub">Example 22.1, “A
sample /boot/grub/grub.conf file”</a>.
+ </div><a id="id555630"
class="indexterm"></a><a id="id555650"
class="indexterm"></a><a id="id478181"
class="indexterm"></a><div class="example"
id="ex-kdump-configuration-cli-memory-grub"><h6>Example 22.1. A sample
/boot/grub/grub.conf file</h6><div class="example-contents"><pre
class="screen"># grub.conf generated by anaconda
+#
+# Note that you do not have to rerun grub after making changes to this file
+# NOTICE: You have a /boot partition. This means that
+# all kernel and initrd paths are relative to /boot/, eg.
+# root (hd0,0)
+# kernel /vmlinuz-version ro root=/dev/sda3
+# initrd /initrd
+#boot=/dev/sda
+default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux (2.6.32-54.el6.i686)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.32-54.el6.i686 root=/dev/sda3 ro crashkernel=128M
+ initrd /initramfs-2.6.32-54.el6.i686.img
+</pre></div></div><br class="example-break" /><div
class="important"><div
class="admonition_header"><h2>Make sure the system has enough
memory</h2></div><div class="admonition"><div
class="para">
+ 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 a user, and defaults to 128 MB, as lower values proved to
be unreliable. For the information on minimum memory requirements, refer to the <em
class="citetitle">Hardware Overview</em> section of the <a
href="http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Not...
class="citetitle">Fedora 15 Release Notes</em></a>.
+ </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"
id="s3-kdump-configuration-cli-target">22.1.2.2. Configuring the Target
Type</h4></div></div></div><a id="id560296"
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. Note that only one of these options
can be set at the moment. 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, open the <code
class="filename">/etc/kdump.conf</code> configuration file in a text
editor such as <span
class="application"><strong>vi</strong></span> or <span
class="application"><strong>nano</strong></span>, and 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="screen">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="screen">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="screen">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(a)my.server.com</code> line, and
replace the value with a valid username and hostname. For example:
+ </div><pre class="screen">net
john(a)penguin.example.com</pre><div class="para">
+ Refer to <a class="xref" href="ch-OpenSSH.html">Chapter 9,
<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="id558603"
class="indexterm"></a><div class="para">
+ For a complete list of currently supported targets, see <a class="xref"
href="ch-kdump.html#tab-kdump-supported_targets">Table 22.1, “Supported kdump
targets”</a>.
+ </div><a id="id668414"
class="indexterm"></a><div class="important"><div
class="admonition_header"><h2>Using the hpsa driver for a
storage</h2></div><div class="admonition"><div
class="para">
+ Due to known issue with the <code
class="systemitem">hpsa</code> driver, <code
class="systemitem">kdump</code> is unable to save the dump to a storage
that uses this driver for HP Smart Array Controllers. If this applies to your machine, it
is advised that you save the dump to a remote system using the NFS or SSH protocol
instead.
+ </div></div></div></div><div class="section"
id="s3-kdump-configuration-cli-filtering"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-kdump-configuration-cli-filtering">22.1.2.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, open the <code
class="filename">/etc/kdump.conf</code> configuration file in a text
editor such as <span
class="application"><strong>vi</strong></span> or <span
class="application"><strong>nano</strong></span>, 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="id460407"
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="screen">core_collector makedumpfile
-c</pre><a id="id605910"
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="ch-kdump.html#table-kdump-configuration-cli-filtering-makedumpfile">Table 22.2,
“Supported filtering levels”</a>. For example, to remove both zero and free pages,
use the following:
+ </div><pre class="screen">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>Table 22.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>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">1</code>
+ </td><td>
+ Zero pages
+ </td></tr><tr><td>
+ <code class="option">2</code>
+ </td><td>
+ Cache pages
+ </td></tr><tr><td>
+ <code class="option">4</code>
+ </td><td>
+ Cache private
+ </td></tr><tr><td>
+ <code class="option">8</code>
+ </td><td>
+ User pages
+ </td></tr><tr><td>
+ <code class="option">16</code>
+ </td><td>
+ 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"
id="s3-kdump-configuration-cli-action">22.1.2.4. Changing the Default
Action</h4></div></div></div><a id="id591408"
class="indexterm"></a><div class="para">
+ By default, when the kernel crash is captured, the root file system is mounted, and
<code class="command">/sbin/init</code> is run. To change this
behavior, open the <code class="filename">/etc/kdump.conf</code>
configuration file in a text editor such as <span
class="application"><strong>vi</strong></span> or <span
class="application"><strong>nano</strong></span>, 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="ch-kdump.html#table-kdump-configuration-cli-action-actions">Table 22.3,
“Supported actions”</a>. For example:
+ </div><pre class="screen">default halt</pre><div
class="table"
id="table-kdump-configuration-cli-action-actions"><h6>Table 22.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>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">reboot</code>
+ </td><td>
+ Reboot the system, losing the core in the process.
+ </td></tr><tr><td>
+ <code class="option">halt</code>
+ </td><td>
+ After attempting to capture a core, halt the system no matter if it succeeded.
+ </td></tr><tr><td>
+ <code class="option">poweroff</code>
+ </td><td>
+ Power off the system.
+ </td></tr><tr><td>
+ <code class="option">shell</code>
+ </td><td>
+ 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><div class="section"
id="s3-kdump-configuration-cli-enable"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-kdump-configuration-cli-enable">22.1.2.5. Enabling the
Service</h4></div></div></div><a id="id575192"
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:
+ </div><pre class="screen"><code
class="command">systemctl enable
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:
+ </div><a id="id508372"
class="indexterm"></a><pre class="screen"><code
class="command">systemctl start kdump.service</code></pre><div
class="para">
+ For more information on runlevels and configuring services in general, refer to
<a class="xref" href="ch-Services_and_Daemons.html">Chapter 7,
<em>Services and Daemons</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"
id="s2-kdump-configuration-testing">22.1.3. Testing the
Configuration</h3></div></div></div><a id="id594716"
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">Section 7.2, “Running Services”</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 class="example"
id="ex-kdump-configuration-testing-vmcore"><h6>Example 22.2. Listing a
content of /var/crash/ after a crash</h6><div
class="example-contents"><pre class="screen">~]# <code
class="command">tree --charset=ascii /var/crash</code>
+/var/crash
+`-- 127.0.0.1-2010-08-25-08:45:02
+ `-- vmcore
+
+1 directory, 1 file</pre></div></div><br
class="example-break" /></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-kernel-modules-additional-resources-websites.html"><strong>Prev</strong>21.8.2. Useful
Websites</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kdump-crash.html"><strong>Next</strong>22.2. Analyzing
the Core Dump</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-proc.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-proc.html
new file mode 100644
index 0000000..a5c3b0c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-proc.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>Appendix C. 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="s1-sysconfig-additional-resources.html"
title="B.3. Additional Resources" /><link rel="next"
href="s1-proc-topfiles.html" title="C.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>Prev</strong></a></li><li
class="ne
xt"><a accesskey="n"
href="s1-proc-topfiles.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="appendix" id="ch-proc"
lang="en-US"><div
class="titlepage"><div><div><h1 class="title">The
proc File System</h1></div></div></div><a
id="id598816" class="indexterm"></a><a
id="id432664" 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"
id="s1-proc-virtual">C.1. A Virtual File
System</h2></div></div></div><a id="id599210"
class="indexterm"></a><a id="id463210"
class="indexterm"></a><a id="id421279"
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"
id="s2-proc-viewing">C.1.1. Viewing Virtual
Files</h3></div></div></div><a id="id561214"
class="indexterm"></a><a id="id561228"
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"
id="s2-proc-change">C.1.2. Changing Virtual
Files</h3></div></div></div><a id="id676922"
class="indexterm"></a><a id="id675756"
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">Section C.4, “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">Section C.3.9, “
/proc/sys/ ”</a>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-sysconfig-additional-resources.html"><strong>Prev</strong>B.3. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-proc-topfiles.html"><strong>Next</strong>C.2. Top-level
Files within the proc File
System</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-yum.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-yum.html
new file mode 100644
index 0000000..63c061b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch-yum.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>Chapter 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="part-Package_Management.html" title="Part II. Package
Management" /><link rel="prev"
href="part-Package_Management.html" title="Part II. Package
Management" /><link rel="next"
href="sec-Packages_and_Package_Groups.html" title="4.2. Packages and
Package Groups" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="part-Package_Management.html"><strong>Prev</strong></a></li>
<li class="next"><a accesskey="n"
href="sec-Packages_and_Package_Groups.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="chapter" id="ch-yum"
lang="en-US"><div
class="titlepage"><div><div><h2
class="title">Chapter 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. Checking For
and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-yum.html#sec-Checking_For_Updates">4.1.1. Checking For
Updates</a></span></dt><dt><span
class="section"><a
href="ch-yum.html#sec-Updating_Packages">4.1.2. Updating
Packages</a></span></dt><dt><span
class="section"><a
href="ch-yum.html#sec-Preserving_Configuration_File_Changes">4.1.3.
Preserving Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html">4.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="se
c-Packages_and_Package_Groups.html#sec-Searching_Packages">4.2.1. Searching
Packages</a></span></dt><dt><span
class="section"><a href="sec-Listing_Packages.html">4.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Package_Information.html">4.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="sec-Installing.html">4.2.4.
Installing Packages</a></span></dt><dt><span
class="section"><a href="sec-Removing.html">4.2.5. Removing
Packages</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Configuring_Yum_and_Yum_Repositories.html">4.3. Configuring Yum and
Yum Repositories</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.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="sec-Setting_repository_Options.html">4.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="
sec-Using_Yum_Variables.html">4.3.3. Using Yum
Variables</a></span></dt><dt><span
class="section"><a
href="sec-Creating_a_Yum_Repository.html">4.3.4. Creating a Yum
Repository</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Yum_Plugins.html">4.4. Yum
Plugins</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.
Enabling, Configuring and Disabling Yum
Plugins</a></span></dt><dt><span
class="section"><a
href="sec-Installing_More_Yum_Plugins.html">4.4.2. Installing Additional Yum
Plugins</a></span></dt><dt><span
class="section"><a href="sec-Plugin_Descriptions.html">4.4.3.
Plugin
Descriptions</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Additional_Resources.html">4.5.
Additional Resources</a></span></dt></dl></div><div
class="para">
+ <span class="application"><strong>Yum</strong></span>
is the The Fedora Project package manager that is able to query for information about
packages, fetch packages from repositories, install and uninstall packages using automatic
dependency resolution, and update an entire system to the latest available packages.
<span class="application"><strong>Yum</strong></span>
performs automatic dependency resolution on packages you are updating, installing or
removing, and thus is able to automatically determine, fetch and install all available
dependent packages. <span
class="application"><strong>Yum</strong></span> can be
configured with new, additional repositories, or <em
class="firstterm">package sources</em>, and also provides many plugins
which enhance and extend its capabilities. <span
class="application"><strong>Yum</strong></span> is able to
perform many of the same tasks that <span
class="application"><strong>RPM</strong></span> can;
additionally, many of the command lin
e options are similar. <span
class="application"><strong>Yum</strong></span> enables
easy and simple package management on a single machine or on groups of them.
+ </div><div class="important"
id="important-Secure_Package_Management_with_GPG-Signed_Packages"><div
class="admonition_header"><h2>Secure package management with GPG-signed
packages</h2></div><div class="admonition"><div
class="para">
+ <span
class="application"><strong>Yum</strong></span> provides
secure package management by enabling GPG (Gnu Privacy Guard; also known as GnuPG)
signature verification on GPG-signed packages to be turned on for all package repositories
(i.e. package sources), or for individual repositories. When signature verification is
enabled, <span
class="application"><strong>Yum</strong></span> will refuse
to install any packages not GPG-signed with the correct key for that repository. This
means that you can trust that the <span
class="application"><strong>RPM</strong></span> packages
you download and install on your system are from a trusted source, such as The Fedora
Project, and were not modified during transfer. Refer to <a class="xref"
href="sec-Configuring_Yum_and_Yum_Repositories.html">Section 4.3,
“Configuring Yum and Yum Repositories”</a> for details on enabling
signature-checking with <span
class="application"><strong>Yum</strong></span>, or <a
class="xref" href="s1-
check-rpm-sig.html">Section A.3, “Checking a Package's Signature”</a>
for information on working with and verifying GPG-signed <span
class="application"><strong>RPM</strong></span> packages in
general.
+ </div></div></div><div class="para">
+ <span class="application"><strong>Yum</strong></span>
also enables you to easily set up your own repositories of <span
class="application"><strong>RPM</strong></span> packages
for download and installation on other machines.
+ </div><div class="para">
+ Learning <span
class="application"><strong>Yum</strong></span> is a
worthwhile investment because it is often the fastest way to perform system administration
tasks, and it provides capabilities beyond those provided by the <span
class="application"><strong>PackageKit</strong></span>
graphical package management tools. Refer to <a class="xref"
href="ch-PackageKit.html">Chapter 5,
<em>PackageKit</em></a> for details on using <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="note"
id="note-Note_Yum_and_Superuser_Privileges"><div
class="admonition_header"><h2>Yum and superuser
privileges</h2></div><div class="admonition"><div
class="para">
+ You must have superuser privileges in order to use <code
class="command">yum</code> to install, update or remove packages on
your system. All examples in this chapter assume that you have already obtained superuser
privileges by using either the <code class="command">su</code> or
<code class="command">sudo</code> command.
+ </div></div></div><div class="section"
id="sec-Checking_For_and_Updating_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-Checking_For_and_Updating_Packages">4.1. Checking For and Updating
Packages</h2></div></div></div><div class="section"
id="sec-Checking_For_Updates"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Checking_For_Updates">4.1.1. Checking For
Updates</h3></div></div></div><a id="id480825"
class="indexterm"></a><div class="para">
+ You can use the <code class="command">yum check-update</code>
command to see which installed packages on your system have updates available:
+ </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">
+ The packages in the above output are listed as having updates available. The first
package in the list is <span
class="application"><strong>PackageKit</strong></span>, the
graphical package manager. The line in the example output tells us:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">PackageKit</code> — the name of
the package
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">x86_64</code> — the CPU
architecture the package was built for
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">0.6.14</code> — the version of
the updated package to be installed
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">fedora</code> — the repository
in which the updated package is located
+ </div></li></ul></div><div class="para">
+ The output also shows us that we can update the kernel (the <span
class="package">kernel</span> package), <span
class="application"><strong>Yum</strong></span> and
<span class="application"><strong>RPM</strong></span>
themselves (the <code class="filename">yum</code> and <code
class="filename">rpm</code> packages), as well as their dependencies
(such as the <span class="package">rpm-libs</span> and <span
class="package">rpm-python</span> packages), all using <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"
id="sec-Updating_Packages">4.1.2. Updating
Packages</h3></div></div></div><a id="id536622"
class="indexterm"></a><div class="para">
+ You can choose to update a single package, multiple packages, or all packages at
once. If any dependencies of the package (or packages) you update have updates available
themselves, then they are updated too.
+ </div><h4> Updating a Single Package </h4><a
id="id440597" class="indexterm"></a><div
class="para">
+ To update a single package, enter <code class="command">yum update
<em
class="replaceable"><code>package_name</code></em></code>,
for example:
+ </div><pre class="screen">~]# <code
class="command">yum update gdb</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+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">
+ This output contains several items of interest:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ <code class="computeroutput">Loaded plugins:</code> —
<code class="command">yum</code> always informs you which <span
class="application"><strong>Yum</strong></span> plugins are
installed and enabled. Here, <code class="command">yum</code> is
using the <span
class="application"><strong>langpacks</strong></span>,
<span
class="application"><strong>presto</strong></span>, and
<span
class="application"><strong>refresh-packagekit</strong></span>
plugins. Refer to <a class="xref"
href="sec-Yum_Plugins.html">Section 4.4, “Yum Plugins”</a> for general
information on <span
class="application"><strong>Yum</strong></span> plugins, or
to <a class="xref"
href="sec-Plugin_Descriptions.html">Section 4.4.3, “Plugin
Descriptions”</a> for descriptions of specific plugins.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">gdb.x86_64</code> — you can
download and install new <span class="package">gdb</span> package.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">yum</code> presents the update
information and then prompts you as to whether you want it to perform the update; <code
class="command">yum</code> runs interactively by default. If you
already know which transactions <code class="command">yum</code>
plans to perform, you can use the <code class="option">-y</code>
option to automatically answer <code class="command">yes</code> to
any questions <code class="command">yum</code> may ask (in which
case it runs non-interactively). However, you should always examine which changes <code
class="command">yum</code> plans to make to the system so that you can
easily troubleshoot any problems that might arise.
+ </div></li></ol></div><div class="para">
+ If a transaction does go awry, you can view <span
class="application"><strong>Yum</strong></span>'s log
of transactions by typing the <code class="command">cat
/var/log/yum.log</code> command at a shell prompt. The most recent transactions are
listed at the end of the log file.
+ </div><div class="important"
id="important-Important-Updating_and_Installing_Kernels_with_Yum"><div
class="admonition_header"><h2>Updating and installing kernels with
Yum</h2></div><div class="admonition"><div
class="para">
+ <code class="command">yum</code> always <span
class="emphasis"><em>installs</em></span> a new kernel in
the same sense that <span
class="application"><strong>RPM</strong></span> installs a
new kernel when you use the command <code class="command">rpm -i
kernel</code>. Therefore, you do not need to worry about the distinction between
<span class="emphasis"><em>installing</em></span> and
<span class="emphasis"><em>upgrading</em></span> a
kernel package when you use <code class="command">yum</code>: it
will do the right thing, regardless of whether you are using the <code
class="command">yum update</code> or <code
class="command">yum install</code> command.
+ </div><div class="para">
+ When using <span
class="application"><strong>RPM</strong></span>, on the
other hand, it is important to use the <code class="command">rpm -i
kernel</code> command (which installs a new kernel) instead of <code
class="command">rpm -u kernel</code> (which <span
class="emphasis"><em>replaces</em></span> the current
kernel). Refer to <a class="xref"
href="sec-Installing_and_Upgrading.html">Section A.2.2, “Installing and
Upgrading”</a> for more information on installing/updating kernels with <span
class="application"><strong>RPM</strong></span>.
+ </div></div></div><h4> Updating All Packages and Their
Dependencies </h4><a id="id420884"
class="indexterm"></a><div class="para">
+ To update all packages and their dependencies, simply enter the <code
class="command">yum update</code> command (without any arguments):
+ </div><pre class="screen">~]# <code
class="command">yum update</code></pre><h4> Updating
Security-Related Packages </h4><a id="id443599"
class="indexterm"></a><a id="id443611"
class="indexterm"></a><a id="id443622"
class="indexterm"></a><div class="para">
+ Discovering which packages have security updates available and then updating those
packages quickly and easily is important. <span
class="application"><strong>Yum</strong></span> provides
the plugin for this purpose. The <span
class="application"><strong>security</strong></span> plugin
extends the <code class="command">yum</code> command with a set of
highly-useful security-centric commands, subcommands and options. Refer to <a
class="xref" href="sec-Plugin_Descriptions.html">Section 4.4.3,
“Plugin Descriptions”</a> for specific information.
+ </div></div><div class="section"
id="sec-Preserving_Configuration_File_Changes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Preserving_Configuration_File_Changes">4.1.3. Preserving
Configuration File Changes</h3></div></div></div><a
id="id443668" class="indexterm"></a><div
class="para">
+ You will inevitably make changes to the configuration files installed by packages as
you use your Fedora system. <span
class="application"><strong>RPM</strong></span>, which
<span class="application"><strong>Yum</strong></span>
uses to perform changes to the system, provides a mechanism for ensuring their integrity.
Refer to <a class="xref"
href="sec-Installing_and_Upgrading.html">Section A.2.2, “Installing and
Upgrading”</a> for details on how to manage changes to configuration files across
package upgrades.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="part-Package_Management.html"><strong>Prev</strong>Part II. Package
Management</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Packages_and_Package_Groups.html"><strong>Next</strong>4.2. Packages
and Package Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch10s02s03.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch10s02s03.html
new file mode 100644
index 0000000..ca81f6e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch10s02s03.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>10.2.3. Starting and Stopping the 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP
Server" /><link rel="prev" href="lease-database.html"
title="10.2.2. Lease Database" /><link rel="next"
href="dhcp-relay-agent.html" title="10.2.4. DHCP Relay 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="lease-database.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="d
hcp-relay-agent.html"><strong>Next</strong></a></li></ul><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id576146">10.2.3. Starting and Stopping the
Server</h3></div></div></div><a id="id576152"
class="indexterm"></a><a id="id576166"
class="indexterm"></a><a id="id576179"
class="indexterm"></a><a id="id530070"
class="indexterm"></a><div class="important"><div
class="admonition_header"><h2>Starting the DHCP server for the first
time</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">
+ To start the DHCP service, use the following command:
+ </div><pre class="screen"><code
class="command">systemctl start dhcpd.service</code></pre><div
class="para">
+ To stop the DHCP server, type:
+ </div><pre class="screen"><code
class="command">systemctl stop dhcpd.service</code></pre><div
class="para">
+ By default, the DHCP service does not start at boot time. To configure the daemon to
start automatically at boot time, run:
+ </div><pre class="screen"><code
class="command">systemctl enable
dhcpcd.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div><a id="id554716"
class="indexterm"></a><a id="id554730"
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">
+ This is useful for a firewall machine with two network cards. One network card can be
configured as a DHCP client to retrieve an IP address to the Internet. The other network
card can be used as a DHCP server for the internal network behind the firewall. Specifying
only the network card connected to the internal network makes the system more secure
because users can not connect to the daemon via the Internet.
+ </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">Section 10.2.4, “DHCP Relay Agent”</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> — Do not print the entire
copyright message when starting the daemon.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="lease-database.html"><strong>Prev</strong>10.2.2. Lease
Database</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="dhcp-relay-agent.html"><strong>Next</strong>10.2.4. DHCP
Relay Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s02.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s02.html
new file mode 100644
index 0000000..53393e6
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s02.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>19.2. Installing and Running ABRT</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-abrt.html" title="Chapter 19. Automatic Bug-Reporting Tool
(ABRT)" /><link rel="prev" href="ch-abrt.html"
title="Chapter 19. Automatic Bug-Reporting Tool (ABRT)" /><link
rel="next" href="abrt-plugins.html" title="19.3. ABRT
Plugins" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-abrt.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="
abrt-plugins.html"><strong>Next</strong></a></li></ul><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="id632165">19.2. Installing and Running
ABRT</h2></div></div></div><div class="para">
+ By default, <span
class="application"><strong>ABRT</strong></span> should be
installed on your system, the <code class="systemitem">abrtd</code>
daemon configured to run at boot time, and <span
class="application"><strong>abrt-applet</strong></span> to
run in the Notification Area of your desktop session.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the ABRT
packages</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>ABRT</strong></span>, first
ensure the <code class="command">abrt-desktop</code> package is
installed on your system by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">yum install abrt-desktop</code></pre><div
class="para">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span> is
typically configured to start up at boot time. You can check that the <code
class="systemitem">abrtd</code> daemon is running by running the
following command, as <code class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl is-active
abrtd.service</code></pre><div class="para">
+ If you receive <code class="computeroutput">abrt is
stopped</code>, you can start the <code
class="systemitem">abrtd</code> service by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl start abrtd.service</code></pre><div
class="para">
+ You can ensure that the <code class="systemitem">abrtd</code>
service initializes at startup time by running the following command, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">systemctl enable
abrtd.service</code></pre><div class="para">
+ <span
class="application"><strong>ABRT</strong></span>'s
applet can be started by hand by running the <code
class="command">abrt-applet</code> program as a normal user when logged
into your desktop session, or by arranging for it to be started when the GUI session is
initialized.
+ </div><div class="figure"
id="fig-ABRT-Notification_Area_alarm_icon"><div
class="figure-contents"><div class="mediaobject"><img
src="images/abrt-alert.png" alt="The ABRT problem report" /><div
class="longdesc"><div class="para">
+ The ABRT problem report
+ </div></div></div></div><h6>Figure 19.2. The ABRT
problem report</h6></div><br class="figure-break" /><div
class="para">
+ When a crash is detected and saved, a broadcast <code
class="systemitem">D-Bus</code> message is sent about this crash. If
<code class="command">abrt-applet</code> is running, it receives
this message and displays an alarm icon in the Notification Area. You can open the GUI
application by clicking on this icon.
+ </div><div class="para">
+ Alternatively, you can open the <span
class="application"><strong>ABRT</strong></span> GUI
application by selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>Automatic Bug Reporting
Tool</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-abrt.html"><strong>Prev</strong>Chapter 19. Automatic
Bug-Reporting Tool (ABRT)</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="abrt-plugins.html"><strong>Next</strong>19.3. ABRT
Plugins</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05.html
new file mode 100644
index 0000000..9ccf197
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05.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>19.5. Using the Command Line 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-abrt.html" title="Chapter 19. Automatic Bug-Reporting Tool
(ABRT)" /><link rel="prev" href="generating-backtrace.html"
title="19.4. Generating Backtraces" /><link rel="next"
href="ch19s05s02.html" title="19.5.2. Reporting Crashes"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="generating-backtrace.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="
n"
href="ch19s05s02.html"><strong>Next</strong></a></li></ul><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="id551684">19.5. Using the Command Line
Interface</h2></div></div></div><div
class="para">
+ Crashes detected by <span
class="application"><strong>ABRT</strong></span> can be
viewed, reported, and deleted using the command line interface.
+ </div><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id483939">19.5.1. Viewing
Crashes</h3></div></div></div><div class="para">
+ To get a list of all crashes, simply enter <code
class="command">abrt-cli --list</code> or <code
class="command">abrt-cli -l</code>:
+ </div><pre class="screen">~]$ <code
class="command">abrt-cli --list</code>
+0.
+ UID : 500
+ UUID : 784b06666020e9f43718d99bf2649f19b4f251a9
+ Package : bash-4.1.2-3.el6
+ Executable : /bin/bash
+ Crash Time : Tue 20 Jul 2010 03:22:52 PM CEST
+ Crash Count: 2
+1.
+ UID : 500
+ UUID : 48007b98d65cca4530d99a564379e2609169239d
+ Package : coreutils-8.4-9.el6
+ Executable : /bin/sleep
+ Crash Time : Tue 20 Jul 2010 03:22:00 PM CEST
+ Crash Count: 1</pre><div class="para">
+ This output contains basic information for every crash. The <code
class="computeroutput">UID:</code> field shows the ID of the user which
ran the program that caused the crash. The <code
class="computeroutput">Package</code> field shows the name and version
of the Fedora package that contains the program, and the <code
class="computeroutput">Executable</code> field shows the location of
the binary or script that crashed. The <code class="computeroutput">Crash
Count</code> field indicates how many times the same crash happened.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="generating-backtrace.html"><strong>Prev</strong>19.4. Generating
Backtraces</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch19s05s02.html"><strong>Next</strong>19.5.2. Reporting
Crashes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05s02.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05s02.html
new file mode 100644
index 0000000..24c591b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05s02.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>19.5.2. Reporting Crashes</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch19s05.html" title="19.5. Using the Command Line Interface"
/><link rel="prev" href="ch19s05.html" title="19.5. Using
the Command Line Interface" /><link rel="next"
href="ch19s05s03.html" title="19.5.3. Deleting Crashes"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch19s05.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch19s05s03.html">
<strong>Next</strong></a></li></ul><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id461408">19.5.2. Reporting
Crashes</h3></div></div></div><div class="para">
+ To report a certain crash, enter <code
class="command">abrt-cli --report <em
class="replaceable"><code>UUID</code></em></code> or
<code class="command">abrt-cli --r <em
class="replaceable"><code>UUID</code></em></code>,
where <code class="varname">UUID</code> is a Universally Unique
Identifier of a crash from the list of crashes; to view this list, execute the <code
class="command">abrt-cli --list</code> command. You do not need to
remember the exact <code class="varname">UUID</code>; either use a
mouse to copy and paste it, or enter a unique prefix and press <span
class="keycap"><strong>ENTER</strong></span>.
+ </div><pre class="screen">~]$ <code
class="command">abrt-cli --report 480</code>
+<span
class="keycap"><strong><ENTER></strong></span>
+>> Starting report creation...</pre><div
class="para">
+ <span
class="application"><strong>ABRT</strong></span> analyzes
the crash and creates a report about it. This might take a while. When the report is
ready, <code class="command">abrt-cli</code> opens a text editor
with the content of the report. You can see what is being reported, and you can fill in
instructions on how to reproduce the crash and other comments. You should also check the
backtrace, because the backtrace might be sent to a public server and viewed by anyone,
depending on the plugin settings.
+ </div><div class="note"><div
class="admonition_header"><h2>Selecting a preferred text
editor</h2></div><div class="admonition"><div
class="para">
+ You can choose which text editor is used to check the reports. <code
class="command">abrt-cli</code> uses the editor defined in the <code
class="envar">ABRT_EDITOR</code> environment variable. If the variable
is not defined, it checks the <code class="envar">VISUAL</code> and
<code class="envar">EDITOR</code> variables. If none of these
variables is set, <code class="command">vi</code> is used. You can
set the preferred editor in your <code
class="filename">.bashrc</code> configuration file. For example, if you
prefer GNU Emacs, add the following line to the file:
+ </div><pre class="programlisting">export <code
class="varname">VISUAL</code>=<strong
class="userinput"><code>emacs</code></strong></pre></div></div><div
class="para">
+ When you are done with the report, save your changes and close the editor. You will
be asked which of the enabled <span
class="application"><strong>ABRT</strong></span> plugins
you want to use to send the report. Respond <span
class="keycap"><strong>Y</strong></span> to send the report
using your desired plugin or <span
class="keycap"><strong>N</strong></span> to skip a plugin
you wish not to use.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch19s05.html"><strong>Prev</strong>19.5. Using the Command
Line Interface</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch19s05s03.html"><strong>Next</strong>19.5.3. Deleting
Crashes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05s03.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05s03.html
new file mode 100644
index 0000000..5da4a63
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ch19s05s03.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.5.3. Deleting Crashes</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch19s05.html" title="19.5. Using the Command Line Interface"
/><link rel="prev" href="ch19s05s02.html"
title="19.5.2. Reporting Crashes" /><link rel="next"
href="configuring.html" title="19.6. Configuring ABRT"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch19s05s02.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="configuring.html"><strong
Next</strong></a></li></ul><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id626809">19.5.3. Deleting
Crashes</h3></div></div></div><div class="para">
+ If you know that you do not want to report a certain crash dump, you can delete
it from the crash list. To delete a certain crash dump, enter the command: <code
class="command">abrt-cli --delete <em
class="replaceable"><code>UUID</code></em> </code>.
+ </div><div class="para">
+ Note that <span
class="application"><strong>ABRT</strong></span> performs a
detection of duplicate crashes by comparing new crashes with all locally saved crashes.
For a repeating crash, <span
class="application"><strong>ABRT</strong></span> requires
you to act upon it only once. However, if you delete the crash dump of that crash, the
next time this specific crash occurs, <span
class="application"><strong>ABRT</strong></span> will treat
it as a new crash: <span
class="application"><strong>ABRT</strong></span> will alert
you about it, prompt you to fill in a description, and report it. This can be redundant,
therefore, deleting a crash is not advisable.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch19s05s02.html"><strong>Prev</strong>19.5.2. Reporting
Crashes</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="configuring.html"><strong>Next</strong>19.6. Configuring
ABRT</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Domains.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Domains.html
new file mode 100644
index 0000000..0bb4f7f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_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>8.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="prev"
href="chap-SSSD_User_Guide-Configuring_Services.html"
title="8.2.4. Configuring Services" /><link rel="next"
href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"
title="8.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="docnav"><li c
lass="previous"><a accesskey="p"
href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>Next</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"
id="chap-SSSD_User_Guide-Configuring_Domains">8.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><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">Section 8.2.5.2,
“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">Section 8.2.6,
“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">Section 8.2.7,
“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"
id="sect-SSSD_User_Guide-Configuring_Domains-Domain_Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Domain_Configuration_Options-General_Domain_Configuration_Options">8.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">Section 8.2.7,
“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@IPA</code>
+ipauser01@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@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@domain</code>, not <code
class="systemitem">name@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"
id="sect-SSSD_User_Guide-Domain_Configuration_Options-Proxy_Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">8.2.5.2. Configuring
an LDAP Domain</h4></div></div></div><a id="id566805"
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...
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="id568432" 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@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="id589804" 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">Section 8.2.3.2.4.1,
“Using SRV Records with Failover”</a>.
+ </div></div></div><h5
id="id557590"></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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">8.2.5.3. Configuring
a Microsoft Active Directory Domain</h4></div></div></div><a
id="id552164" 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...
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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2003">8.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">Section 8.2.5.3.2,
“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="id604163">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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008">8.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>Prev</strong>8.2.4. Configuring
Services</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>Next</strong>8.2.6. Setting
Up Kerberos Authentication</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.html
new file mode 100644
index 0000000..51758f4
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.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>8.2.4. Configuring Services</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="prev"
href="chap-SSSD_User_Guide-Setting_Up_SSSD.html" title="8.2.3. Setting Up
SSSD" /><link rel="next"
href="chap-SSSD_User_Guide-Configuring_Domains.html"
title="8.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Configuring_Domains.html"><strong>Next</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"
id="chap-SSSD_User_Guide-Configuring_Services">8.2.4. Configuring
Services</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"
id="sect-SSSD_User_Guide-Configuring_Services-Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Configuration_Options-General_Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Configuration_Options-NSS_Configuration_Options">8.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"
id="sect-SSSD_User_Guide-Configuration_Options-PAM_Configuration_Options">8.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>Prev</strong>8.2.3. Setting
Up SSSD</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Configuring_Domains.html"><strong>Next</strong>8.2.5. Configuring
Domains</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.html
new file mode 100644
index 0000000..b3bb7c3
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.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>8.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Configuring_Authentication.html" title="Chapter 8. Configuring
Authentication" /><link rel="prev"
href="ch-Configuring_Authentication.html" title="Chapter 8. Configuring
Authentication" /><link rel="next"
href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"
title="8.2.2. SSSD Features" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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_Authentic
ation.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="section"
id="chap-SSSD_User_Guide-Introduction" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="chap-SSSD_User_Guide-Introduction">8.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"
id="sect-SSSD_User_Guide-Introduction-What_is_SSSD">8.2.1. What is
SSSD?</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>Prev</strong>Chapter 8. Configuring
Authentication</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>Next</strong>8.2.2. SSSD
Features</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
new file mode 100644
index 0000000..e15ad99
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
@@ -0,0 +1,186 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="prev"
href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"
title="8.2.2. SSSD Features" /><link rel="next"
href="chap-SSSD_User_Guide-Configuring_Services.html"
title="8.2.4. Configuring Services" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>Next</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"
id="chap-SSSD_User_Guide-Setting_Up_SSSD">8.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"
id="sect-SSSD_User_Guide-Setting_Up_SSSD-Installing_SSSD">8.2.3.1. Installing
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"
id="sect-SSSD_User_Guide-Installing_SSSD-Upgrading_from_a_Previous_Version">8.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><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"
id="sect-SSSD_User_Guide-Installing_SSSD-Starting_and_Stopping_SSSD">8.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">Section 8.2.5,
“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"
id="sect-SSSD_User_Guide-Setting_Up_SSSD-Configuring_SSSD">8.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">Section 8.2.9,
“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"
id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS">8.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"
id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h6 class="title"
id="id586029">8.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"
id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id551994">8.2.3.2.3. Configuring Access
Control</h5></div></div></div><a id="id607298"
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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h6 class="title"
id="id542117">8.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="id484930">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="id597335">Access Control
Rules</h5><a id="id572694" 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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h6 class="title"
id="id604723">8.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="id608235">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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover">8.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">Section 8.2.3.2.4.1,
“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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">8.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"
id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-How_the_Failover_Mechanism_Works">8.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">Section 8.2.3.2.4.1,
“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>Prev</strong>8.2.2. SSSD
Features</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>Next</strong>8.2.4. Configuring
Services</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html
new file mode 100644
index 0000000..ace86be
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html
@@ -0,0 +1,122 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.8. Troubleshooting</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="prev"
href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html"
title="8.2.7. Configuring a Proxy Domain" /><link rel="next"
href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"
title="8.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" alt="Document
ation 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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>Next</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"
id="chap-SSSD_User_Guide-Troubleshooting">8.2.8. Troubleshooting</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"
id="sect-SSSD_User_Guide-Troubleshooting-Using_SSSD_Log_Files">8.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"
id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Configuration">8.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"
id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Service_Configuration">8.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"
id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_NSS">8.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">Section 8.2.3.2.1,
“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"
id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_PAM">8.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@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">Section 8.2.3.2.2,
“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"><div class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id555445">8.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"
id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Domain_Configuration">8.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"
id="sect-SSSD_User_Guide-Troubleshooting-Additional_Resources">8.2.8.5. Additional
Resources</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"
id="sect-SSSD_User_Guide-Additional_Resources-Manual_Pages">8.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"
id="sect-SSSD_User_Guide-Additional_Resources-Mailing_Lists">8.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">...
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>Prev</strong>8.2.7. Configuring
a Proxy Domain</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>Next</strong>8.2.9. SSSD
Configuration File Format</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-automatic-reporting.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-automatic-reporting.html
new file mode 100644
index 0000000..e0adcf4
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-automatic-reporting.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.8. Configuring Automatic Reporting</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-abrt.html" title="Chapter 19. Automatic Bug-Reporting Tool
(ABRT)" /><link rel="prev"
href="testing-upload-method.html" title="19.7.2. Testing the Upload
Method" /><link rel="next"
href="part-Kernel_Module_and_Driver_Configuration.html"
title="Part VII. Kernel, Module and Driver 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="testing-upload-method.h
tml"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="part-Kernel_Module_and_Driver_Configuration.html"><strong>Next</strong></a></li></ul><div
class="section" id="configuring-automatic-reporting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="configuring-automatic-reporting">19.8. Configuring Automatic
Reporting</h2></div></div></div><div
class="para">
+ <span
class="application"><strong>ABRT</strong></span> can be
configured to automatically report any detected issues or crashes. The following steps
show how to enable this feature:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ In your <code class="filename">/etc/abrt/abrt.conf</code>
configuration file, for each analyzer, change the list of reporters according to your
needs, for example:
+ </div><pre class="programlisting">[ AnalyzerActionsAndReporters
]
+Kerneloops = Logger
+CCpp = Logger
+Python = Logger</pre></li><li class="listitem"><div
class="para">
+ In the configuration files corresponding to each analyzer plugin (that is, <code
class="filename">/etc/abrt/plugins/CCpp.conf</code>, <code
class="filename">/etc/abrt/plugins/Kerneloops.conf</code> and <code
class="filename">/etc/abrt/plugins/Python.conf</code>), add the
following line:
+ </div><pre class="programlisting">AutoReportUIDs = <em
class="replaceable"><code>USERNAME</code></em></pre><div
class="para">
+ where <em
class="replaceable"><code>USERNAME</code></em> represents a
user whose detected crashes and issues will be automatically reported via your specified
reporters. You can specify multiple users by separating them with a comma (<code
class="literal">,</code>).
+ </div></li></ol></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="testing-upload-method.html"><strong>Prev</strong>19.7.2. Testing
the Upload Method</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="part-Kernel_Module_and_Driver_Configuration.html"><strong>Next</strong>Part VII. Kernel,
Module and Driver Configuration</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-centralized-crash-collection.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-centralized-crash-collection.html
new file mode 100644
index 0000000..1ab226b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-centralized-crash-collection.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>19.7. Configuring Centralized Crash Collection</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-abrt.html" title="Chapter 19. Automatic Bug-Reporting Tool
(ABRT)" /><link rel="prev" href="configuring.html"
title="19.6. Configuring ABRT" /><link rel="next"
href="testing-upload-method.html" title="19.7.2. Testing the Upload
Method" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="configuring.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" h
ref="testing-upload-method.html"><strong>Next</strong></a></li></ul><div
class="section"
id="configuring-centralized-crash-collection"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="configuring-centralized-crash-collection">19.7. Configuring Centralized
Crash Collection</h2></div></div></div><div
class="para">
+ You can set up <span
class="application"><strong>ABRT</strong></span> so that
crash reports are collected from multiple systems and sent to a dedicated system for
further processing. This is useful when an administrator does not want to log into
hundreds of systems and manually check for crashes found by <span
class="application"><strong>ABRT</strong></span>. In order
to use this method, you need to install the <span
class="application"><strong>abrt-plugin-reportuploader</strong></span>
plugin (<code class="command">yum install
abrt-plugin-reportuploader</code>).
+ </div><div class="para">
+ The steps to configure <span
class="application"><strong>ABRT</strong></span>'s
centralized crash collection are:
+ </div><div class="orderedlist"><ol><li
class="listitem"><div class="para">
+ Complete the following steps on a dedicated system ("server system"):
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Create a directory to which you want the crash reports to be uploaded to. Usually,
<code class="filename">/var/spool/abrt-upload/</code> is used (the
rest of the document assumes you are using <code
class="filename">/var/spool/abrt-upload/</code>). Make sure this
directory is writable by the <code class="systemitem">abrt</code>
user.
+ </div><div class="note"><div
class="admonition_header"><h2>The abrt user and
group</h2></div><div class="admonition"><div
class="para">
+ When the <span class="package">abrt-desktop</span> package
is installed, it creates a new system user and a group, both named <code
class="systemitem">abrt</code>. This user is used by the <code
class="systemitem">abrtd</code> daemon for various things, for example,
as the owner:group of <code
class="filename">/var/spool/abrt/*</code> directories.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ In the <code class="filename">/etc/abrt/abrt.conf</code>
configuration file, set the <code
class="varname">WatchCrashdumpArchiveDir</code> directive to the
following:
+<pre class="programlisting">WatchCrashdumpArchiveDir =
/var/spool/abrt-upload/</pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ Determine your preferred upload mechanism; for example, <code
class="systemitem">FTP</code> or <code
class="systemitem">SCP</code>. For more information on how to configure
<code class="systemitem">FTP</code>, refer to <a
class="xref" href="s1-FTP.html">Section 15.2, “FTP”</a>. For
more information on how to configure <code
class="systemitem">SCP</code>, refer to <a class="xref"
href="s2-ssh-clients-scp.html">Section 9.3.2, “Using the <code
class="command">scp</code> Utility”</a>.
+ </div><div class="para">
+ For security reasons, make sure that uploads can only be performed by a specific
user and with a password. The rest of the document assumes that the username used for
uploads is <code class="systemitem">USERNAME</code> and the password
is <code class="literal">PASSWORD</code>. If you do not already have
a suitable username which can be used to perform uploads under, you may use the <code
class="systemitem">abrt</code> user which already exists on every
system where <span
class="application"><strong>ABRT</strong></span> is
installed.
+ </div><div class="para">
+ It is advisable to check whether your upload method works. For more information,
refer to <a class="xref"
href="testing-upload-method.html">Section 19.7.2, “Testing the Upload
Method”</a>.
+ </div></li><li class="listitem"><div
class="para">
+ It is advisable to check and modify the following parameters if needed:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ The <em
class="parameter"><code>MaxCrashReportsSize</code></em>
directive (in <code class="filename">/etc/abrt/abrt.conf</code>)
needs to be set to a larger value if the expected volume of crash data is larger than the
default <code class="constant">1000</code> MB.
+ </div></li><li class="listitem"><div
class="para">
+ The <em
class="parameter"><code>ProcessUnpackaged</code></em>
directive (in <code class="filename">/etc/abrt/abrt.conf</code>)
needs to be set to <em
class="replaceable"><code>yes</code></em> and the <em
class="parameter"><code>BacktraceRemotes</code></em> (in
<code class="filename">/etc/abrt/plugins/CCpp.conf</code>) needs to
be set to <em class="replaceable"><code>no</code></em>
if the client system and the server system have significantly different sets of installed
packages.
+ </div></li></ul></div></li></ul></div></li><li
class="listitem"><div class="para">
+ Complete the following steps on every client system which will use the central
management method:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Modify the <code
class="filename">/etc/abrt/plugins/ReportUploader.conf</code>
configuration file so that the <span
class="application"><strong>ReportUploader</strong></span>
plugin knows where to copy the saved crash reports in the following way:
+<pre class="programlisting">Enabled = yes
+Upload = yes
+URL = ftp://USERNAME:PASSWORD@SERVERNAME/var/spool/abrt-upload/</pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ To automatically send the crash reports to the server system immediately after the
crash occurs, is detected, and saved, set the <code
class="varname">[ ActionsAndReporters ]</code> directive in the
<code class="filename">/etc/abrt/abrt.conf</code> configuration file
to the following:
+<pre class="programlisting">ActionsAndReporters =
ReportUploader</pre>
+
+ </div></li><li class="listitem"><div
class="para">
+ Alternatively, if user interaction is required before the crash dump is sent to
the server system, set the <em
class="parameter"><code>ReportUploader</code></em> to be a
reporter plugin for a specific crash type in the <code
class="literal">[ AnalyzerActionsAndReporters ]</code> section of the
<code class="filename">/etc/abrt/abrt.conf</code> configuration
file. The user will be required to run <span
class="application"><strong>abrt-cli</strong></span> or
<span
class="application"><strong>abrt-gui</strong></span> and
instruct the <code class="systemitem">abrtd</code> daemon to report
the crash and send it to the server system. For example, if you want all crash types to
use this method, edit the <code
class="literal">[ AnalyzerActionsAndReporters ]</code> section in your
<code class="filename">/etc/abrt/abrt.conf</code> configuration file
in the following way:
+ </div><pre class="programlisting">Kerneloops =
ReportUploader
+CCpp = ReportUploader
+Python =
ReportUploader</pre></li></ul></div></li></ol></div><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id462013">19.7.1. Testing ABRT's Crash
Detection</h3></div></div></div><div
class="para">
+ After completing all the steps of the configuration process, the basic setup is
finished. To test that this setup works properly use the <code
class="command">kill -s SEGV <em
class="replaceable"><code>PID</code></em> </code>
command to terminate a process on a client system. For example, start a <code
class="systemitem">sleep</code> process and terminate it with the
<code class="command">kill</code> command in the following way:
+<pre class="screen">~]$ <code class="command">sleep 100
&</code>
+[1] 2823
+~]$ <code class="command">kill -s SEGV 2823</code></pre>
+ <span
class="application"><strong>ABRT</strong></span> should
detect a crash shortly after executing the <code
class="command">kill</code> command. Check that the crash was detected
by <span
class="application"><strong>ABRT</strong></span> on the
client system (this can be checked by examining the appropriate syslog file, by running
the <code class="command">abrt-cli --list --full</code> command, or
by examining the crash dump created in the <code
class="filename">/var/spool/abrt</code> directory), copied to the
server system, unpacked on the server system and can be seen and acted upon using <code
class="command">abrt-cli</code> or <code
class="command">abrt-gui</code> on the server system.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="configuring.html"><strong>Prev</strong>19.6. Configuring
ABRT</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="testing-upload-method.html"><strong>Next</strong>19.7.2. Testing
the Upload Method</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-plugins-in-the-gui.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-plugins-in-the-gui.html
new file mode 100644
index 0000000..51f2ead
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring-plugins-in-the-gui.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>19.3.3. Plugin Configuration in the GUI</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="abrt-plugins.html" title="19.3. ABRT Plugins" /><link
rel="prev" href="reporter-plugins.html" title="19.3.2. Reporter
Plugins" /><link rel="next"
href="generating-backtrace.html" title="19.4. Generating Backtraces"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="reporter-plugins.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="generating-bac
ktrace.html"><strong>Next</strong></a></li></ul><div
class="section" id="configuring-plugins-in-the-gui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="configuring-plugins-in-the-gui">19.3.3. Plugin Configuration in the
GUI</h3></div></div></div><div class="para">
+ You can override the system-wide plugin configuration in the <code
class="filename">/etc/abrt/plugins/*.conf</code> configuration files on
a per-user basis. Each of the plugins specified in section <a class="xref"
href="reporter-plugins.html">Section 19.3.2, “Reporter Plugins”</a> can
be configured in the <span
class="application"><strong>ABRT</strong></span> GUI
application. Open the plugins window by clicking <span
class="guimenu"><strong>Edit</strong></span> → <span
class="guisubmenu"><strong>Event
configuration</strong></span>. This window shows a list of all installed
plugins. When you select one of the configurable plugins, you can click the <span
class="guibutton"><strong>Configure Event</strong></span>
button and you will be able to configure your desired plugin. If you change any of the
plugins' parameters, they are saved in the GNOME Keyring and will be used in the
future GUI sessions.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not store sensitive data in global
configuration files</h2></div><div class="admonition"><div
class="para">
+ All of the <code
class="filename">/etc/abrt/plugins/*.conf</code> configuration files
are world readable and are meant to be used as global settings. Thus, it is not advisable
to store usernames, passwords or any other sensitive data in them. The per-user settings
(set in the GUI application and readable by the owner of $HOME only) are stored in the
Gnome keyring or can be stored in a text file in <code
class="filename">$HOME/.abrt/*.conf</code> for use in <code
class="command">abrt-cli</code>.
+ </div></div></div><div class="figure"
id="mediaobj-abrt-plugins"><div
class="figure-contents"><div class="mediaobject"><img
src="images/abrt-event-configuration.png" alt="ABRT plugins"
/><div class="longdesc"><div class="para">
+ ABRT plugins
+ </div></div></div></div><h6>Figure 19.3. ABRT
plugins</h6></div><br class="figure-break" /><div
class="para">
+ The following is a list of all configuration options available for each configurable
plugin in the <span
class="application"><strong>ABRT</strong></span> GUI
application.
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span
class="term">MailX</span></dt><dd><div
class="para">
+ In the <span class="guilabel"><strong>MailX plugin
configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Subject</strong></span> — A string
that appears in the <code class="literal">Subject</code> field of a
crash report email sent by <span
class="application"><strong>mailx</strong></span> (by
default, set to <code class="literal">"[abrt] crash
report"</code>).
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Your
Email</strong></span> — A string that appears in the <code
class="literal">From</code> field of a crash report email.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Recipient's
Email</strong></span> — Email address of the recipient of a crash report
email.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Send Binary
Data</strong></span> option is checked, the crash report email will also
contain all binary files associated with the crash in an attachment. The core dump file is
also sent as an attachment.
+ </div></dd><dt class="varlistentry"><span
class="term">ReportUploader</span></dt><dd><div
class="para">
+ In the <span class="guilabel"><strong>ReportUploader plugin
configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Customer</strong></span> —
Specifies customer's identification.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Ticket</strong></span> — Specifies
the Ticket ID number in a specific issue tracker that collects crash reports.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>URL</strong></span> — Specifies
the URL of the issue tracker used to collect crash reports.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Retry
count</strong></span> — Specifies the number of retries should an upload
fail.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Retry
delay</strong></span> — Specifies the number or seconds between two retries.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Use
encryption</strong></span> option is checked, the crash report sent to the
issue tracker is encrypted.
+ </div><div class="para">
+ When the <span
class="guilabel"><strong>Upload</strong></span> option is
checked, all crash reports are uploaded to the specified issue tracker. If the option is
unchecked, all crash reports are saved locally.
+ </div></dd><dt class="varlistentry"><span
class="term">Bugzilla</span></dt><dd><div
class="para">
+ In the <span class="guilabel"><strong>Bugzilla plugin
configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Bugzilla
URL</strong></span> — Specifies the Bugzilla URL where crash dumps are sent
(by default, set to <a
href="https://bugzilla.redhat.com">https://bugzilla.redhat.com</a>).
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Login
(email)</strong></span> — User login which is used to log into Bugzilla and
create a Bugzilla database entry for a reported crash.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Password</strong></span> —
Password used to log into Bugzilla.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>SSL
verify</strong></span> option is checked, the <code
class="systemitem">SSL</code> protocol is used when sending the data
over the network.
+ </div></dd><dt class="varlistentry"><span
class="term">Logger</span></dt><dd><div
class="para">
+ In the <span class="guilabel"><strong>Logger plugin
configuration</strong></span>, you can configure the following parameter:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span class="guilabel"><strong>Logger
file</strong></span> — Specifies a file into which the crash reports are saved
(by default, set to <code
class="filename">/var/log/abrt.log</code>).
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Append new
logs</strong></span> option is checked, the Logger plugin will append new
crash reports to the log file specified in the <span
class="guilabel"><strong>Logger file</strong></span>
option. When unchecked, the new crash report always replaces the previous one.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="reporter-plugins.html"><strong>Prev</strong>19.3.2. Reporter
Plugins</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="generating-backtrace.html"><strong>Next</strong>19.4. Generating
Backtraces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring.html
new file mode 100644
index 0000000..81fcf52
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/configuring.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>19.6. Configuring ABRT</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-abrt.html" title="Chapter 19. Automatic Bug-Reporting Tool
(ABRT)" /><link rel="prev" href="ch19s05s03.html"
title="19.5.3. Deleting Crashes" /><link rel="next"
href="configuring-centralized-crash-collection.html"
title="19.7. Configuring Centralized Crash Collection"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch19s05s03.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="configuring-centralized-crash-collection.html"><strong>Next</strong></a></li></ul><div
class="section" id="configuring"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="configuring">19.6. Configuring
ABRT</h2></div></div></div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span>'s main
configuration file is <code
class="filename">/etc/abrt/abrt.conf</code>. <span
class="application"><strong>ABRT</strong></span> plugins
can be configured through their configuration files, located in the <code
class="filename">/etc/abrt/plugins/</code> directory.
+ </div><div class="important"><div
class="admonition_header"><h2>Restart the abrtd daemon to apply the
changes</h2></div><div class="admonition"><div
class="para">
+ After changing and saving the <code
class="filename">/etc/abrt/abrt.conf</code> configuration file, you
must restart the <code class="systemitem">abrtd</code> daemon—as
<code class="systemitem">root</code>—for the new settings to take
effect:
+ </div><pre class="screen"><code
class="command">systemctl restart
abrtd.service</code></pre></div></div><div
class="para">
+ The following configuration directives are currently supported in <code
class="filename">/etc/abrt/abrt.conf</code>.
+ </div><div class="variablelist"><h6>[ Common ] Section
Directives</h6><dl><dt class="varlistentry"><span
class="term">OpenGPGCheck = <em
class="replaceable"><code>yes/no</code></em>
</span></dt><dd><div class="para">
+ Setting the <code class="computeroutput">OpenGPGCheck</code>
directive to <strong
class="userinput"><code>yes</code></strong> (the default
setting) tells <span
class="application"><strong>ABRT</strong></span> to
<span class="emphasis"><em>only</em></span> analyze and
handle crashes in applications provided by packages which are signed by the GPG keys whose
locations are listed in the <code
class="filename">/etc/abrt/gpg_keys</code> file. Setting <em
class="parameter"><code>OpenGPGCheck</code></em> to
<strong class="userinput"><code>no</code></strong> tells
<span class="application"><strong>ABRT</strong></span>
to catch crashes in all programs.
+ </div></dd><dt class="varlistentry"><span
class="term">BlackList = nspluginwrapper, valgrind, strace,
avant-window-navigator, [<span class="optional"><em
class="replaceable"><code>additional_packages</code></em>
</span>] </span></dt><dd><div class="para">
+ Crashes in packages and binaries listed after the <em
class="parameter"><code>BlackList</code></em> directive
will not be handled by <span
class="application"><strong>ABRT</strong></span>. If you
want <span
class="application"><strong>ABRT</strong></span> to ignore
other packages and binaries, list them here separated by commas.
+ </div></dd><dt class="varlistentry"><span
class="term">ProcessUnpackaged = <em
class="replaceable"><code>yes/no</code></em>
</span></dt><dd><div class="para">
+ This directive tells <span
class="application"><strong>ABRT</strong></span> whether to
process crashes in executables that do not belong to any package.
+ </div></dd><dt class="varlistentry"><span
class="term">BlackListedPaths = <code
class="filename">/usr/share/doc/*</code>, <code
class="filename">*/example*</code>
</span></dt><dd><div class="para">
+ Crashes in executables in these paths will be ignored by <span
class="application"><strong>ABRT</strong></span>.
+ </div></dd><dt class="varlistentry"><span
class="term">Database = SQLite3</span></dt><dd><div
class="para">
+ This directive instructs <span
class="application"><strong>ABRT</strong></span> to store
its crash data in the <span
class="application"><strong>SQLite3</strong></span>
database. Other databases are not currently supported. However, <span
class="application"><strong>ABRT</strong></span>'s
plugin architecture allows for future support for alternative databases.
+ </div></dd><dt class="varlistentry"><span
class="term">#WatchCrashdumpArchiveDir =
/var/spool/abrt-upload/</span></dt><dd><div
class="para">
+ This directive is commented out by default. Enable (uncomment) it if you want
<code class="systemitem">abrtd</code> to auto-unpack crashdump
tarballs which appear in the specified directory — in this case <code
class="filename">/var/spool/abrt-upload/</code> — (for example,
uploaded via <code class="systemitem">ftp</code>, <code
class="systemitem">scp</code>, etc.). You must ensure that whatever
directory you specify in this directive exists and is writable for <code
class="systemitem">abrtd</code>. <code
class="systemitem">abrtd</code> will not create it automatically.
+ </div></dd><dt class="varlistentry"><span
class="term">MaxCrashReportsSize = <em
class="replaceable"><code>size_in_megabytes</code></em>
</span></dt><dd><div class="para">
+ This option sets the amount of storage space, in megabytes, used by <span
class="application"><strong>ABRT</strong></span> to store
all crash information from all users. The default setting is <code
class="constant">1000</code> MB. Once the quota specified here has been
met, <span
class="application"><strong>ABRT</strong></span> will
continue catching crashes, and in order to make room for the new crash dumps, it will
delete the oldest and largest ones.
+ </div></dd><dt class="varlistentry"><span
class="term">ActionsAndReporters = SOSreport, [<span
class="optional"><em
class="replaceable"><code>additional_plugins</code></em>
</span>] </span></dt><dd><div class="para">
+ This option tells <span
class="application"><strong>ABRT</strong></span> to run the
specified plugin(s) immediately after a crash is detected and saved. For example, the
<strong
class="userinput"><code>SOSreport</code></strong> plugin
runs the <code class="systemitem">sosreport</code> tool which adds
the data collected by it to the created crash dump. You can turn this behavior off by
commenting out this line. For further fine-tuning, you can add <strong
class="userinput"><code>SOSreport</code></strong> (or any
other specified plugin) to either the <em
class="parameter"><code>CCpp</code></em> or <em
class="parameter"><code>Python</code></em> options to make
<span class="application"><strong>ABRT</strong></span>
run <code class="command">sosreport</code> (or any other specified
plugin) after any C and C++ or Python applications crash, respectively. For more
information on various Action and Reporter plugins, refer to <a class="xref"
href="abrt-plugins.html">Section 19.
3, “ ABRT Plugins”</a>
+ </div></dd></dl></div><div
class="variablelist"><h6>[ AnalyzerActionsAndReporters ] Section
Directives</h6><div class="para">
+ This section allows you to associate certain analyzer actions and reporter actions to
run when <span
class="application"><strong>ABRT</strong></span> catches
kernel oopses or crashes in C, C++ or Python programs. The actions and reporters specified
in any of the directives below will run only if you run <code
class="command">abrt-gui</code> or <code
class="command">abrt-cli</code> and report the crash that occurred. If
you do not specify any actions and reporters in these directives, you will not be able to
report a crash via <code class="command">abrt-gui</code> or <code
class="command">abrt-cli</code>. The order of actions and reporters is
important. Commenting out a directive, will cause <span
class="application"><strong>ABRT</strong></span> not to
catch the crashes associated with that directive. For example, commenting out the
Kerneloops line will cause <span
class="application"><strong>ABRT</strong></span> not to
catch kernel oopses.
+ </div><dl><dt class="varlistentry"><span
class="term">Kerneloops = Logger</span></dt><dd><div
class="para">
+ This directive specifies that, for kernel oopses, the Logger reporter will be run.
+ </div></dd><dt class="varlistentry"><span
class="term">CCpp = Logger</span></dt><dd><div
class="para">
+ This directive specifies that, when C or C++ program crashes occur, the Logger
reporter will be run.
+ </div></dd><dt class="varlistentry"><span
class="term">Python = Logger</span></dt><dd><div
class="para">
+ This directive specifies that, when Python program crashes occur, the Logger
reporter will be run.
+ </div></dd></dl></div><div class="para">
+ Each of these destinations' details can be specified in the corresponding <code
class="filename">plugins/*.conf</code> file. All these options can also
be configured through the <code class="command">abrt-gui</code>
application (for more information on plugin configuration refer to <a
class="xref" href="abrt-plugins.html">Section 19.3, “ ABRT
Plugins”</a>).
+ </div><div class="variablelist"><h6>[ Cron ] Section
Directives</h6><dl><dt class="varlistentry"><span
class="term"> <em
class="replaceable"><code>time</code></em> = <em
class="replaceable"><code>action_to_run</code></em>
</span></dt><dd><div class="para">
+ The <code class="computeroutput">[ Cron ]</code> section of
<code class="filename">abrt.conf</code> allows you to specify the
exact time, or elapsed amount of time between, when <span
class="application"><strong>ABRT</strong></span> should run
a certain action, such as scanning for kernel oopses or performing file transfers. You can
list further actions to run by appending them to the end of this section.
+ </div><div class="example"
id="ex-_Cron__section_of__etc_abrt_abrt.conf"><h6>Example 19.1. [ Cron ]
section of /etc/abrt/abrt.conf</h6><div
class="example-contents"><pre class="programlisting"># Which
Action plugins to run repeatedly
+[ Cron ]
+# h:m - at h:m
+# s - every s seconds
+120 = KerneloopsScanner
+#02:00 = FileTransfer</pre></div></div><br
class="example-break" /><div class="para">
+ The format for an entry is either <strong
class="userinput"><code>time_in_seconds = <em
class="replaceable"><code>action_to_run</code></em>
</code></strong> or <strong
class="userinput"><code>hh:mm = action_to_run
</code></strong>, where <strong
class="userinput"><code>hh</code></strong> (hour) is in the
range <code class="constant">00-23</code> (all hours less than 10
should be zero-filled, i.e. preceded by a <code
class="constant">0</code>), and <strong
class="userinput"><code>mm</code></strong> (minute) is
<code class="constant">00-59</code>, zero-filled likewise.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch19s05s03.html"><strong>Prev</strong>19.5.3. Deleting
Crashes</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="configuring-centralized-crash-collection.html"><strong>Next</strong>19.7. Configuring
Centralized Crash Collection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/dhcp-relay-agent.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/dhcp-relay-agent.html
new file mode 100644
index 0000000..25b6540
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/dhcp-relay-agent.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>10.2.4. DHCP Relay 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP
Server" /><link rel="prev" href="ch10s02s03.html"
title="10.2.3. Starting and Stopping the Server" /><link
rel="next" href="s1-dhcp-configuring-client.html"
title="10.3. Configuring a DHCP Client" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch10s02s03.html"><strong>Prev</strong></a></li><li
class="nex
t"><a accesskey="n"
href="s1-dhcp-configuring-client.html"><strong>Next</strong></a></li></ul><div
class="section" id="dhcp-relay-agent"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="dhcp-relay-agent">10.2.4. DHCP Relay
Agent</h3></div></div></div><a id="id550695"
class="indexterm"></a><a id="id607345"
class="indexterm"></a><a id="id607358"
class="indexterm"></a><div class="para">
+ The DHCP Relay Agent (<code class="command">dhcrelay</code>)
allows for the relay of DHCP and BOOTP requests from a subnet with no DHCP server on it to
one or more DHCP servers on other subnets.
+ </div><div class="para">
+ When a DHCP client requests information, the DHCP Relay Agent forwards the request to
the list of DHCP servers specified when the DHCP Relay Agent is started. When a DHCP
server returns a reply, the reply is broadcast or unicast on the network that sent the
original request.
+ </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">
+ To start the DHCP Relay Agent, use the following command:
+ </div><pre class="screen"><code
class="command">systemctl start
dhcrelay.service</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch10s02s03.html"><strong>Prev</strong>10.2.3. Starting and
Stopping the Server</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-dhcp-configuring-client.html"><strong>Next</strong>10.3. Configuring
a DHCP Client</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/generating-backtrace.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/generating-backtrace.html
new file mode 100644
index 0000000..74130ba
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/generating-backtrace.html
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.4. Generating Backtraces</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-abrt.html" title="Chapter 19. Automatic Bug-Reporting Tool
(ABRT)" /><link rel="prev"
href="configuring-plugins-in-the-gui.html" title="19.3.3. Plugin
Configuration in the GUI" /><link rel="next"
href="ch19s05.html" title="19.5. Using the Command Line 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="configuring-plugins-in-the-gui.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n"
href="ch19s05.html"><strong>Next</strong></a></li></ul><div
class="section" id="generating-backtrace"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="generating-backtrace">19.4. Generating
Backtraces</h2></div></div></div><div
class="para">
+ In order to analyze a reported crash, developers need as much detail about the crash
as possible. A <em class="firstterm">stack backtrace</em> is an
important source of information when a crash in a binary program (caught by the <code
class="command">CCpp</code> analyzer plugin) occurs.
+ </div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span> is
configured to generate a backtrace whenever a crash is reported through the <span
class="application"><strong>ABRT</strong></span> GUI
application or the <span
class="application"><strong>ABRT</strong></span> command
line interface.
+ </div><div class="para">
+ <span
class="application"><strong>ABRT</strong></span> completes
the following steps to generate a backtrace:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It examines the core dump (which consists of the recorded contents of the memory of
an application at a specific time), which is saved in the crash dump directory. From this
file, <span
class="application"><strong>ABRT</strong></span> extracts
the information about the crashed binary program and information about every loaded
dynamic library.
+ </div></li><li class="listitem"><div
class="para">
+ It queries <span
class="application"><strong>Yum</strong></span> to
determine which <span class="package">debuginfo</span> packages
correspond to all the files extracted from the crash dump. This is the first potentially
slow operation. <span
class="application"><strong>Yum</strong></span> may need to
refresh the <em
class="parameter"><code>filelists</code></em> of various
repositories in order to find the correct package names. This process may take a few
minutes.
+ </div></li><li class="listitem"><div
class="para">
+ It downloads the needed <span class="package">debuginfo</span>
packages, and extracts and saves the <code
class="command">debuginfo</code> files. In order to speed up future
backtrace generation, <code class="command">debuginfo</code> files
are cached in the <code class="filename">/var/cache/abrt-di</code>
directory.
+ </div></li><li class="listitem"><div
class="para">
+ It generates a backtrace using <span
class="application"><strong>GDB</strong></span> (the GNU
Debugger) and saves it into the crash dump directory.
+ </div></li></ul></div><div class="para">
+ You can change the following backtrace generation parameters in the <code
class="filename">/etc/abrt/plugins/CCpp.conf</code> file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">Backtrace = <em
class="replaceable"><code>yes/no</code></em></code> —
Enables/Disables backtrace generation.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">BacktraceRemotes = <em
class="replaceable"><code>yes/no</code></em></code> —
For more information about this parameter, refer to <a class="xref"
href="configuring-centralized-crash-collection.html">Section 19.7,
“Configuring Centralized Crash Collection”</a>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">InstallDebugInfo = <em
class="replaceable"><code>yes/no</code></em></code> —
Enables/Disables the installation of <span
class="package">debuginfo</span> packages (useful if your network is
not available or it is firewalled).
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">ReadonlyLocalDebugInfoDirs =
/path1:/path2:...</code> — Specifies the paths of local repositories (available, for
example, through a network mount) that contain pre-downloaded <span
class="package">debuginfo</span> packages.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">DebugInfoCacheMB = <code
class="constant">4000</code></code> — Specifies the maximum size
of the cached <span class="package">debuginfo</span> packages in the
<code class="filename">/var/cache/abrt-di</code> directory.
+ </div></li></ul></div><div class="section"
id="troubleshooting"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="troubleshooting">19.4.1. Troubleshooting Backtrace
Generation</h3></div></div></div><div
class="para">
+ In some cases, a long delay in the <span
class="application"><strong>ABRT</strong></span> GUI
application occurs after choosing a crash and pressing the <span
class="guibutton"><strong>Report</strong></span> button. In
this case, open the <span
class="guibutton"><strong>Details</strong></span> in the
<span class="guilabel"><strong>Generating
backtrace</strong></span> window and examine the messages.
+ </div><div class="para">
+ The following is a typical output seen in the <span
class="guilabel"><strong>Generating
backtrace</strong></span> window:
+ </div><pre class="screen">Starting the debuginfo installation
+Getting list of build IDs
+12 missing debuginfos, getting package list from cache
+12 missing debuginfos, getting package list from repositories
+Downloading 7 packages
+Download 1/7: acl-debuginfo-2.2.49-6.fc13.x86_64
+Unpacking: acl-debuginfo-2.2.49-6.fc13.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/3d/e20df1db609bd9313b1dc440796004f95911fd.debug
+Download 2/7: firefox-debuginfo-3.6.7-1.fc13.x86_64
+Unpacking: firefox-debuginfo-3.6.7-1.fc13.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/3d/b29c9308cb276431ce8854a2d88cf83518afc6.debug
+Caching debuginfo:
+usr/lib/debug/.build-id/a3/86884285365c8288e4e761ec034fafaa1daee1.debug
+⋮
+Download 7/7: zlib-debuginfo-1.2.3-23.fc12.x86_64
+Unpacking: zlib-debuginfo-1.2.3-23.fc12.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/f7/933750da80f555321576e72b375caf7a3cc075.debug
+All needed debuginfos are present
+Generating backtrace</pre><div class="para">
+ This process is performed by the <span
class="application"><strong>/usr/bin/abrt-debuginfo-install</strong></span>
shell script. This script uses a temporary directory (e.g. <code
class="filename">/var/run/abrt/tmp-29177-1283344373</code>) for its
operations. Normally, this directory is removed when <span
class="application"><strong>abrt-debuginfo-install</strong></span>
exits.
+ </div><div class="para">
+ If the <span class="package">debuginfo</span> installation
hangs, or is unable to download anything, you may debug the problem by editing the
<span
class="application"><strong>abrt-debuginfo-install</strong></span>
script. Change the following parameters:
+ </div><pre class="programlisting">debug=false
+keep_tmp=false</pre><div class="para">
+ at the top of the script to:
+ </div><pre class="programlisting">debug=true
+keep_tmp=true</pre><div class="para">
+ The first parameter instructs <span
class="application"><strong>abrt-debuginfo-install</strong></span>
to be verbose, the second parameter instructs <span
class="application"><strong>abrt-debuginfo-install</strong></span>
to not delete the <code
class="filename">/var/run/abrt/tmp-NNN-NNN</code> directory. You can
examine the log files in this directory, they may contain useful error messages.
+ </div><div class="para">
+ <span
class="application"><strong>abrt-debuginfo-install</strong></span>
uses <span
class="application"><strong>yum</strong></span> and
<span
class="application"><strong>yumdownloader</strong></span>
to handle the <span class="package">debuginfo</span> packages. In
order to quickly check that your <span
class="application"><strong>yum</strong></span>
configuration does not cause any problems which prevent <span
class="application"><strong>abrt-debuginfo-install</strong></span>
from working properly, change to the <code
class="filename">/tmp</code> directory and run the following commands,
as <code class="systemitem">root</code>:
+ </div><pre class="screen">tmp]# <code
class="command">yum --enablerepo=*debuginfo* --quiet provides
/usr/bin/true</code>
+tmp]# <code class="command">yumdownloader --enablerepo=*debuginfo*
--quiet coreutils</code></pre><div class="para">
+ Both of these commands should complete successfully, with no error messages. The
second command should download the <code
class="filename">coreutils-*.rpm</code> file. If any error messages
appear, check your <span
class="application"><strong>yum</strong></span>
configuration files in the <code
class="filename">/etc/yum.repos.d/*</code> directory and the <code
class="filename">/etc/yum/*</code> directory. If any of these commands
hang, check that you do not have another instance of <span
class="application"><strong>yum</strong></span> running,
and that your network connection is working properly.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="configuring-plugins-in-the-gui.html"><strong>Prev</strong>19.3.3. Plugin
Configuration in the GUI</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch19s05.html"><strong>Next</strong>19.5. Using the Command
Line Interface</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png
new file mode 100644
index 0000000..9c331b6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png
b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png
new file mode 100644
index 0000000..6acf293
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png
new file mode 100644
index 0000000..8df5a42
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png
new file mode 100644
index 0000000..f4cb430
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt-alert.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt-alert.png
new file mode 100644
index 0000000..c95a6be
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt-alert.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt-event-configuration.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt-event-configuration.png
new file mode 100644
index 0000000..f213180
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt-event-configuration.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt.png
new file mode 100644
index 0000000..8a7f53d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/abrt.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-filters-available.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-filters-available.png
new file mode 100644
index 0000000..78050b5
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-filters-available.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-filters-end-user.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-filters-end-user.png
new file mode 100644
index 0000000..b909b93
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-filters-end-user.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-install.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-install.png
new file mode 100644
index 0000000..064d224
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-install.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-log.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-log.png
new file mode 100644
index 0000000..dcfaae7
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-log.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-package-group.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-package-group.png
new file mode 100644
index 0000000..2626ea1
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-package-group.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-remove.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-remove.png
new file mode 100644
index 0000000..3b8429c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software-remove.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software.png
new file mode 100644
index 0000000..219c461
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/add-remove-software.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-01.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-01.png
new file mode 100644
index 0000000..214673d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-01.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-02.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-02.png
new file mode 100644
index 0000000..2c6b837
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-02.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-03.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-03.png
new file mode 100644
index 0000000..bcebeee
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-03.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-04.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-04.png
new file mode 100644
index 0000000..67cfbda
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-04.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-05.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-05.png
new file mode 100644
index 0000000..fff1bfa
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-05.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-06.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-06.png
new file mode 100644
index 0000000..13d27ee
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-06.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-07.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-07.png
new file mode 100644
index 0000000..4b454ba
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/apache-mod_ssl-genkey-07.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/authconfig_LDAP_kerb.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/authconfig_LDAP_kerb.png
new file mode 100644
index 0000000..7268d86
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/authconfig_LDAP_kerb.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/authconfig_advanced.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/authconfig_advanced.png
new file mode 100644
index 0000000..53ddd7c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/authconfig_advanced.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/date-and-time-panel.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/date-and-time-panel.png
new file mode 100644
index 0000000..d3873b9
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/date-and-time-panel.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/date-and-time-settings.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/date-and-time-settings.png
new file mode 100644
index 0000000..260a043
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/date-and-time-settings.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/devicemngr.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/devicemngr.png
new file mode 100644
index 0000000..ebbd20b
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/devicemngr.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/gnome-print-queue.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/gnome-print-queue.png
new file mode 100644
index 0000000..a19d10c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/gnome-print-queue.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/hwbrowser.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/hwbrowser.png
new file mode 100644
index 0000000..a15d0bf
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/hwbrowser.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
new file mode 100644
index 0000000..bec8d23
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
new file mode 100644
index 0000000..9242e4a
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
b/public_html/en-US/Fedora/15/html/Deployment_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/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png
new file mode 100644
index 0000000..e9f5b66
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration.png
new file mode 100644
index 0000000..2b250b7
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/kdump-kernel_dump_configuration.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/oprof-start-config.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/oprof-start-config.png
new file mode 100644
index 0000000..03b8701
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/oprof-start-config.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/oprof-start-setup.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/oprof-start-setup.png
new file mode 100644
index 0000000..5f0c64b
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/oprof-start-setup.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/print_conf_window.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/print_conf_window.png
new file mode 100644
index 0000000..ba58c70
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/print_conf_window.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-add-printer.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-add-printer.png
new file mode 100644
index 0000000..9a25612
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-add-printer.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config1.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config1.png
new file mode 100644
index 0000000..5f67b4d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config1.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config2.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config2.png
new file mode 100644
index 0000000..9e05c23
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config2.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config3.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config3.png
new file mode 100644
index 0000000..47e483c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config3.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config4.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config4.png
new file mode 100644
index 0000000..a2387a8
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config4.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config5.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config5.png
new file mode 100644
index 0000000..9074579
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config5.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config6.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config6.png
new file mode 100644
index 0000000..152a760
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-config6.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-ipp.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-ipp.png
new file mode 100644
index 0000000..55e8e89
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-ipp.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-jetdirect.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-jetdirect.png
new file mode 100644
index 0000000..5884d66
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-jetdirect.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-lpd.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-lpd.png
new file mode 100644
index 0000000..5ea620c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-lpd.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-main.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-main.png
new file mode 100644
index 0000000..57fb07d
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-main.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-select-driver.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-select-driver.png
new file mode 100644
index 0000000..6b27ff1
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-select-driver.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-select-model.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-select-model.png
new file mode 100644
index 0000000..a8e49f8
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-select-model.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-smb.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-smb.png
new file mode 100644
index 0000000..26b7939
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/printconf-smb.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-language.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-language.png
new file mode 100644
index 0000000..e846eaf
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-language.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts-add.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts-add.png
new file mode 100644
index 0000000..607a1aa
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts-add.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts-indicator.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts-indicator.png
new file mode 100644
index 0000000..c61e692
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts-indicator.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts.png
new file mode 100644
index 0000000..448c00c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/region-and-language-layouts.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-basic.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-basic.png
new file mode 100644
index 0000000..c0dffc3
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-basic.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-create-share.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-create-share.png
new file mode 100644
index 0000000..14bc8d5
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-create-share.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-security.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-security.png
new file mode 100644
index 0000000..fb71f96
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-security.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-users.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-users.png
new file mode 100644
index 0000000..8de4375
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba-users.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba.png
new file mode 100644
index 0000000..27abf11
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/s-c-samba.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/samba-nautilus-domain.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/samba-nautilus-domain.png
new file mode 100644
index 0000000..3b8e5a9
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/samba-nautilus-domain.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update-preferences.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update-preferences.png
new file mode 100644
index 0000000..64f5b91
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update-preferences.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update-software-sources.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update-software-sources.png
new file mode 100644
index 0000000..3ab48d5
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update-software-sources.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update.png
new file mode 100644
index 0000000..f1b066b
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/software-update.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-passphrase-prompt.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-passphrase-prompt.png
new file mode 100644
index 0000000..b8b7b11
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-passphrase-prompt.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications-add.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications-add.png
new file mode 100644
index 0000000..517567e
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications-add.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications-check.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications-check.png
new file mode 100644
index 0000000..a3d8599
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications-check.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications.png
new file mode 100644
index 0000000..bfa9578
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/ssh-startup-applications.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/switchmail-gui.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/switchmail-gui.png
new file mode 100644
index 0000000..380d884
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/switchmail-gui.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-add.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-add.png
new file mode 100644
index 0000000..3690469
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-add.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-alerts.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-alerts.png
new file mode 100644
index 0000000..db4301a
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-alerts.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-define.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-define.png
new file mode 100644
index 0000000..3b37e73
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-define.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-enable.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-enable.png
new file mode 100644
index 0000000..06eb44c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-enable.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-manage.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-manage.png
new file mode 100644
index 0000000..285f83f
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer-filters-manage.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer.png
new file mode 100644
index 0000000..7c3bdd6
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-log-viewer.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-file-systems.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-file-systems.png
new file mode 100644
index 0000000..4f6050c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-file-systems.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-processes.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-processes.png
new file mode 100644
index 0000000..f218181
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-processes.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-resources.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-resources.png
new file mode 100644
index 0000000..e56a166
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/system-monitor-resources.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-create.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-create.png
new file mode 100644
index 0000000..652df07
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-create.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-password-change.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-password-change.png
new file mode 100644
index 0000000..da264e4
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-password-change.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-remove.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-remove.png
new file mode 100644
index 0000000..727df90
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts-remove.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts.png
new file mode 100644
index 0000000..633b363
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-accounts.png differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-add-group.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-add-group.png
new file mode 100644
index 0000000..d59e89c
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-add-group.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-add-user.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-add-user.png
new file mode 100644
index 0000000..af1eb92
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-add-user.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-edit-group.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-edit-group.png
new file mode 100644
index 0000000..594ab85
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-edit-group.png
differ
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-edit-user.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-edit-user.png
new file mode 100644
index 0000000..a49ff97
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager-edit-user.png
differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager.png
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager.png
new file mode 100644
index 0000000..a50cad2
Binary files /dev/null and
b/public_html/en-US/Fedora/15/html/Deployment_Guide/images/user-manager.png differ
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/index.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/index.html
new file mode 100644
index 0000000..26965b5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/index.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>Deployment Guide</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><meta name="description" content="The Deployment Guide documents
relevant information regarding the deployment, configuration, and administration of Fedora
15. It is oriented towards system administrators with a basic understanding of the
system." /><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="next"
href="pr01.html" title="Preface" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
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>Next</strong></a></li></ul><div
xml:lang="en-US" class="book" id="id408939"
lang="en-US"><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">15</span></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h1 id="id408939"
class="title">Deployment Guide</h1></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><h2
class="subtitle">Deployment, Configuration and Administration of Fedora
15</h2></div><p class="edition">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="en-US"
class="authorgroup" lang="en-US"><div
class="author"><h3 class="author"><span
class="firstname">Jaromír</span> <span
class="surname">Hradílek</span></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:jhradile@redhat.com">jhradile@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="firstname">Douglas</span> <span
class="surname">Silas</span></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:dhensley@redhat.com">dhensley@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="firstname">Martin</span> <span
class="surname">Prpi
č</span></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@redhat.com">mprpic@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="firstname">Eva</span> <span
class="surname">Kopalová</span></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:ekopalov@redhat.com">ekopalov@redhat.com</a></code></div><div
class="author"><h3 class="author"><span
class="firstname">John</span> <span
class="surname">Ha</span></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="firstname">David</span>
<span class="surname">O'Brien</span></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="firstname">Michael</span>
<span class="surname">Hideo</span></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="firstname">Don</span>
<span class="surname">Domingo</span></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="id627778" class="legalnotice"><h1
class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2011 Red Hat,
Inc. and others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative
Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An
explanation of CC-BY-SA is available at <a
href="http://creativecommons.org/licenses/by-sa/3.0/">http:/...;.
The original authors of this document, and Red Hat, designate the Fedora Project as the
"Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if
you distribute this document or an adaptation of it, you must provide the URL for the
original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not
to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the
Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States
and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a
href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines"...;.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark
of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of
Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon
Graphics International Corp. or its subsidiaries in the United States and/or other
countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark
of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div
font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold"
font-size="12pt" text-align="center"><div
class="abstract"><h6>Abstract</h6><div
class="para">
+ The <em class="citetitle">Deployment Guide</em> documents
relevant information regarding the deployment, configuration, and administration of Fedora
15. It is oriented towards system administrators with a basic understanding of the
system.
+ </div></div></div></div><hr /></div><div
class="toc"><dl><dt><span class="preface"><a
href="pr01.html">Preface</a></span></dt><dd><dl><dt><span
class="section"><a
href="pr01.html#sect-Preface-Target_Audience">1. Target
Audience</a></span></dt><dt><span
class="section"><a
href="sect-Preface-Book_Organization.html">2. How to Read this
Book</a></span></dt><dt><span
class="section"><a href="pr01s03.html">3. Document
Conventions</a></span></dt><dd><dl><dt><span
class="section"><a href="pr01s03.html#id426550">3.1.
Typographic Conventions</a></span></dt><dt><span
class="section"><a href="pr01s03s02.html">3.2. Pull-quote
Conventions</a></span></dt><dt><span
class="section"><a href="pr01s03s03.html">3.3. Notes and
Warnings</a></span></dt></dl></dd><dt><span
class="section"><a href="sect-Preface-Feedback.html">4.
Feedback</a></span></dt><dt><span
class="section"><a href="pref-Acknowledgments.html">5.
Acknowledgments</a></span></dt></dl></dd><dt><span
class="part"><a href="part-Basic
_System_Configuration.html">I. Basic System
Configuration</a></span></dt><dd><dl><dt><span
class="chapter"><a
href="ch-Language_and_Keyboard_Configuration.html">1. Language and Keyboard
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Language_and_Keyboard_Configuration.html#sect-Language_and_Keyboard_Configuration-Language">1.1.
Changing the Language</a></span></dt><dt><span
class="section"><a
href="sect-Language_and_Keyboard_Configuration-Layouts.html">1.2. Changing
the Keyboard
Layout</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="ch-Date_and_Time_Configuration.html">2. Date and Time
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">2.1.
Date and Time Configuration Tool</a></span></dt><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html">2.2.
Command Line Configuration</a></span></dt
<dd><dl><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">2.2.1.
Configuring the Date and Time</a></span></dt><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">2.2.2.
Configuring the Network Time
Protocol</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Additional_Resources.html">2.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Additional_Resources.html#sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation">2.3.1.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Managing_Users_and_Groups.html">3. Managing Users and
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-Managing_Users_and_G
roups.html#sect-Managing_Users_and_Groups-User_Accounts">3.1. User Accounts
Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.1.1.
Configuring an Account</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">3.1.2.
Adding a New User</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.1.3.
Removing a User</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-configui.html">3.2. User
Manager Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-configui.html#s2-redhat-config-users-user-new">3.2.1. Adding a
New User</a></span></dt><dt><span
class="section"><a
href="s2-redhat-config-users-group-new.html">3.2.2. Adding a New
Group</a></span></dt
<dt><span class="section"><a
href="s2-redhat-config-users-group-properties.html">3.2.3. Modifying Group
Properties</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-tools.html">3.3. User and
Group Management
Tools</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-tools.html#s2-users-cmd-line">3.3.1. Command Line
Configuration</a></span></dt><dt><span
class="section"><a
href="s2-redhat-config-users-process.html">3.3.2. Explaining the
Process</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-users-groups-standard-users.html">3.4. Standard
Users</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-standard-groups.html">3.5. Standard
Groups</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-private-groups.html">3.6. User Private
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-groups-private-groups.html#s2-users-groups-rationale">3.6.1.
Group Directories</a></span></dt></dl></d
d><dt><span class="section"><a
href="s1-users-groups-shadow-utilities.html">3.7. Shadow
Passwords</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-additional-resources.html">3.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">3.8.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="part-Package_Management.html">II.
Package Management</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. Checking For
and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-yum.html#sec-Checking_For_Updates">4.1.1. Checking For
Updates</a></span></dt><dt><span
class="section"><a
href="ch-yum.html#sec-Updating_Packages">4.1.2. Updating
Packages</a></span></dt><dt
<span class="section"><a
href="ch-yum.html#sec-Preserving_Configuration_File_Changes">4.1.3.
Preserving Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html">4.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">4.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="sec-Listing_Packages.html">4.2.2.
Listing Packages</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Package_Information.html">4.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="sec-Installing.html">4.2.4.
Installing Packages</a></span></dt><dt><span
class="section"><a href="sec-Removing.html">4.2.5. Removing
Packages</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Configuring_Yum_and_Yum_Repositories.html">4.3. Configuring Yum and
Yum Repositories</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.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="sec-Setting_repository_Options.html">4.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="sec-Using_Yum_Variables.html">4.3.3.
Using Yum Variables</a></span></dt><dt><span
class="section"><a
href="sec-Creating_a_Yum_Repository.html">4.3.4. Creating a Yum
Repository</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Yum_Plugins.html">4.4. Yum
Plugins</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.
Enabling, Configuring and Disabling Yum
Plugins</a></span></dt><dt><span
class="section"><a
href="sec-Installing_More_Yum_Plugins.html">4.4.2. Installing Additional Yum
Plugins</a></span></dt><dt><span
class="section"><a href="sec-Plugin_Descriptions.ht
ml">4.4.3. Plugin
Descriptions</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Additional_Resources.html">4.5.
Additional
Resources</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.
Updating Packages with Software
Update</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-PackageKit.html#sec-Setting_preferences_for_checking_for_updates">5.1.1.
Setting the Update-Checking Interval</a></span></dt><dt><span
class="section"><a
href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">5.1.2.
Setting the Software
Sources</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Using_Add_Remove_Software.html">5.2. Using Add/Remove
Software</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repo
sitories">5.2.1. Refreshing Software Sources (Yum
Repositories)</a></span></dt><dt><span
class="section"><a
href="sec-Finding_Packages_with_Filters.html">5.2.2. Finding Packages with
Filters</a></span></dt><dt><span
class="section"><a
href="sec-Installing_and_Removing_Packages_and_Dependencies.html">5.2.3.
Installing and Removing Packages (and
Dependencies)</a></span></dt><dt><span
class="section"><a
href="sec-Installing_and_Removing_Package_Groups.html">5.2.4. Installing and
Removing Package Groups</a></span></dt><dt><span
class="section"><a
href="sec-Viewing_the_Transaction_Log.html">5.2.5. Viewing the Transaction
Log</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-PackageKit_Architecture.html">5.3. PackageKit
Architecture</a></span></dt><dt><span
class="section"><a
href="ch-Graphical_Package_Management-sec-Additional_Resources.html">5.4.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a href="part-Networking.html">III. Netwo
rking</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-Network_Interfaces.html">6.
Network Interfaces</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Network_Interfaces.html#s1-networkscripts-files">6.1. Network
Configuration Files</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-interfaces.html">6.2. Interface Configuration
Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">6.2.1.
Ethernet Interfaces</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-chan.html">6.2.2. Channel Bonding
Interfaces</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-alias.html">6.2.3. Alias and Clone
Files</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-ppp0.html">6.2.4. Dialup
Interfaces</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-other.html">6.2.5. O
ther Interfaces</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-networkscripts-control.html">6.3.
Interface Control Scripts</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-static-routes.html">6.4. Configuring Static
Routes</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-functions.html">6.5. Network Function
Files</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-resources.html">6.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-networkscripts-resources.html#s2-networkscripts-docs-inst">6.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="part-Infrastructure_Services.html">IV.
Infrastructure
Services</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-Services_and_Daemons.html">7.
Services and
Daemons</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s1-services-configu
ring">7.1. Configuring
Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">7.1.1.
Enabling the Service</a></span></dt><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">7.1.2.
Disabling the
Service</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-services-running.html">7.2.
Running Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-running.html#s3-services-running-checking">7.2.1. Checking
the Service Status</a></span></dt><dt><span
class="section"><a
href="s3-services-running-running.html">7.2.2. Running the
Service</a></span></dt><dt><span
class="section"><a
href="s3-services-running-stopping.html">7.2.3. Stopping the
Service</a></span></dt><dt><span
class="section"><a
href="s3-services-running-restarting.html">7.2.4. Restarting the
Service</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-s
ervices-additional-resources.html">7.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-additional-resources.html#s2-services-additional-resources-installed">7.3.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-services-additional-resources-books.html">7.3.2. Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_Authentication.html">8. Configuring
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">8.1.
The Authentication Configuration
Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1.
Identity & Authentication</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_
Tool-Advanced_Options">8.1.2. Advanced
Options</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3.
Command Line
Version</a></span></dt></dl></dd><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Introduction.html">8.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">8.2.1.
What is SSSD?</a></span></dt><dt><span
class="section"><a
href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html">8.2.2. SSSD
Features</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Setting_Up_SSSD.html">8.2.3. Setting Up
SSSD</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Configuring_Services.html">8.2.4. Configuring
Services</a></span></dt><dt><span
class="section"><a href="chap-SSSD_User_Guide-Configuring_
Domains.html">8.2.5. Configuring
Domains</a></span></dt><dt><span
class="section"><a
href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">8.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">8.2.7.
Configuring a Proxy Domain</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Troubleshooting.html">8.2.8.
Troubleshooting</a></span></dt><dt><span
class="section"><a
href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">8.2.9.
SSSD Configuration File
Format</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-OpenSSH.html">9.
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OpenSSH.html#s1-ssh-protocol">9.1. The SSH
Protocol</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-why">9.1.1.
Why Use
SSH?</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-features">9.1.2. Main
Features</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-versions">9.1.3. Protocol
Versions</a></span></dt><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">9.1.4.
Event Sequence of an SSH
Connection</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-configuration.html">9.2. An
OpenSSH
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">9.2.1.
Configuration Files</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-sshd.html">9.2.2. Starting an OpenSSH
Server</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-requiring.html">9.2.3. Requiring SSH for Remote
Connections</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-keypairs.html">9.2.4. Using a Key-Based
Authentication</a></span></dt></dl
</dd><dt><span class="section"><a
href="s1-ssh-clients.html">9.3. OpenSSH
Clients</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-clients.html#s2-ssh-clients-ssh">9.3.1. Using the ssh
Utility</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-scp.html">9.3.2.
Using the <code class="command">scp</code>
Utility</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-sftp.html">9.3.3.
Using the <code class="command">sftp</code>
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-beyondshell.html">9.4. More
Than a Secure
Shell</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">9.4.1. X11
Forwarding</a></span></dt><dt><span
class="section"><a
href="s2-ssh-beyondshell-tcpip.html">9.4.2. Port
Forwarding</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-openssh-additional-resources.html">9.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="
section"><a
href="s1-openssh-additional-resources.html#s2-openssh-installed-docs">9.5.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-openssh-useful-websites.html">9.5.2. Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a href="part-Servers.html">V.
Servers</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-DHCP_Servers.html">10. DHCP
Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DHCP_Servers.html#s1-dhcp-why">10.1. Why Use
DHCP?</a></span></dt><dt><span
class="section"><a
href="s1-dhcp-configuring-server.html">10.2. Configuring a DHCP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-dhcp-configuring-server.html#config-file">10.2.1. Configuration
File</a></span></dt><dt><span
class="section"><a href="lease-database.html">10.2.2. Lease
Database</a></span></dt><dt><span
class="section"><a href="ch10s02s03.html">10.2.3. Starting
and Stopping the Server</a></sp
an></dt><dt><span class="section"><a
href="dhcp-relay-agent.html">10.2.4. DHCP Relay
Agent</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-dhcp-configuring-client.html">10.3. Configuring a DHCP
Client</a></span></dt><dt><span
class="section"><a
href="sect-Configuring_a_Multihomed_DHCP_Server.html">10.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">10.4.1.
Host
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">10.5.
DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span
class="section"><a
href="s1-dhcp-additional-resources.html">10.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">10.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-DNS_Servers.html">1
1. DNS Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNS_Servers.html#s1-Introduction_to_DNS">11.1. Introduction to
DNS</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-zones">11.1.1. Nameserver
Zones</a></span></dt><dt><span
class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">11.1.2. Nameserver
Types</a></span></dt><dt><span
class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-bind">11.1.3. BIND as a
Nameserver</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-BIND.html">11.2.
BIND</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-BIND.html#s2-bind-namedconf">11.2.1. Configuring the named
Service</a></span></dt><dt><span
class="section"><a href="s2-bind-zone.html">11.2.2. Editing
Zone Files</a></span></dt><dt><span
class="section"><a href="s2-bind-rndc.html">11.2.3. Using the
rndc Utility</a></span></dt><dt><span
class="section"><a href="s2-b
ind-dig.html">11.2.4. Using the dig
Utility</a></span></dt><dt><span
class="section"><a href="s2-bind-features.html">11.2.5.
Advanced Features of BIND</a></span></dt><dt><span
class="section"><a href="s2-bind-mistakes.html">11.2.6.
Common Mistakes to Avoid</a></span></dt><dt><span
class="section"><a
href="s2-bind-additional-resources.html">11.2.7. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Web_Servers.html">12. Web
Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">12.1. The Apache HTTP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-features">12.1.1. New
Features</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-changes">12.1.2. Notable
Changes</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-migrating">12.1.3. Updating the
Config
uration</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-running">12.1.4. Running the httpd
Service</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-editing">12.1.5. Editing the
Configuration Files</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-dso">12.1.6. Working with
Modules</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-virtualhosts">12.1.7. Setting Up Virtual
Hosts</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-mod_ssl">12.1.8. Setting Up an SSL
Server</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-resources">12.1.9. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Mail_Servers.html">13. Mail
Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s1-email-protocols">13.1. Email
Protocols</a></span></dt><
dd><dl><dt><span class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-send">13.1.1. Mail Transport
Protocols</a></span></dt><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-client">13.1.2. Mail Access
Protocols</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-types.html">13.2. Email
Program
Classifications</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-types.html#s2-email-types-mta">13.2.1. Mail Transport
Agent</a></span></dt><dt><span
class="section"><a href="s2-email-types-mda.html">13.2.2.
Mail Delivery Agent</a></span></dt><dt><span
class="section"><a href="s2-email-types-mua.html">13.2.3.
Mail User Agent</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mta.html">13.3. Mail
Transport Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mta.html#s2-email-mta-postfix">13.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="s2-email-mta-sendmail.h
tml">13.3.2. Sendmail</a></span></dt><dt><span
class="section"><a href="s2-email-mta-fetchmail.html">13.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="s2-email-switchmail.html">13.3.4.
Mail Transport Agent (MTA)
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mda.html">13.4. Mail
Delivery Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mda.html#s2-email-procmail-configuration">13.4.1. Procmail
Configuration</a></span></dt><dt><span
class="section"><a
href="s2-email-procmail-recipes.html">13.4.2. Procmail
Recipes</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mua.html">13.5. Mail User
Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mua.html#s2-email-security">13.5.1. Securing
Communication</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-email-additional-resources.html">13.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="s
ection"><a
href="s1-email-additional-resources.html#s2-email-installed-docs">13.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-email-useful-websites.html">13.6.2. Useful
Websites</a></span></dt><dt><span
class="section"><a href="s2-email-related-books.html">13.6.3.
Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Directory_Servers.html">14.
Directory Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s1-OpenLDAP">14.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-introduction">14.1.1. Introduction to
LDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-installation">14.1.2. Installing the
OpenLDAP Suite</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-configuration">14.1.3. Configuring an
OpenLDAP Server</a></span></dt><dt><span class="se
ction"><a
href="ch-Directory_Servers.html#s2-ldap-running">14.1.4. Running an OpenLDAP
Server</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-pam">14.1.5. Configuring a System to
Authenticate Using OpenLDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-resources">14.1.6. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-File_and_Print_Servers.html">15.
File Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s1-Samba">15.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#samba-rgs-overview">15.1.1. Introduction
to Samba</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-daemons">15.1.2. Samba Daemons
and Related Services</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-connect-share">15.1.3
. Connecting to a Samba Share</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-configuring">15.1.4.
Configuring a Samba Server</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-startstop">15.1.5. Starting and
Stopping Samba</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-servers">15.1.6. Samba Server
Types and the <code class="filename">smb.conf</code>
File</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">15.1.7. Samba
Security Modes</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">15.1.8. Samba
Account Information Databases</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">15.1.9. Samba
Network Browsing</a></span></dt><dt><span
class="section"><a href="ch-File_and_Print_Servers.html
#s2-samba-cups">15.1.10. Samba with CUPS Printing
Support</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-programs">15.1.11. Samba
Distribution Programs</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-resources">15.1.12. Additional
Resources</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-FTP.html">15.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-FTP.html#s2-ftp-protocol">15.2.1.
The File Transfer Protocol</a></span></dt><dt><span
class="section"><a href="s2-ftp-servers.html">15.2.2. FTP
Servers</a></span></dt><dt><span
class="section"><a href="s3-ftp-vsftpd-conf.html">15.2.3.
Files Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-start.html">15.2.4. Starting and Stopping <code
class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-conf.html">15.2.5.
<code class="command">vsftpd</code> Configuration
Options</a></span></dt><dt><span
class="section"><a href="s2-ftp-resources.html">15.2.6.
Additional
Resources</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="part"><a
href="part-Monitoring_and_Automation.html">VI. Monitoring and
Automation</a></span></dt><dd><dl><dt><span
class="chapter"><a href="ch-System_Monitoring_Tools.html">16.
System Monitoring
Tools</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">16.1.
System Processes</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-memory-usage.html">16.2.
Memory Usage</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-filesystems.html">16.3.
File Systems</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-hardware.html">16.4.
Hardware</a></span></dt><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html">16.5. Additional
Resources</a></span></dt><dd><
dl><dt><span class="section"><a
href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.5.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Viewing_and_Managing_Log_Files.html">17. Viewing and Managing Log
Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s1-configuring-rsyslog">17.1.
Configuring
rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-global-directives">17.1.1.
Global Directives</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-modules">17.1.2.
Modules</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-rules">17.1.3.
Rules</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-rsyslog-cmd-options">17.1.4.
<span
class="application"><strong>rsyslog</strong></span> Command
L
ine
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-logfiles-locating.html">17.2.
Locating Log Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-logfiles-locating.html#configuring-logrotate">17.2.1. Configuring
logrotate</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-logfiles-viewing.html">17.3.
Viewing Log Files</a></span></dt><dt><span
class="section"><a href="s1-logfiles-adding.html">17.4.
Adding a Log File</a></span></dt><dt><span
class="section"><a href="s1-logfiles-examining.html">17.5.
Monitoring Log Files</a></span></dt><dt><span
class="section"><a
href="s1-log-files-additional-resources.html">17.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-log-files-additional-resources.html#s2-log-files-installed-docs">17.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-log-files-useful-websites.html">17.6.2. Useful
Websites</a></span></dt></dl></dd
</dl></dd><dt><span
class="chapter"><a href="ch-Automating_System_Tasks.html">18.
Automating System
Tasks</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">18.1. Cron
and Anacron</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-service">18.1.1.
Starting and Stopping the Service</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.2.
Configuring Anacron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">18.1.3.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">18.1.4.
Controlling Access to Cron</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">18.1.5.
Black/White Listing of Cron Job
s</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-autotasks-at-batch.html">18.2. At
and Batch</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-at-batch.html#s2-autotasks-at-configuring">18.2.1.
Configuring At Jobs</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-batch-configuring.html">18.2.2. Configuring Batch
Jobs</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-viewing.html">18.2.3. Viewing Pending
Jobs</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-commandline-options.html">18.2.4. Additional Command Line
Options</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-controlling-access.html">18.2.5. Controlling
Access to At and Batch</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-service.html">18.2.6. Starting and Stopping the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html">18.3. Ad
ditional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">18.3.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-abrt.html">19. Automatic
Bug-Reporting Tool
(ABRT)</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-abrt.html#id443090">19.1.
Overview</a></span></dt><dt><span
class="section"><a href="ch19s02.html">19.2. Installing and
Running ABRT</a></span></dt><dt><span
class="section"><a href="abrt-plugins.html">19.3. ABRT
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a
href="abrt-plugins.html#analyzer-plugins">19.3.1. Analyzer
Plugins</a></span></dt><dt><span
class="section"><a href="reporter-plugins.html">19.3.2.
Reporter Plugins</a></span></dt><dt><span
class="section"><a
href="configuring-plugins-in-the-gui.html">19.3.3. Plugin Configuration in
the GUI</a></span></dt></dl></dd><dt><span
class="section"><a href="g
enerating-backtrace.html">19.4. Generating
Backtraces</a></span></dt><dd><dl><dt><span
class="section"><a
href="generating-backtrace.html#troubleshooting">19.4.1. Troubleshooting
Backtrace
Generation</a></span></dt></dl></dd><dt><span
class="section"><a href="ch19s05.html">19.5. Using the
Command Line
Interface</a></span></dt><dd><dl><dt><span
class="section"><a href="ch19s05.html#id483939">19.5.1.
Viewing Crashes</a></span></dt><dt><span
class="section"><a href="ch19s05s02.html">19.5.2. Reporting
Crashes</a></span></dt><dt><span
class="section"><a href="ch19s05s03.html">19.5.3. Deleting
Crashes</a></span></dt></dl></dd><dt><span
class="section"><a href="configuring.html">19.6. Configuring
ABRT</a></span></dt><dt><span
class="section"><a
href="configuring-centralized-crash-collection.html">19.7. Configuring
Centralized Crash
Collection</a></span></dt><dd><dl><dt><span
class="section"><a
href="configuring-centralized-crash-collection.html#id462013">19.7.1. Testing
ABRT's Cras
h Detection</a></span></dt><dt><span
class="section"><a href="testing-upload-method.html">19.7.2.
Testing the Upload
Method</a></span></dt></dl></dd><dt><span
class="section"><a
href="configuring-automatic-reporting.html">19.8. Configuring Automatic
Reporting</a></span></dt></dl></dd></dl></dd><dt><span
class="part"><a
href="part-Kernel_Module_and_Driver_Configuration.html">VII. Kernel, Module
and Driver
Configuration</a></span></dt><dd><dl><dt><span
class="chapter"><a
href="ch-Manually_Upgrading_the_Kernel.html">20. Manually Upgrading the
Kernel</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">20.1.
Overview of Kernel Packages</a></span></dt><dt><span
class="section"><a href="s1-kernel-preparing.html">20.2.
Preparing to Upgrade</a></span></dt><dt><span
class="section"><a href="s1-kernel-download.html">20.3.
Downloading the Upgraded Kernel</a></span></dt><dt><span
class="section"><a href="s1-kernel-perform-up
grade.html">20.4. Performing the
Upgrade</a></span></dt><dt><span
class="section"><a
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">20.5. Verifying the
Initial RAM Disk Image</a></span></dt><dt><span
class="section"><a href="s1-kernel-boot-loader.html">20.6.
Verifying the Boot
Loader</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">20.6.1.
Configuring the GRUB Boot Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-iseries.html">20.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-pseries.html">20.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">21. 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">21.1.
Listing C
urrently-Loaded Modules</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Information_About_a_Module.html">21.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="sec-Loading_a_Module.html">21.3.
Loading a Module</a></span></dt><dt><span
class="section"><a href="sec-Unloading_a_Module.html">21.4.
Unloading a Module</a></span></dt><dt><span
class="section"><a
href="sec-Setting_Module_Parameters.html">21.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="sec-Persistent_Module_Loading.html">21.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="sec-Specific_Kernel_Module_Capabilities.html">21.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">21.7.1.
Using Multiple Ethernet Cards</a></span></dt><dt><span
class="section"><a href="sec-Using_Channel_B
onding.html">21.7.2. Using Channel
Bonding</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html">21.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html#s2-kernel-modules-additional-resources-installed">21.8.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-kernel-modules-additional-resources-websites.html">21.8.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-kdump.html">22. The kdump Crash
Recovery Service</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-kdump.html#s1-kdump-configuration">22.1. Configuring the kdump
Service</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-gui">22.1.1. Using the Kernel Dump
Configuration Utility</a></span></dt><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-cli">22.1
.2. Configuring kdump on the Command
Line</a></span></dt><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-testing">22.1.3. Testing the
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-kdump-crash.html">22.2. Analyzing
the Core Dump</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kdump-crash.html#s2-kdump-crash-running">22.2.1. Running the crash
Utility</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-log.html">22.2.2.
Displaying the Message Buffer</a></span></dt><dt><span
class="section"><a
href="s2-kdump-crash-backtrace.html">22.2.3. Displaying a
Backtrace</a></span></dt><dt><span
class="section"><a
href="s2-kdump-crash-processes.html">22.2.4. Displaying a Process
Status</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-memory.html">22.2.5.
Displaying Virtual Memory Information</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-files.html">22.2.6.
Displaying Open Fil
es</a></span></dt><dt><span class="section"><a
href="s2-kdump-crash-exit.html">22.2.7. Exiting the
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-kdump-resources.html">22.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kdump-resources.html#s2-kdump-resources-installed">22.3.1. Installed
Documentation</a></span></dt><dt><span
class="section"><a
href="s2-kdump-resources-online.html">22.3.2. Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span
class="appendix"><a href="ch-RPM.html">A.
RPM</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-RPM.html#s1-rpm-design">A.1. RPM
Design Goals</a></span></dt><dt><span
class="section"><a href="s1-rpm-using.html">A.2. Using
RPM</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-rpm-using.html#s2-rpm-finding">A.2.1. Finding RPM
Packages</a></span></dt><dt><span
class="section"><a
href="sec-Installing_and_Upgrading.html">A.2.2. Installing and U
pgrading</a></span></dt><dt><span
class="section"><a
href="sec-Configuration_File_Changes.html">A.2.3. Configuration File
Changes</a></span></dt><dt><span
class="section"><a href="s2-rpm-uninstalling.html">A.2.4.
Uninstalling</a></span></dt><dt><span
class="section"><a href="s2-rpm-freshening.html">A.2.5.
Freshening</a></span></dt><dt><span
class="section"><a href="s2-rpm-querying.html">A.2.6.
Querying</a></span></dt><dt><span
class="section"><a href="s2-rpm-verifying.html">A.2.7.
Verifying</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-check-rpm-sig.html">A.3. Checking
a Package's
Signature</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-check-rpm-sig.html#s2-keys-importing">A.3.1. Importing
Keys</a></span></dt><dt><span
class="section"><a href="s2-keys-checking.html">A.3.2.
Verifying Signature of
Packages</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-rpm-impressing.html">A.4.
Practical and Common Examples of RPM Usage</a></span
</dt><dt><span class="section"><a
href="s1-rpm-additional-resources.html">A.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-rpm-additional-resources.html#s2-rpm-installed-docs">A.5.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a href="s2-rpm-useful-websites.html">A.5.2.
Useful Websites</a></span></dt><dt><span
class="section"><a href="s2-rpm-related-books.html">A.5.3.
Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="appendix"><a href="ch-The_sysconfig_Directory.html">B.
The sysconfig
Directory</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s1-sysconfig-files">B.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">B.1.1.
/etc/sysconfig/arpwatch </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-authconfig">B.1.2
.
/etc/sysconfig/authconfig </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-autofs">B.1.3.
/etc/sysconfig/autofs </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-clock">B.1.4.
/etc/sysconfig/clock </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-dhcpd">B.1.5.
/etc/sysconfig/dhcpd </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-firewall">B.1.6.
/etc/sysconfig/firstboot </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-i18n">B.1.7.
/etc/sysconfig/i18n </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-init">B.1.8.
/etc/sysconfig/init </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-ip6tables">B.1.9.
/etc/sysconfig/ip6tables-config </a></span></dt>
<dt><span class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-kybd">B.1.10.
/etc/sysconfig/keyboard </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-ldap">B.1.11.
/etc/sysconfig/ldap </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-named">B.1.12.
/etc/sysconfig/named </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-network">B.1.13.
/etc/sysconfig/network </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-ntpd">B.1.14.
/etc/sysconfig/ntpd </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-quagga">B.1.15.
/etc/sysconfig/quagga </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-radvd">B.1.16.
/etc/sysconfig/radvd </a></span></dt><dt><span
class="section"><a href="ch-The_sysconfig_Di
rectory.html#s2-sysconfig-samba">B.1.17. /etc/sysconfig/samba
</a></span></dt><dt><span class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-selinux">B.1.18.
/etc/sysconfig/selinux </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-sendmail">B.1.19.
/etc/sysconfig/sendmail </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-spamd">B.1.20.
/etc/sysconfig/spamassassin </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-squid">B.1.21.
/etc/sysconfig/squid </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-rcu">B.1.22.
/etc/sysconfig/system-config-users </a></span></dt><dt><span
class="section"><a
href="ch-The_sysconfig_Directory.html#s2-sysconfig-vncservers">B.1.23.
/etc/sysconfig/vncservers </a></span></dt><dt><span
class="section"><a href="ch-The_sysconfig_Directory.html#s2-sys
config-xinetd">B.1.24. /etc/sysconfig/xinetd
</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-sysconfig-etcsysconf-dir.html">B.2. Directories in the
/etc/sysconfig/ Directory</a></span></dt><dt><span
class="section"><a
href="s1-sysconfig-additional-resources.html">B.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysconfig-additional-resources.html#s2-sysconfig-installed-documentation">B.3.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="appendix"><a href="ch-proc.html">C. The proc File
System</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-proc.html#s1-proc-virtual">C.1. A
Virtual File
System</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-proc.html#s2-proc-viewing">C.1.1.
Viewing Virtual Files</a></span></dt><dt><span
class="section"><a href="ch-proc.html#s2-proc-change">C.1.2.
Changing Virtual
Files</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-pro
c-topfiles.html">C.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">C.2.1. /proc/buddyinfo
</a></span></dt><dt><span class="section"><a
href="s2-proc-cmdline.html">C.2.2. /proc/cmdline
</a></span></dt><dt><span class="section"><a
href="s2-proc-cpuinfo.html">C.2.3. /proc/cpuinfo
</a></span></dt><dt><span class="section"><a
href="s2-proc-crypto.html">C.2.4. /proc/crypto
</a></span></dt><dt><span class="section"><a
href="s2-proc-devices.html">C.2.5. /proc/devices
</a></span></dt><dt><span class="section"><a
href="s2-proc-dma.html">C.2.6. /proc/dma
</a></span></dt><dt><span class="section"><a
href="s2-proc-execdomains.html">C.2.7. /proc/execdomains
</a></span></dt><dt><span class="section"><a
href="s2-proc-fb.html">C.2.8. /proc/fb
</a></span></dt><dt><span class="section"><a
href="s2-proc-filesystems.html">C.2.9. /proc/filesystems
</a></span></d
t><dt><span class="section"><a
href="s2-proc-interrupts.html">C.2.10. /proc/interrupts
</a></span></dt><dt><span class="section"><a
href="s2-proc-iomem.html">C.2.11. /proc/iomem
</a></span></dt><dt><span class="section"><a
href="s2-proc-ioports.html">C.2.12. /proc/ioports
</a></span></dt><dt><span class="section"><a
href="s2-proc-kcore.html">C.2.13. /proc/kcore
</a></span></dt><dt><span class="section"><a
href="s2-proc-kmsg.html">C.2.14. /proc/kmsg
</a></span></dt><dt><span class="section"><a
href="s2-proc-loadavg.html">C.2.15. /proc/loadavg
</a></span></dt><dt><span class="section"><a
href="s2-proc-locks.html">C.2.16. /proc/locks
</a></span></dt><dt><span class="section"><a
href="s2-proc-mdstat.html">C.2.17. /proc/mdstat
</a></span></dt><dt><span class="section"><a
href="s2-proc-meminfo.html">C.2.18. /proc/meminfo
</a></span></dt><dt><span class="section"><a
href="s2-proc-misc.html">C.2.19. /proc/misc
</a></span></dt><dt><span class="section"><a
href="s2-proc-modu
les.html">C.2.20. /proc/modules
</a></span></dt><dt><span class="section"><a
href="s2-proc-mounts.html">C.2.21. /proc/mounts
</a></span></dt><dt><span class="section"><a
href="s2-proc-mtrr.html">C.2.22. /proc/mtrr
</a></span></dt><dt><span class="section"><a
href="s2-proc-partitions.html">C.2.23. /proc/partitions
</a></span></dt><dt><span class="section"><a
href="s2-proc-slabinfo.html">C.2.24. /proc/slabinfo
</a></span></dt><dt><span class="section"><a
href="s2-proc-stat.html">C.2.25. /proc/stat
</a></span></dt><dt><span class="section"><a
href="s2-proc-swaps.html">C.2.26. /proc/swaps
</a></span></dt><dt><span class="section"><a
href="s2-proc-sysrq-trigger.html">C.2.27. /proc/sysrq-trigger
</a></span></dt><dt><span class="section"><a
href="s2-proc-uptime.html">C.2.28. /proc/uptime
</a></span></dt><dt><span class="section"><a
href="s2-proc-version.html">C.2.29. /proc/version
</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-proc-directories.html">C.3.
Directories within
/proc/</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-proc-directories.html#s2-proc-processdirs">C.3.1. Process
Directories</a></span></dt><dt><span
class="section"><a href="s2-proc-dir-bus.html">C.3.2.
/proc/bus/ </a></span></dt><dt><span
class="section"><a href="s2-proc-pci.html">C.3.3.
/proc/bus/pci </a></span></dt><dt><span
class="section"><a href="s2-proc-dir-driver.html">C.3.4.
/proc/driver/ </a></span></dt><dt><span
class="section"><a href="s2-proc-dir-fs.html">C.3.5.
/proc/fs </a></span></dt><dt><span
class="section"><a href="s2-proc-dir-irq.html">C.3.6.
/proc/irq/ </a></span></dt><dt><span
class="section"><a href="s2-proc-dir-net.html">C.3.7.
/proc/net/ </a></span></dt><dt><span
class="section"><a href="s2-proc-dir-scsi.html">C.3.8.
/proc/scsi/ </a></span></dt><dt><span
class="section"><a href="s2-proc-dir-sys.html">C.3.9.
/proc/sys/ </a></span></dt><dt><span
class="section"><a href="s2-proc-dir-sysvipc.html">C.3.10.
/proc/s
ysvipc/ </a></span></dt><dt><span
class="section"><a href="s2-proc-tty.html">C.3.11.
/proc/tty/ </a></span></dt><dt><span
class="section"><a href="s2-proc-pid.html">C.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">C.4. Using the
sysctl Command</a></span></dt><dt><span
class="section"><a
href="s1-proc-additional-resources.html">C.5.
References</a></span></dt></dl></dd><dt><span
class="appendix"><a href="app-Revision_History.html">D.
Revision History</a></span></dt><dt><span
class="index"><a
href="ix01.html">Index</a></span></dt></dl></div></div><ul
class="docnav"><li class="previous"></li><li
class="next"><a accesskey="n"
href="pr01.html"><strong>Next</strong>Preface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/ix01.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/ix01.html
new file mode 100644
index 0000000..d228aae
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/ix01.html
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Index</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="app-Revision_History.html"
title="Appendix D. Revision History" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="app-Revision_History.html"><strong>Prev</strong></a></li><li
class="next"></li></ul><div class="index"
id="id400094"><div
class="titlepage"><div><div><h2
class="title">Index</h2></div></div></div><d
iv class="index"><div
class="indexdiv"><h3>Symbols</h3><dl><dt>
.fetchmailrc , <a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration">Fetchmail
Configuration Options</a></dt><dd><dl><dt>server options,
<a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-server">Server
Options</a></dt><dt>user options, <a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-fetchmail-configuration-user">User
Options</a></dt></dl></dd><dt>.htaccess, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dd><dl><dt>(see also Apache HTTP
Server)</dt></dl></dd><dt>.htpasswd, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dd><dl><dt>(see also Apache HTTP
Server)</dt></dl></dd><dt> .procmailrc , <a
class="indexterm"
href="s1-email-mda.html#s2-email-procmail-configuration">Procmail Con
figuration</a></dt><dt> /dev/shm , <a class="indexterm"
href="s1-sysinfo-filesystems.html">File
Systems</a></dt><dt>/etc/named.conf (see BIND)</dt><dt>
/etc/sysconfig/ directory (see sysconfig directory)</dt><dt>
/etc/sysconfig/dhcpd , <a class="indexterm"
href="ch10s02s03.html">Starting and Stopping the
Server</a></dt><dt> /proc/ directory, <a class="indexterm"
href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">Installed
Documentation</a> (see proc file system)</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></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#id551994">Configuring Access
Control</a>
</dt><dt>in SSSD, rules, <a class="indexterm"
href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#id542117">The Simple Access
Provider</a></dt></dl></dd><dt>adding</dt><dd><dl><dt>group,
<a class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt><dt>user, <a class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>anacron, <a
class="indexterm"
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">Cron and
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>A
pache HTTP Server</dt><dd><dl><dt>additional
resources</dt><dd><dl><dt>installed documentation, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-resources-installed">Installed
Documentation</a></dt><dt>useful websites, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-resources-web">Useful
Websites</a></dt></dl></dd><dt>checking configuration, <a
class="indexterm"
href="ch-Web_Servers.html#s2-apache-editing">Editing the Configuration
Files</a></dt><dt>checking status, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-running-status">Checking the Service
Status</a></dt><dt>directives</dt><dd><dl><dt><Directory>,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt><IfDefine>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt><IfModule>, <a
class="indexterm" href="ch-Web_Servers.html#s3-apache-httpdconf
-directives">Common httpd.conf
Directives</a></dt><dt><Location>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt><Proxy>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt><VirtualHost>, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AccessFileName, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Action, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AddDescription, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AddEncoding, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives<
/a></dt><dt>AddHandler, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AddIcon, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AddIconByEncoding, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AddIconByType, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AddLanguage, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AddType, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Alias, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Allow, <a class="indexterm"
href="ch-Web_Servers.html
#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>AllowOverride, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>BrowserMatch, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CacheDefaultExpire, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CacheDisable, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CacheEnable, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CacheLastModifiedFactor, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CacheMaxExpire, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives"
Common httpd.conf
Directives</a></dt><dt>CacheNegotiatedDocs, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CacheRoot, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>CustomLog, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>DefaultIcon, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>DefaultType, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Deny, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>DirectoryIndex, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>DocumentRoot, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ErrorDocument, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ErrorLog, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ExtendedStatus, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Group, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>HeaderName, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>HostnameLookups, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Include, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdcon
f-directives">Common httpd.conf
Directives</a></dt><dt>IndexIgnore, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>IndexOptions, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>KeepAlive, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>KeepAliveTimeout, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>LanguagePriority, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Listen, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>LoadModule, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>
LogFormat, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>LogLevel, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>MaxClients, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">Common Multi-Processing
Module Directives</a></dt><dt>MaxKeepAliveRequests, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>MaxSpareServers, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">Common Multi-Processing
Module Directives</a></dt><dt>MaxSpareThreads, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">Common Multi-Processing
Module Directives</a></dt><dt>MinSpareServers, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">Common Multi-Processing
Module Directives</a></dt><dt>MinSpareThreads, <a class="inde
xterm" href="ch-Web_Servers.html#s3-apache-mpm-common">Common
Multi-Processing Module Directives</a></dt><dt>NameVirtualHost, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Options, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Order, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>PidFile, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ProxyRequests, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ReadmeName, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>Redirect, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Co
mmon httpd.conf Directives</a></dt><dt>ScriptAlias, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerAdmin, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerName, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerRoot, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerSignature, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ServerTokens, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>SetEnvIf, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-sslconf-common">Common ssl.conf
Directives</a></dt><dt>StartServers, <a class="ind
exterm" href="ch-Web_Servers.html#s3-apache-mpm-common">Common
Multi-Processing Module Directives</a></dt><dt>SuexecUserGroup, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>ThreadsPerChild, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">Common Multi-Processing
Module Directives</a></dt><dt>Timeout, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>TypesConfig, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>UseCanonicalName, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>User, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>UserDir, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-
directives">Common httpd.conf
Directives</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/httpd/,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/etc/httpd/conf.d/, <a
class="indexterm"
href="ch-Web_Servers.html#s2-apache-editing">Editing the Configuration
Files</a>, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/usr/lib/httpd/modules/, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</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">Common httpd.conf
Directives</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-W
eb_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/var/www/cgi-bin/, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/var/www/html/, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/var/www/icons/, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>~/public_html/, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt></dl></dd><dt>files</dt><dd><dl><dt>.htaccess,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>.htpasswd, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/etc/httpd/conf.d/ssl.conf, <a
class="indexterm" href="ch-
Web_Servers.html#s3-apache-sslconf-common">Common ssl.conf Directives</a>,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-enabling">Enabling the mod_ssl
Module</a></dt><dt>/etc/httpd/conf/httpd.conf, <a
class="indexterm"
href="ch-Web_Servers.html#s2-apache-editing">Editing the Configuration
Files</a>, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a>, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mpm-common">Common Multi-Processing
Module Directives</a></dt><dt>/etc/httpd/logs/access_log, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/etc/httpd/logs/error_log, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>/etc/httpd/run/httpd.pid, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a>
</dt><dt>/etc/mime.types, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt></dl></dd><dt>modules</dt><dd><dl><dt>developing,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-dso-writing">Writing a
Module</a></dt><dt>loading, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-dso-loading">Loading a
Module</a></dt><dt>mod_asis, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-changes">Notable
Changes</a></dt><dt>mod_cache, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-features">New
Features</a></dt><dt>mod_cern_meta, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-changes">Notable
Changes</a></dt><dt>mod_disk_cache, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-features">New
Features</a></dt><dt>mod_ext_filter, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-changes">Notable
Changes</a></dt><dt>mod_proxy_b
alancer, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-features">New
Features</a></dt><dt>mod_rewrite, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf
Directives</a></dt><dt>mod_ssl, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-mod_ssl">Setting Up an SSL
Server</a></dt><dt>mod_userdir, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-migrating">Updating the
Configuration</a></dt></dl></dd><dt>restarting, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-running-restarting">Restarting the
Service</a></dt><dt>SSL
server</dt><dd><dl><dt>certificate, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">An Overview of
Certificates and Security</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">Generating a New
Key and Certificate</a></dt><dt>certificate authority, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">An Overview of
Certificates and Security</a></dt><dt>private key, <a
class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">An Overview of
Certificates and Security</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">Generating a New Key and
Certificate</a></dt><dt>public key, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-mod_ssl-certificates">An Overview of
Certificates and Security</a></dt></dl></dd><dt>starting,
<a class="indexterm"
href="ch-Web_Servers.html#s3-apache-running-starting">Starting the
Service</a></dt><dt>stopping, <a class="indexterm"
href="ch-Web_Servers.html#s3-apache-running-stopping">Stopping the
Service</a></dt><dt>version
2.2</dt><dd><dl><dt>change
s, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-changes">Notable
Changes</a></dt><dt>features, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-features">New
Features</a></dt><dt>updating from version 2.0, <a
class="indexterm"
href="ch-Web_Servers.html#s2-apache-version2-migrating">Updating the
Configuration</a></dt></dl></dd><dt>virtual host, <a
class="indexterm"
href="ch-Web_Servers.html#s2-apache-virtualhosts">Setting Up Virtual
Hosts</a></dt></dl></dd><dt> at , <a
class="indexterm" href="s1-autotasks-at-batch.html">At and
Batch</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="s1-autotasks-additional-resources.html">Additional
Resources</a></dt></dl></dd><dt> authconfig (see
Authentication Configuration Tool )</dt><dd><dl><dt> commands ,
<a class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">Command
Line Version</a></dt></dl></dd><dt>authenti
cation</dt><dd><dl><dt> Authentication Configuration Tool , <a
class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">The
Authentication Configuration Tool</a></dt><dt> using fingerprint support
, <a class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">Advanced
Options</a></dt><dt> using smart card authentication , <a
class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">Advanced
Options</a></dt></dl></dd><dt> Authentication Configuration
Tool </dt><dd><dl><dt> and Kerberos authentication , <a
class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and LDAP , <a
class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authen
tication">Identity & Authentication</a></dt><dt> and
NIS , <a class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and NIS authentication , <a
class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and Winbind , <a
class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt><dt> and Winbind authentication , <a
class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity
& Authentication</a></dt></dl></dd><dt>authoritative
nameserver (see BIND)</dt><dt>Automated Tasks, <a
class="indexterm" href="ch-Automating_System_Tasks.html">Automating
System Ta
sks</a></dt></dl></div><div
class="indexdiv"><h3>B</h3><dl><dt> batch , <a
class="indexterm" href="s1-autotasks-at-batch.html">At and
Batch</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="s1-autotasks-additional-resources.html">Additional
Resources</a></dt></dl></dd><dt>Berkeley Internet Name
Domain (see
BIND)</dt><dt>BIND</dt><dd><dl><dt>additional
resources</dt><dd><dl><dt>installed documentation, <a
class="indexterm"
href="s2-bind-additional-resources.html#s3-bind-installed-docs">Installed
Documentation</a></dt><dt>related books, <a
class="indexterm"
href="s2-bind-additional-resources.html#s3-bind-related-books">Related
Books</a></dt><dt>useful websites, <a class="indexterm"
href="s2-bind-additional-resources.html#s3-bind-useful-websites">Useful
Websites</a></dt></dl></dd><dt>common mistakes, <a
class="indexterm" href="s2-bind-mistakes.html">Common Mistakes to
Avoid</a></dt><dt>configuration</dt><dd><dl><dt>acl
statement, <a class="indexterm" href="s1
-BIND.html#s3-bind-namedconf-state">Common Statement
Types</a></dt><dt>comment tags, <a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-comm">Comment
Tags</a></dt><dt>controls statement, <a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-state-other">Other Statement
Types</a></dt><dt>include statement, <a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-state">Common Statement
Types</a></dt><dt>key statement, <a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-state-other">Other Statement
Types</a></dt><dt>logging statement, <a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-state-other">Other Statement
Types</a></dt><dt>options statement, <a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-state">Common Statement
Types</a></dt><dt>server statement, <a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-state-other">Other Statement
Types</a></dt><dt>trusted-keys statement, <a
class="indexterm" href="s1-BIND.html#s3-bind-namedconf-sta
te-other">Other Statement Types</a></dt><dt>view statement,
<a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-state-other">Other Statement
Types</a></dt><dt>zone statement, <a class="indexterm"
href="s1-BIND.html#s3-bind-namedconf-state">Common Statement
Types</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/named/,
<a class="indexterm"
href="s1-BIND.html#s2-bind-namedconf">Configuring the named
Service</a></dt><dt>/var/named/, <a class="indexterm"
href="s2-bind-zone.html">Editing Zone
Files</a></dt><dt>/var/named/data/, <a class="indexterm"
href="s2-bind-zone.html">Editing Zone
Files</a></dt><dt>/var/named/dynamic/, <a class="indexterm"
href="s2-bind-zone.html">Editing Zone
Files</a></dt><dt>/var/named/slaves/, <a class="indexterm"
href="s2-bind-zone.html">Editing Zone
Files</a></dt></dl></dd><dt>features</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">Internet Protocol version
6 (IPv6)</a></dt><dt>multiple views, <a class="indexterm"
href="s2-bind-features.html#s3-bind-features-views">Multiple
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>files</dt><dd><dl><dt>/etc/named.conf,
<a class="indexterm"
href="s1-BIND.html#s2-bind-namedconf">Configuring the named
Service</a>, <a class="indexterm"
href="s2-bind-rndc.html#s3-bind-rndc-configuration">Configuring the
Utility</a></dt><dt>/etc/rnd
c.conf, <a class="indexterm"
href="s2-bind-rndc.html#s3-bind-rndc-configuration">Configuring the
Utility</a></dt><dt>/etc/rndc.key, <a class="indexterm"
href="s2-bind-rndc.html#s3-bind-rndc-configuration">Configuring the
Utility</a></dt></dl></dd><dt>resource record, <a
class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-zones">Nameserver
Zones</a></dt><dt>types</dt><dd><dl><dt>authoritative
nameserver, <a class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">Nameserver
Types</a></dt><dt>primary (master) nameserver, <a
class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-zones">Nameserver
Zones</a>, <a class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">Nameserver
Types</a></dt><dt>recursive nameserver, <a
class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">Nameserver
Types</a></dt><dt>secondary (slave) nameserver, <a
class="indexterm" href="ch-DNS_Servers.html#s2-dns-introduction
-zones">Nameserver Zones</a>, <a class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">Nameserver
Types</a></dt></dl></dd><dt>utilities</dt><dd><dl><dt>dig,
<a class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-bind">BIND as a
Nameserver</a>, <a class="indexterm"
href="s2-bind-dig.html">Using the dig Utility</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 as a
Nameserver</a>, <a class="indexterm"
href="s1-BIND.html#s2-bind-namedconf">Configuring the named
Service</a></dt><dt>rndc, <a class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-bind">BIND as a
Nameserver</a>, <a class="indexterm"
href="s2-bind-rndc.html">Using the rndc
Utility</a></dt></dl></dd><dt>zones</dt><dd><dl><dt>$INCLUDE
directive, <a class="indexterm"
href="s2-bind-zone.html#s3-bind-zone-directives">Comm
on Directives</a></dt><dt>$ORIGIN directive, <a
class="indexterm"
href="s2-bind-zone.html#s3-bind-zone-directives">Common
Directives</a></dt><dt>$TTL directive, <a class="indexterm"
href="s2-bind-zone.html#s3-bind-zone-directives">Common
Directives</a></dt><dt>A (Address) resource record, <a
class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common
Resource Records</a></dt><dt>CNAME (Canonical Name) resource record,
<a class="indexterm"
href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource
Records</a></dt><dt>comment tags, <a class="indexterm"
href="s2-bind-zone.html#s3-bind-zone-comm">Comment
Tags</a></dt><dt>description, <a class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-zones">Nameserver
Zones</a></dt><dt>example usage, <a class="indexterm"
href="s2-bind-zone.html#s4-bind-zone-examples-basic">A Simple Zone
File</a>, <a class="indexterm"
href="s2-bind-zone.html#s3-bind-configuration-zone-reverse">A Reverse Name
Resolution Zone File</a></dt><dt>MX
(Mail Exchange) resource record, <a class="indexterm"
href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource
Records</a></dt><dt>NS (Nameserver) resource record, <a
class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common
Resource Records</a></dt><dt>PTR (Pointer) resource record, <a
class="indexterm" href="s2-bind-zone.html#s4-bind-zone-rr">Common
Resource Records</a></dt><dt>SOA (Start of Authority) resource record,
<a class="indexterm"
href="s2-bind-zone.html#s4-bind-zone-rr">Common Resource
Records</a></dt></dl></dd></dl></dd><dt>block
devices, <a class="indexterm" href="s2-proc-devices.html">
/proc/devices </a></dt><dd><dl><dt>(see also /proc/devices
)</dt><dt>definition of, <a class="indexterm"
href="s2-proc-devices.html"> /proc/devices
</a></dt></dl></dd><dt>bonding (see channel
bonding)</dt><dt>boot
loader</dt><dd><dl><dt>verifying, <a
class="indexterm" href="s1-kernel-boot-loader.html">Verifying the
Boot Loader</a></dt></dl></dd><dt>boot media, <a class
="indexterm" href="s1-kernel-preparing.html">Preparing to
Upgrade</a></dt></dl></div><div
class="indexdiv"><h3>C</h3><dl><dt>ch-email
.fetchmailrc </dt><dd><dl><dt>global options, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-global">Global
Options</a></dt></dl></dd><dt>chage
command</dt><dd><dl><dt>forcing password expiration with, <a
class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</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>interface</dt><dd><dl><dt>configuration
of, <a class="indexterm"
href="s2-networkscripts-interfaces-chan.html">Channel Bonding
Interfaces</a></dt></dl></dd><dt>parameters to bonded
interfaces, <a class="indexterm" href="sec-Using_Channel_Bonding.h
tml#s3-modules-bonding-directives">Bonding Module
Directives</a></dt></dl></dd><dt>channel bonding interface
(see kernel module)</dt><dt>character devices, <a
class="indexterm" href="s2-proc-devices.html"> /proc/devices
</a></dt><dd><dl><dt>(see also /proc/devices
)</dt><dt>definition of, <a class="indexterm"
href="s2-proc-devices.html"> /proc/devices
</a></dt></dl></dd><dt>Configuration File Changes, <a
class="indexterm"
href="ch-yum.html#sec-Preserving_Configuration_File_Changes">Preserving
Configuration File
Changes</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">Disp
laying 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">Automating
System Tasks</a></dt><dt> cron , <a class="indexterm"
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">Cron and
Anacron</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="s1-autotasks-additional-resources.html">Additional
Resources</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#s
2-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></dl></div><div
class="indexdiv"><h3>D</h3><dl><dt>date, <a
class="indexterm"
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Date
and Time Configuration Tool</a>, <a class="indexterm"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">Configuring
the Date and Time</a></dt><dd><dl><dt>(see also Date and
Time)</dt></dl></dd><dt>Date and
Time</dt><dd><dl><dt>system date, <a
class="indexterm"
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Date
and Time Configuration Tool</a></dt><dt>system time, <a
class="indexterm"
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Date
and Time Configuration Tool</a></dt><dt>time zone settings, <a
class="indexterm"
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Date
and Time Configuration Tool</a></dt></dl></dd><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>(see also /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> df , <a
class="indexterm" href="s1-sysinfo-filesystems.html">File
Systems</a></dt><dt>DHCP, <a class="indexterm"
href="ch-DHCP_Servers.html">DHCP
Servers</a></dt><dd><dl><dt>additional resources, <a
class="indexterm" href="s1-dh
cp-additional-resources.html">Additional
Resources</a></dt><dt>client configuration, <a
class="indexterm"
href="s1-dhcp-configuring-client.html">Configuring a DHCP
Client</a></dt><dt>command line options, <a
class="indexterm" href="ch10s02s03.html">Starting and Stopping the
Server</a></dt><dt>connecting to, <a class="indexterm"
href="s1-dhcp-configuring-client.html">Configuring a DHCP
Client</a></dt><dt>dhcpd.conf, <a class="indexterm"
href="s1-dhcp-configuring-server.html#config-file">Configuration
File</a></dt><dt> dhcpd.leases , <a class="indexterm"
href="ch10s02s03.html">Starting and Stopping the
Server</a></dt><dt>dhcpd6.conf, <a class="indexterm"
href="s1-dhcp_for_ipv6_dhcpv6.html">DHCP for IPv6
(DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm"
href="s1-dhcp_for_ipv6_dhcpv6.html">DHCP for IPv6
(DHCPv6)</a></dt><dt> dhcrelay , <a class="indexterm"
href="dhcp-relay-agent.html">DHCP Relay
Agent</a></dt><dt>global parameters, <a class="indexterm"
href="s1-dhcp-configuring-
server.html#config-file">Configuration File</a></dt><dt>group,
<a class="indexterm"
href="s1-dhcp-configuring-server.html#config-file">Configuration
File</a></dt><dt>options, <a class="indexterm"
href="s1-dhcp-configuring-server.html#config-file">Configuration
File</a></dt><dt>reasons for using, <a class="indexterm"
href="ch-DHCP_Servers.html#s1-dhcp-why">Why Use
DHCP?</a></dt><dt>Relay Agent, <a class="indexterm"
href="dhcp-relay-agent.html">DHCP Relay
Agent</a></dt><dt>server configuration, <a
class="indexterm"
href="s1-dhcp-configuring-server.html">Configuring a DHCP
Server</a></dt><dt> shared-network , <a class="indexterm"
href="s1-dhcp-configuring-server.html#config-file">Configuration
File</a></dt><dt>starting the server, <a class="indexterm"
href="ch10s02s03.html">Starting and Stopping the
Server</a></dt><dt>stopping the server, <a
class="indexterm" href="ch10s02s03.html">Starting and Stopping the
Server</a></dt><dt>subnet, <a class="indexterm"
href="s1-dhcp-configuri
ng-server.html#config-file">Configuration
File</a></dt></dl></dd><dt>dhcpd.conf, <a
class="indexterm"
href="s1-dhcp-configuring-server.html#config-file">Configuration
File</a></dt><dt>dhcpd.leases, <a class="indexterm"
href="ch10s02s03.html">Starting and Stopping the
Server</a></dt><dt> dhcrelay , <a class="indexterm"
href="dhcp-relay-agent.html">DHCP Relay
Agent</a></dt><dt>dig (see BIND)</dt><dt>directory server
(see OpenLDAP)</dt><dt>DNS</dt><dd><dl><dt>definition,
<a class="indexterm" href="ch-DNS_Servers.html">DNS
Servers</a></dt><dd><dl><dt>(see also
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 (see Denial of
Service attack)</dt><dt>drivers (see kernel module)</dt><dt>DSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">
Generating Key Pairs</a></dt></dl></dd><dt> du , <a
class="indexterm" href="s1-sysinfo-filesystems.html">File
Systems</a></dt><dt>Dynamic Host Configuration Protocol (see
DHCP)</dt></dl></div><div
class="indexdiv"><h3>E</h3><dl><dt>email</dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="s1-email-additional-resources.html">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm"
href="s1-email-additional-resources.html#s2-email-installed-docs">Installed
Documentation</a></dt><dt>related books, <a
class="indexterm" href="s2-email-related-books.html">Related
Books</a></dt><dt>useful websites, <a class="indexterm"
href="s2-email-useful-websites.html">Useful
Websites</a></dt></dl></dd><dt>Fetchmail, <a
class="indexterm"
href="s2-email-mta-fetchmail.html">Fetchmail</a></dt><dt>history
of, <a class="indexterm" href="ch-Mail_Servers.html">Mail
Servers</a></dt><dt>mail
server</dt><dd><dl><dt>Dovecot, <a class="indexterm"
href="ch-Mail_Serv
ers.html#s3-mail-server-dovecot">Dovecot</a></dt></dl></dd><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">Mail Delivery
Agents</a></dt><dt>program classifications, <a
class="indexterm" href="s1-email-types.html">Email Program
Classifications</a></dt><dt>protocols, <a class="indexterm"
href="ch-Mail_Servers.html#s1-email-protocols">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>security,
<a class="indexterm"
href="s1-email-mua.html#s2-email-security">Securing
Communication</a></dt><dd><dl><dt>clients, <a
class="indexterm"
href="s1-email-mua.html#s3-email-security-clients">Secure Email Clien
ts</a></dt><dt>servers, <a class="indexterm"
href="s1-email-mua.html#s3-email-security-servers">Securing Email Client
Communications</a></dt></dl></dd><dt>Sendmail, <a
class="indexterm"
href="s2-email-mta-sendmail.html">Sendmail</a></dt><dt>spam</dt><dd><dl><dt>filtering
out, <a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-mda-spam">Spam
Filters</a></dt></dl></dd><dt>types</dt><dd><dl><dt>Mail
Delivery Agent, <a class="indexterm"
href="s2-email-types-mda.html">Mail Delivery
Agent</a></dt><dt>Mail Transport Agent, <a
class="indexterm"
href="s1-email-types.html#s2-email-types-mta">Mail Transport
Agent</a></dt><dt>Mail User Agent, <a class="indexterm"
href="s2-email-types-mua.html">Mail User
Agent</a></dt></dl></dd></dl></dd><dt>epoch,
<a class="indexterm" href="s2-proc-stat.html"> /proc/stat
</a></dt><dd><dl><dt>(see also /proc/stat
)</dt><dt>definition of, <a class="indexterm"
href="s2-proc-stat.html"> /proc/stat
</a></dt></dl></dd><dt>Ethernet (see networ
k)</dt><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>(see also
/proc/execdomains )</dt><dt>definition of, <a class="indexterm"
href="s2-proc-execdomains.html"> /proc/execdomains
</a></dt></dl></dd><dt>expiration of password, forcing,
<a class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt></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">Finding
RPM
Packages</a></dt></dl></dd><dt>feedback</dt><dd><dl><dt>contact
information for this manual, <a class="indexterm" href="sect-Preface
-Feedback.html">Feedback</a></dt></dl></dd><dt>Fetchmail,
<a class="indexterm"
href="s2-email-mta-fetchmail.html">Fetchmail</a></dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="s1-email-additional-resources.html">Additional
Resources</a></dt><dt>command options, <a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands">Fetchmail
Command Options</a></dt><dd><dl><dt>informational, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands-info">Informational
or Debugging Options</a></dt><dt>special, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands-special">Special
Options</a></dt></dl></dd><dt>configuration options, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration">Fetchmail
Configuration Options</a></dt><dd><dl><dt>global options,
<a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-gl
obal">Global Options</a></dt><dt>server options, <a
class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-server">Server
Options</a></dt><dt>user options, <a class="indexterm"
href="s2-email-mta-fetchmail.html#s3-email-fetchmail-configuration-user">User
Options</a></dt></dl></dd></dl></dd><dt>file
system</dt><dd><dl><dt>virtual (see proc file
system)</dt></dl></dd><dt>file systems, <a
class="indexterm" href="s1-sysinfo-filesystems.html">File
Systems</a></dt><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> findsmb , <a
class="indexterm" href="ch-File_and_Print_Servers.html#s3-samba-co
nnect-share-cmdline">Command Line</a></dt><dt> findsmb program,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>FQDN (see fully qualified domain
name)</dt><dt>frame buffer device, <a class="indexterm"
href="s2-proc-fb.html"> /proc/fb
</a></dt><dd><dl><dt>(see also /proc/fb
)</dt></dl></dd><dt> free , <a class="indexterm"
href="s1-sysinfo-memory-usage.html">Memory
Usage</a></dt><dt>FTP, <a class="indexterm"
href="s1-FTP.html">FTP</a></dt><dd><dl><dt>(see
also vsftpd )</dt><dt>active mode, <a class="indexterm"
href="s1-FTP.html#s3-ftp-protocol-multiport">Multiple Ports, Multiple
Modes</a></dt><dt>command port, <a class="indexterm"
href="s1-FTP.html#s3-ftp-protocol-multiport">Multiple Ports, Multiple
Modes</a></dt><dt>data port, <a class="indexterm"
href="s1-FTP.html#s3-ftp-protocol-multiport">Multiple Ports, Multiple
Modes</a></dt><dt>definition of, <a class="indexterm"
href="s1-FTP.html">FTP</a></dt><dt>in
troducing, <a class="indexterm"
href="s1-FTP.html#s2-ftp-protocol">The File Transfer
Protocol</a></dt><dt>passive mode, <a class="indexterm"
href="s1-FTP.html#s3-ftp-protocol-multiport">Multiple Ports, Multiple
Modes</a></dt><dt>server
software</dt><dd><dl><dt> Red Hat Content Accelerator , <a
class="indexterm" href="s2-ftp-servers.html">FTP
Servers</a></dt><dt> vsftpd , <a class="indexterm"
href="s2-ftp-servers.html">FTP
Servers</a></dt></dl></dd></dl></dd><dt>fully
qualified domain name, <a class="indexterm"
href="ch-DNS_Servers.html#s2-dns-introduction-zones">Nameserver
Zones</a></dt></dl></div><div
class="indexdiv"><h3>G</h3><dl><dt> GNOME System
Monitor , <a class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">System
Processes</a></dt><dt> gnome-system-log (see Log File Viewer
)</dt><dt> gnome-system-monitor , <a class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">System
Processes</a></dt><dt>GnuPG</dt><
dd><dl><dt>checking RPM package signatures, <a
class="indexterm" href="s1-check-rpm-sig.html">Checking a
Package's Signature</a></dt></dl></dd><dt>group
configuration</dt><dd><dl><dt>adding groups, <a
class="indexterm"
href="s2-redhat-config-users-group-new.html">Adding a New
Group</a></dt><dt>filtering list of groups, <a
class="indexterm" href="s1-users-configui.html">User Manager
Tool</a></dt><dt>groupadd, <a class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt><dt>modify users in groups, <a
class="indexterm"
href="s2-redhat-config-users-group-properties.html">Modifying Group
Properties</a></dt><dt>modifying group properties, <a
class="indexterm"
href="s2-redhat-config-users-group-properties.html">Modifying Group
Properties</a></dt><dt>viewing list of groups, <a
class="indexterm" href="s1-users-configui.html">User Manager
Tool</a></dt></dl></dd><dt>groups (see group
configuration)</dt><dd><dl><dt>additional resources, <a
class="
indexterm" href="s1-users-groups-additional-resources.html">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm"
href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">Installed
Documentation</a></dt></dl></dd><dt>GID, <a
class="indexterm" href="ch-Managing_Users_and_Groups.html">Managing
Users and Groups</a></dt><dt>introducing, <a
class="indexterm" href="ch-Managing_Users_and_Groups.html">Managing
Users and Groups</a></dt><dt>shared directories, <a
class="indexterm"
href="s1-users-groups-private-groups.html#s2-users-groups-rationale">Group
Directories</a></dt><dt>standard, <a class="indexterm"
href="s1-users-groups-standard-groups.html">Standard
Groups</a></dt><dt>tools for management
of</dt><dd><dl><dt>groupadd, <a class="indexterm"
href="s1-users-tools.html">User and Group Management Tools</a>, <a
class="indexterm" href="s1-users-groups-private-groups.html">User
Private Groups</a></dt><dt>system-config-users, <a c
lass="indexterm" href="s1-users-groups-private-groups.html">User
Private Groups</a></dt><dt>User Manager, <a
class="indexterm" href="s1-users-tools.html">User and Group
Management Tools</a></dt></dl></dd><dt>user private, <a
class="indexterm" href="s1-users-groups-private-groups.html">User
Private Groups</a></dt></dl></dd><dt>GRUB 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 Boot Loader</a></dt><dt>configuring, <a
class="indexterm"
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the
GRUB Boot Loader</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>H</h3><dl><dt>hardware</dt><dd><dl><dt>viewing,
<a class="indexterm"
href="s1-sysinfo-hardware.html">Hardware</a></dt></dl></dd><dt>HTTP
server (see Apache HTTP Server)</dt><dt>httpd (see 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">Interface
Control Scripts</a></dt><dt> ifup , <a class="indexterm"
href="s1-networkscripts-control.html">Interface Control
Scripts</a></dt><dt>information</dt><dd><dl><dt>about
your system, <a class="indexterm"
href="ch-System_Monitoring_Tools.html">System Monitoring
Tools</a></dt></dl></dd><dt>initial RAM disk
image</dt><dd><dl><dt>verifying, <a class="indexterm"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">Verifying the Initial
RAM Disk Image</a></dt><dd><dl><dt>IBM eServer System i,
<a class="indexterm"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">Verifying the Initial
RAM Disk
Image</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">Finding
RPM Packages</a></dt></dl></dd><dt>
insmod , <a class="indexterm"
href="sec-Loading_a_Module.html">Loading a
Module</a></dt><dd><dl><dt>(see also kernel
module)</dt></dl></dd><dt>installing package
groups</dt><dd><dl><dt>installing package groups with PackageKit,
<a class="indexterm"
href="sec-Installing_and_Removing_Package_Groups.html">Installing and
Removing Package Groups</a></dt></dl></dd><dt>installing the
kernel, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the
Kernel</a></dt></dl></div><div
class="indexdiv"><h3>K</h3><dl><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">Installed
Documentation</a></dt><dt>manual pages, <a
class="indexterm"
href="s1-kdump-resources.html#s2-kdump-resources-installed">Installed
Documentation</a></dt><dt>websites, <a class="indexterm"
href="s2-kdump-resources-online.html">Useful
Websites</a></dt></dl></dd><dt>analyzing
the dump (see crash)</dt><dt>configuring the
service</dt><dd><dl><dt>default action, <a
class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-action">Changing the Default
Action</a></dt><dt>dump image compression, <a
class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-filtering">Configuring the
Core Collector</a></dt><dt>filtering level, <a
class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-filtering">The Filtering
Settings Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-filtering">Configuring the
Core Collector</a></dt><dt>initial RAM disk, <a
class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configura
tion-cli-memory">Configuring the Memory
Usage</a></dt><dt>kernel image, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-memory">Configuring the Memory
Usage</a></dt><dt>kernel options, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-memory">Configuring the Memory
Usage</a></dt><dt>memory usage, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-basic">The Basic Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-memory">Configuring the Memory
Usage</a></dt><dt>supported targets, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-target">The Target Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-target">Configuring the Target
Type</a></dt><dt>target location, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-target">The Target Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-target">Configuring the Target
Type</a></dt></dl></dd><dt>enabling the service, <a
class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-enable">Enabling the
Service</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-enable">Enabling the
Service</a></dt><dt>known
issues</dt><dd><dl><dt>hpsa driver, <a
class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-gui-target">The Target Settings
Tab</a>, <a class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-target">Configuring the Target
Type</a></dt></dl></dd><dt>running the service, <a
class="indexterm"
href="ch-kdump.html#s3-kdump-configuration-cli-enable">Enabling the
Service</a></dt><dt>system requirements, <a
class="indexterm" href="ch-kdump.html#s1-kdump-configuration">Co
nfiguring the kdump Service</a></dt><dt>testing the configuration,
<a class="indexterm"
href="ch-kdump.html#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.html">Downloading
the Upgraded Kernel</a></dt><dt>installing kernel packages, <a
class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the
Kernel</a></dt><dt>kernel packages, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of
Kernel Packages</a></dt><dt>package, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the
Kernel</a></dt><dt>performing kernel upgrade, <a
class="indexterm" href="s1-kernel-perform-upgrade.html">Performing
the Upgrade</a></dt><dt>RPM package, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the
Kernel</a></dt><dt>upgrade kernel available, <a cla
ss="indexterm" href="s1-kernel-download.html">Downloading the
Upgraded Kernel</a></dt><dd><dl><dt>Security Advisories,
<a class="indexterm" href="s1-kernel-download.html">Downloading
the Upgraded Kernel</a></dt><dt>via Fedora Update System, <a
class="indexterm" href="s1-kernel-download.html">Downloading the
Upgraded
Kernel</a></dt></dl></dd><dt>upgrading</dt><dd><dl><dt>preparing,
<a class="indexterm" href="s1-kernel-preparing.html">Preparing
to Upgrade</a></dt><dt>working boot media, <a
class="indexterm" href="s1-kernel-preparing.html">Preparing to
Upgrade</a></dt></dl></dd><dt>upgrading the kernel, <a
class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the
Kernel</a></dt></dl></dd><dt>Kernel Dump Configuration (see
kdump)</dt><dt>kernel module</dt><dd><dl><dt>bonding
module, <a class="indexterm"
href="sec-Using_Channel_Bonding.html">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">Loading a
Module</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">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
Curre
ntly-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">Loading a
Module</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
Module 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="inde
xterm" 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">Loading a
Module</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">Loading a Module</a>, <a
class="indexterm" href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt><dt> rmmod , <a class="indexterm"
href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt></dl></dd></dl></dd><dt>kernel
package</dt><dd><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">Overview of
Kernel Package
s</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">Overview of
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">Overview of
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">Overview of
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">Overview of
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">Overview of
Kernel
Packages</a></dt></dl></dd></dl></dd><dt>kernel
upgrading</dt><dd><dl><dt>
preparing, <a class="indexterm"
href="s1-kernel-preparing.html">Preparing to
Upgrade</a></dt></dl></dd><dt>keyboard configuration (see
Region and Language)</dt></dl></div><div
class="indexdiv"><h3>L</h3><dl><dt>language
configuration (see Region and Language)</dt><dt>LDAP (see
OpenLDAP)</dt><dt> Log File Viewer
</dt><dd><dl><dt>filtering, <a class="indexterm"
href="s1-logfiles-viewing.html">Viewing Log
Files</a></dt><dt>monitoring, <a class="indexterm"
href="s1-logfiles-examining.html">Monitoring Log
Files</a></dt><dt>searching, <a class="indexterm"
href="s1-logfiles-viewing.html">Viewing Log
Files</a></dt></dl></dd><dt>log files, <a
class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html">Viewing and Managing Log
Files</a></dt><dd><dl><dt>(see also Log Viewer
)</dt><dt>additional
resources</dt><dd><dl><dt>installed documentation, <a
class="indexterm"
href="s1-log-files-additional-resources.html#s2-log-files-installed-docs">Installed
Documentation</a></dt><dt>useful
websites, <a class="indexterm"
href="s2-log-files-useful-websites.html">Useful
Websites</a></dt></dl></dd><dt>description, <a
class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html">Viewing and Managing Log
Files</a></dt><dt>locating, <a class="indexterm"
href="s1-logfiles-locating.html">Locating Log
Files</a></dt><dt>monitoring, <a class="indexterm"
href="s1-logfiles-examining.html">Monitoring Log
Files</a></dt><dt>rotating, <a class="indexterm"
href="s1-logfiles-locating.html">Locating Log
Files</a></dt><dt> rsyslogd daemon , <a class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html">Viewing and Managing Log
Files</a></dt><dt>viewing, <a class="indexterm"
href="s1-logfiles-viewing.html">Viewing Log
Files</a></dt></dl></dd><dt> Log Viewer
</dt><dd><dl><dt>refresh rate, <a class="indexterm"
href="s1-logfiles-viewing.html">Viewing Log
Files</a></dt></dl></dd><dt> logrotate , <a
class="indexterm" href="s1-logfiles-locating.html">Locating Log
Files</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>(see also
kernel module)</dt></dl></dd><dt> lspci , <a
class="indexterm" href="s2-proc-pci.html"> /proc/bus/pci
</a></dt></dl></div><div
class="indexdiv"><h3>M</h3><dl><dt>Mail Delivery
Agent (see email)</dt><dt>Mail Transport Agent (see email) (see
MTA)</dt><dt> Mail Transport Agent Switcher , <a
class="indexterm" href="s2-email-switchmail.html">Mail Transport
Agent (MTA) Configuration</a></dt><dt>Mail User Agent, <a
class="indexterm" href="s2-email-switchmail.html">Mail Transport
Agent (MTA) Configuration</a> (see email)</dt><dt>MDA (see Mail Delivery
Agent)</dt><dt>memory usage, <a class="indexterm"
href="s1-sysinfo-memory-usage.html">Memory
Usage</a></dt><dt> modinfo , <a class="indexterm"
href="sec-Displaying_Information_About_a_Module.html">Displaying Information
About a Module</a></dt><dd><dl><dt>(see also ke
rnel module)</dt></dl></dd><dt> modprobe , <a
class="indexterm" href="sec-Loading_a_Module.html">Loading a
Module</a>, <a class="indexterm"
href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt><dd><dl><dt>(see also kernel
module)</dt></dl></dd><dt>module (see kernel
module)</dt><dt>module parameters (see kernel module)</dt><dt>MTA
(see Mail Transport Agent)</dt><dd><dl><dt>setting default, <a
class="indexterm" href="s2-email-switchmail.html">Mail Transport
Agent (MTA) Configuration</a></dt><dt>switching with Mail Transport
Agent Switcher , <a class="indexterm"
href="s2-email-switchmail.html">Mail Transport Agent (MTA)
Configuration</a></dt></dl></dd><dt>MUA, <a
class="indexterm" href="s2-email-switchmail.html">Mail Transport
Agent (MTA) Configuration</a> (see Mail User Agent)</dt><dt>Multihomed
DHCP</dt><dd><dl><dt>host configuration, <a
class="indexterm"
href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configuration">Host
Configuration</a></dt><dt
server configuration, <a class="indexterm"
href="sect-Configuring_a_Multihomed_DHCP_Server.html">Configuring a
Multihomed DHCP Server</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></dl></div><div
class="indexdiv"><h3>N</h3><dl><dt>named (see
BIND)</dt><dt>nameserver (see DNS)</dt><dt> net program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>network</dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="s1-networkscripts-resources.html">Additional
Resources</a></dt><dt>commands</dt><dd><dl><dt>
/sbin/ifdown , <a class="indexterm"
href="s1-networkscripts-control.html">Interface Control
Scripts</a></dt><dt> /sbin/ifup , <a class="indexterm"
href="s1-networkscripts-control.html">
Interface Control
Scripts</a></dt></dl></dd><dt>configuration, <a
class="indexterm"
href="s1-networkscripts-interfaces.html">Interface Configuration
Files</a></dt><dt>configuration files, <a class="indexterm"
href="ch-Network_Interfaces.html#s1-networkscripts-files">Network
Configuration Files</a></dt><dt>functions, <a
class="indexterm" href="s1-networkscripts-functions.html">Network
Function Files</a></dt><dt>interface configuration files, <a
class="indexterm"
href="s1-networkscripts-interfaces.html">Interface Configuration
Files</a></dt><dt>interfaces</dt><dd><dl><dt>alias,
<a class="indexterm"
href="s2-networkscripts-interfaces-alias.html">Alias and Clone
Files</a></dt><dt>channel bonding, <a class="indexterm"
href="s2-networkscripts-interfaces-chan.html">Channel Bonding
Interfaces</a></dt><dt>clone, <a class="indexterm"
href="s2-networkscripts-interfaces-alias.html">Alias and Clone
Files</a></dt><dt>dialup, <a class="indexterm"
href="s2-networkscripts-interfaces-ppp0.htm
l">Dialup Interfaces</a></dt><dt>Ethernet, <a
class="indexterm"
href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">Ethernet
Interfaces</a></dt></dl></dd><dt>scripts, <a
class="indexterm" href="ch-Network_Interfaces.html">Network
Interfaces</a></dt></dl></dd><dt>Network Time Protocol,
<a class="indexterm"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Configuring
the Network Time Protocol</a></dt><dd><dl><dt>ntpd, <a
class="indexterm"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Configuring
the Network Time Protocol</a></dt><dt>ntpdate, <a
class="indexterm"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Configuring
the 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 Distribution
Programs</a></dt><dt>NTP (see Network Time
Protocol)</dt><dt>ntpd, <a class="indexterm"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Configuring
the Network Time Protocol</a></dt><dt>ntpdate, <a
class="indexterm"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Configuring
the Network Time Protocol</a></dt></dl></div><div
class="indexdiv"><h3>O</h3><dl><dt>OpenLDAP</dt><dd><dl><dt>checking
status, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-running-status">Checking the Service
Status</a></dt><dt>client applications, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-packages-applications">Overview of
Common LDAP Client
Applications</a></dt><dt>configuration</dt><dd><dl><dt>database,
<a class="indexterm" href="ch-Directory_Servers.html#s3-ldap
-configuration-database">Changing the Database-Specific
Configuration</a></dt><dt>global, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>overview, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-setup">OpenLDAP Server
Setup</a></dt></dl></dd><dt>directives</dt><dd><dl><dt>olcAllows,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcConnMaxPending, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcConnMaxPendingAuth, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcDisallows, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcIdleTimeout, <a
class="indexterm" h
ref="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcLogFile, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcReadOnly, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">Changing the
Database-Specific Configuration</a></dt><dt>olcReferral, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>olcRootDN, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">Changing the
Database-Specific Configuration</a></dt><dt>olcRootPW, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">Changing the
Database-Specific Configuration</a></dt><dt>olcSuffix, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">Changing the
Database-Specific Configurati
on</a></dt><dt>olcWriteTimeout, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global
Configuration</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/openldap/slapd.d/,
<a class="indexterm"
href="ch-Directory_Servers.html#s2-ldap-configuration">Configuring an
OpenLDAP Server</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>features, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-features">OpenLDAP
Features</a></dt><dt>files</dt><dd><dl><dt>/etc/openldap/ldap.conf,
<a class="indexterm"
href="ch-Directory_Servers.html#s2-ldap-configuration">Configuring an
OpenLDAP Server</a></dt><dt>/etc/openldap/slapd.d/cn=config.ldif, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-global">Changing the
Global Configuration</a></dt><dt>/etc/openldap/slapd.d/cn=config/olcDa
tabase={1}bdb.ldif, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-database">Changing the
Database-Specific
Configuration</a></dt></dl></dd><dt>installation, <a
class="indexterm"
href="ch-Directory_Servers.html#s2-ldap-installation">Installing the OpenLDAP
Suite</a></dt><dt>migrating authentication information, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-migrationtools">Migrating Old
Authentication Information to LDAP Format</a></dt><dt>packages, <a
class="indexterm"
href="ch-Directory_Servers.html#s2-ldap-installation">Installing the OpenLDAP
Suite</a></dt><dt>restarting, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-running-restarting">Restarting the
Service</a></dt><dt>running, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-running-starting">Starting the
Service</a></dt><dt>schema, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-configuration-schema">Extending
Schema</a></dt><dt>stoppin
g, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-running-stopping">Stopping the
Service</a></dt><dt>terminology</dt><dd><dl><dt>attribute,
<a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-terminology">LDAP
Terminology</a></dt><dt>entry, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-terminology">LDAP
Terminology</a></dt><dt> LDIF , <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-terminology">LDAP
Terminology</a></dt></dl></dd><dt>utilities, <a
class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-packages-openldap-servers">Overview
of OpenLDAP Server Utilities</a>, <a class="indexterm"
href="ch-Directory_Servers.html#s3-ldap-packages-openldap-clients">Overview
of OpenLDAP Client Utilities</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">Main
Features</a></dt><dd><dl><dt>(see also
SSH)</dt><dt>additional resources, <a cla
ss="indexterm"
href="s1-openssh-additional-resources.html">Additional
Resources</a></dt><dt>client, <a class="indexterm"
href="s1-ssh-clients.html">OpenSSH
Clients</a></dt><dd><dl><dt> scp , <a
class="indexterm" href="s2-ssh-clients-scp.html">Using the scp
Utility</a></dt><dt> sftp , <a class="indexterm"
href="s2-ssh-clients-sftp.html">Using the sftp
Utility</a></dt><dt> ssh , <a class="indexterm"
href="s1-ssh-clients.html#s2-ssh-clients-ssh">Using the ssh
Utility</a></dt></dl></dd><dt>DSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating
Key Pairs</a></dt></dl></dd><dt>RSA
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating
Key Pairs</a></dt></dl></dd><dt>RSA Version 1
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-
keypairs-generating">Generating Key
Pairs</a></dt></dl></dd><dt>server, <a
class="indexterm" href="s2-ssh-configuration-sshd.html">Starting an
OpenSSH Server</a></dt><dd><dl><dt>starting, <a
class="indexterm" href="s2-ssh-configuration-sshd.html">Starting an
OpenSSH Server</a></dt><dt>stopping, <a class="indexterm"
href="s2-ssh-configuration-sshd.html">Starting an OpenSSH
Server</a></dt></dl></dd><dt> ssh-add , <a
class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Configuring
ssh-agent</a></dt><dt> ssh-agent , <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Configuring
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">Generating
Key Pairs</a></dt><dt>RSA, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating
Key Pa
irs</a></dt><dt>RSA Version 1, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating
Key Pairs</a></dt></dl></dd><dt>using key-based
authentication, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html">Using a Key-Based
Authentication</a></dt></dl></dd><dt>OpenSSL</dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="s1-openssh-additional-resources.html">Additional
Resources</a></dt><dt>SSL (see SSL)</dt><dt>TLS (see
TLS)</dt></dl></dd><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>package</dt><dd><dl><dt>kernel
RPM, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgradi
ng the Kernel</a></dt></dl></dd><dt>PackageKit, <a
class="indexterm"
href="ch-PackageKit.html">PackageKit</a></dt><dd><dl><dt>adding
and removing, <a class="indexterm"
href="sec-Using_Add_Remove_Software.html">Using Add/Remove
Software</a></dt><dt>architecture, <a class="indexterm"
href="sec-PackageKit_Architecture.html">PackageKit
Architecture</a></dt><dt>installing and removing package groups, <a
class="indexterm"
href="sec-Installing_and_Removing_Package_Groups.html">Installing and
Removing Package Groups</a></dt><dt>installing packages , <a
class="indexterm"
href="ch-PackageKit.html">PackageKit</a></dt><dt>managing
packages , <a class="indexterm"
href="ch-PackageKit.html">PackageKit</a></dt><dt>PolicyKit</dt><dd><dl><dt>authentication,
<a class="indexterm"
href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating
Packages with Software
Update</a></dt></dl></dd><dt>uninstalling packages , <a
class="indexterm"
href="ch-PackageKit.html">PackageKit</a></d
t><dt>updating packages , <a class="indexterm"
href="ch-PackageKit.html">PackageKit</a></dt><dt>viewing
packages , <a class="indexterm"
href="ch-PackageKit.html">PackageKit</a></dt><dt>viewing
transaction log, <a class="indexterm"
href="sec-Viewing_the_Transaction_Log.html">Viewing the Transaction
Log</a></dt></dl></dd><dt>packages</dt><dd><dl><dt>adding
and removing with PackageKit, <a class="indexterm"
href="sec-Using_Add_Remove_Software.html">Using Add/Remove
Software</a></dt><dt>dependencies, <a class="indexterm"
href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">Unresolved
Dependency</a></dt><dt>determining file ownership with, <a
class="indexterm" href="s1-rpm-impressing.html">Practical and
Common Examples of RPM Usage</a></dt><dt>displaying packages with
Yum</dt><dd><dl><dt>yum info, <a class="indexterm"
href="sec-Displaying_Package_Information.html">Displaying Package
Information</a></dt></dl></dd><dt>filtering with PackageKit,
<a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dd><dl><dt>Development, <a
class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Free, <a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Hide Subpackages, <a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Installed, <a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>No Filter, <a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Only Available, <a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Only Development, <a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Only End User Files, <a class="index
term" href="sec-Finding_Packages_with_Filters.html">Finding Packages
with Filters</a></dt><dt>Only Graphical, <a
class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Only Installed, <a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Only Native Packages, <a
class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt><dt>Only Newest Packages, <a
class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</a></dt></dl></dd><dt>filtering with PackageKit for
packages, <a class="indexterm"
href="sec-Finding_Packages_with_Filters.html">Finding Packages with
Filters</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>finding RPM packages, <a
class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding
RPM Packages</a></dt><dt>iFedora installation media, <a
class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding
RPM Packages</a></dt><dt>initial RPM repositories, <a
class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding
RPM Packages</a></dt><dt>installing a package group with Yum, <a
class="indexterm" href="sec-Installing.html">Installing
Packages</a></dt><dt>installing and removing package groups, <a
class="indexterm"
href="sec-Installing_and_Removing_Package_Groups.html">Installing and
Removing Package Groups</a></dt><dt>installing packages with PackageKit,
<a class="indexterm"
href="ch-PackageKit.html">PackageKit</a>, <a
class="indexterm"
href="sec-Installing_and_Removing_Packages_and_Dependencies.html">Installing
and Removing Packages (and
Dependencies)</a></dt><dd><dl><dt>dependencies, <a
class="indexterm"
href="sec-Installing_and_Removing_Packages_and_Dependencies.html">Installing
and Removing Packages (and
Dependencies)</a></dt></dl></dd><dt>ins
talling RPM, <a class="indexterm"
href="sec-Installing_and_Upgrading.html">Installing and
Upgrading</a></dt><dt>installing with Yum, <a
class="indexterm" href="sec-Installing.html">Installing
Packages</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">Overview of
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">Overview of
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">Overview of
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">Overview of
Kernel Packages</a></dt></dl></dd><dt>l
inux-firmware</dt><dd><dl><dt> firmware files, <a
class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of
Kernel Packages</a></dt></dl></dd><dt>listing packages with
Yum</dt><dd><dl><dt> Glob expressions, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum grouplist, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum list all, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum list available, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum list installed, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum repolist, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum search, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt></dl></dd><dt>locating documentation for,
<a class="indexterm" href="s1-rp
m-impressing.html">Practical and Common Examples of RPM
Usage</a></dt><dt>managing packages with PackageKit, <a
class="indexterm"
href="ch-PackageKit.html">PackageKit</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>packages and package groups, <a
class="indexterm"
href="sec-Packages_and_Package_Groups.html">Packages and Package
Groups</a></dt><dt>perf</dt><dd><dl><dt>
firmware files, <a class="indexterm"
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of
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>removing, <a
class="indexterm"
href="s2-rpm-uninstalling.html">Uninstalling</a></dt><dt>removing
package groups with Yum, <a class="indexterm"
href="sec-Removing.html">Removing
Packages</a></dt><dt>removing packages with PackageKit, <a
class="i
ndexterm"
href="sec-Installing_and_Removing_Packages_and_Dependencies.html">Installing
and Removing Packages (and Dependencies)</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">Package Already
Installed</a></dt><dt>configuration file changes, <a
class="indexterm"
href="sec-Configuration_File_Changes.html">Configuration File
Changes</a></dt><dt>conflict, <a class="indexterm"
href="sec-Installing_and_Upgrading.html#s3-rpm-conflicting-files">Conflicting
Files</a></dt><dt>failed dependencies, <a class="indexterm"
href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">Unresolved
Dependency</a></dt><dt>freshening, <a class="indexterm"
href="s2-rpm-freshening.html">Freshening</a></dt><dt>pristine
sources, <a class="indexterm"
href="ch-RPM.html#s1-rpm-design">RPM Design
Goals</a></dt><dt>querying, <a class="indexterm"
href="s2-rpm-querying.htm
l">Querying</a></dt><dt>removing, <a
class="indexterm"
href="s2-rpm-uninstalling.html">Uninstalling</a></dt><dt>source
and binary packages, <a class="indexterm"
href="ch-RPM.html">RPM</a></dt><dt>tips, <a
class="indexterm" href="s1-rpm-impressing.html">Practical and
Common Examples of RPM Usage</a></dt><dt>uninstalling, <a
class="indexterm"
href="s2-rpm-uninstalling.html">Uninstalling</a></dt><dt>verifying,
<a class="indexterm"
href="s2-rpm-verifying.html">Verifying</a></dt></dl></dd><dt>searching
packages with Yum</dt><dd><dl><dt>yum search, <a
class="indexterm"
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>setting packages with
PackageKit</dt><dd><dl><dt>checking interval, <a
class="indexterm"
href="ch-PackageKit.html#sec-Setting_preferences_for_checking_for_updates">Setting
the Update-Checking
Interval</a></dt></dl></dd><dt>uninstalling packages with
PackageKit, <a class="indexterm" href="ch-PackageKit.html">Pa
ckageKit</a></dt><dt>uninstalling packages with Yum, <a
class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt><dd><dl><dt>yum remove package_name, <a
class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt></dl></dd><dt>updating currently installed
packages</dt><dd><dl><dt>available updates, <a
class="indexterm"
href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating
Packages with Software Update</a></dt></dl></dd><dt>updating
packages with 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">Updating
Packages with Software Update</a></dt><dt>Software Update, <a
class="indexterm"
href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating
Packages with Software
Update</a></dt></dl></dd><dt>upgrading RPM, <a
class="indexterm" href="sec-Installing_and_Upgrading.html">Install
ing and Upgrading</a></dt><dt>viewing packages with PackageKit, <a
class="indexterm"
href="ch-PackageKit.html">PackageKit</a></dt><dt>viewing
transaction log, <a class="indexterm"
href="sec-Viewing_the_Transaction_Log.html">Viewing the Transaction
Log</a></dt><dt>viewing Yum repositories with PackageKit, <a
class="indexterm"
href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">Setting
the Software Sources</a></dt><dt>Yum instead of RPM, <a
class="indexterm"
href="ch-RPM.html">RPM</a></dt></dl></dd><dt>password</dt><dd><dl><dt>aging,
<a class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt><dt>expire, <a class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>passwords</dt><dd><dl><dt>shadow,
<a class="indexterm"
href="s1-users-groups-shadow-utilities.html">Shadow
Passwords</a></dt></dl></dd><dt> pdbedit program, <a
class="indexterm" href="ch-File_and_Print_Se
rvers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>PolicyKit, <a class="indexterm"
href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">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>default
installation, <a class="indexterm"
href="s1-email-mta.html#s3-email-mta-postfix-default">The Default Postfix
Installation</a></dt></dl></dd><dt>postfix, <a
class="indexterm" href="s2-email-switchmail.html">Mail Transport
Agent (MTA) Configuration</a></dt><dt>primary nameserver (see
BIND)</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> /proc/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" href="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="indexterm"
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"> /pro
c/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>(see also 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/fs/ 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 (see system
request key)</dt><dt> /proc/sys/net/ director
y, <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">References</a></dt><dd><dl><dt>installed
documentation, <a class="indexterm"
href="s1-proc-additional-resources.html#s2-proc-installed-documentation">Installed
Documentation</a></dt
<dt>useful websites, <a class="indexterm"
href="s1-proc-additional-resources.html#s2-proc-useful-websites">Useful
Websites</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
within 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>proc
esses, <a
class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">System
Processes</a></dt><dt>Procmail, <a class="indexterm"
href="s1-email-mda.html">Mail Delivery
Agents</a></dt><dd><dl><dt>additional resources, <a
class="indexterm"
href="s1-email-additional-resources.html">Additional
Resources</a></dt><dt>configuration, <a class="indexterm"
href="s1-email-mda.html#s2-email-procmail-configuration">Procmail
Configuration</a></dt><dt>recipes, <a class="indexterm"
href="s2-email-procmail-recipes.html">Procmail
Recipes</a></dt><dd><dl><dt>delivering, <a
class="indexterm"
href="s2-email-procmail-recipes.html#s2-email-procmail-recipes-delivering">Delivering
vs. Non-Delivering Recipes</a></dt><dt>examples, <a
class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-examples">Recipe
Examples</a></dt><dt>flags, <a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-flags">Flags</a></dt><dt>local
lockf
iles, <a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-lockfile">Specifying
a Local Lockfile</a></dt><dt>non-delivering, <a
class="indexterm"
href="s2-email-procmail-recipes.html#s2-email-procmail-recipes-delivering">Delivering
vs. Non-Delivering Recipes</a></dt><dt>SpamAssassin, <a
class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-mda-spam">Spam
Filters</a></dt><dt>special actions, <a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special">Special
Conditions and Actions</a></dt><dt>special conditions, <a
class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special">Special
Conditions and
Actions</a></dt></dl></dd></dl></dd><dt> ps ,
<a class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">System
Processes</a></dt></dl></div><div
class="indexdiv"><h3>R</h3><dl><dt>RAM, <a
class="indexterm" href="s1-sysinfo-memory-usage.html">Memory Usa
ge</a></dt><dt> rcp , <a class="indexterm"
href="s2-ssh-clients-scp.html">Using the scp
Utility</a></dt><dt>recursive nameserver (see
BIND)</dt><dt>Region and
Language</dt><dd><dl><dt>keyboard configuration, <a
class="indexterm"
href="sect-Language_and_Keyboard_Configuration-Layouts.html">Changing the
Keyboard Layout</a></dt><dt>language configuration, <a
class="indexterm"
href="ch-Language_and_Keyboard_Configuration.html#sect-Language_and_Keyboard_Configuration-Language">Changing
the Language</a></dt></dl></dd><dt>removing package
groups</dt><dd><dl><dt>removing package groups with PackageKit,
<a class="indexterm"
href="sec-Installing_and_Removing_Package_Groups.html">Installing and
Removing Package Groups</a></dt></dl></dd><dt>resource
record (see BIND)</dt><dt> rmmod , <a class="indexterm"
href="sec-Unloading_a_Module.html">Unloading a
Module</a></dt><dd><dl><dt>(see also kernel
module)</dt></dl></dd><dt>rndc (see BIND)</dt><dt>root
nameserver (see BIND)</dt><dt> rpcclien
t program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>RPM, <a class="indexterm"
href="ch-RPM.html">RPM</a></dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="s1-rpm-additional-resources.html">Additional
Resources</a></dt><dt>already installed, <a
class="indexterm"
href="sec-Installing_and_Upgrading.html#s3-rpm-errors">Package Already
Installed</a></dt><dt>basic modes, <a class="indexterm"
href="s1-rpm-using.html">Using RPM</a></dt><dt>book about,
<a class="indexterm" href="s2-rpm-related-books.html">Related
Books</a></dt><dt>checking package signatures, <a
class="indexterm" href="s1-check-rpm-sig.html">Checking a
Package's Signature</a></dt><dt>configuration file changes, <a
class="indexterm"
href="sec-Configuration_File_Changes.html">Configuration File
Changes</a></dt><dd><dl><dt>conf.rpmsave, <a
class="indexterm"
href="sec-Configuration_File_Changes.html">Configuration File
Changes</a><
/dt></dl></dd><dt>conflicts, <a class="indexterm"
href="sec-Installing_and_Upgrading.html#s3-rpm-conflicting-files">Conflicting
Files</a></dt><dt>dependencies, <a class="indexterm"
href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">Unresolved
Dependency</a></dt><dt>design goals, <a class="indexterm"
href="ch-RPM.html#s1-rpm-design">RPM Design
Goals</a></dt><dd><dl><dt>powerful querying, <a
class="indexterm" href="ch-RPM.html#s1-rpm-design">RPM Design
Goals</a></dt><dt>system verification, <a class="indexterm"
href="ch-RPM.html#s1-rpm-design">RPM Design
Goals</a></dt><dt>upgradability, <a class="indexterm"
href="ch-RPM.html#s1-rpm-design">RPM Design
Goals</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>documentation 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">Unresolved
Dependency</a></dt><dt>file
conflicts</dt><dd><dl><dt>resolving, <a
class="indexterm"
href="sec-Installing_and_Upgrading.html#s3-rpm-conflicting-files">Conflicting
Files</a></dt></dl></dd><dt>file name, <a
class="indexterm"
href="sec-Installing_and_Upgrading.html">Installing and
Upgrading</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>finding RPM packages, <a
class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding
RPM Packages</a></dt><dt>freshening, <a class="indexterm"
href="s2-rpm-freshening.html">Freshening</a></dt><dt>GnuPG,
<a class="indexterm" href="s1-check-rpm-sig.html">Checking a
Package's Signature</a></dt><dt>installing, <a
class="indexterm"
href="sec-Installing_and_Upgrading.html">Installing and
Upgrading</a></dt><dt>md5sum, <a class="indexterm"
href="s1
-check-rpm-sig.html">Checking a Package's
Signature</a></dt><dt>querying, <a class="indexterm"
href="s2-rpm-querying.html">Querying</a></dt><dt>querying
for file list, <a class="indexterm"
href="s1-rpm-impressing.html">Practical and Common Examples of RPM
Usage</a></dt><dt>querying uninstalled packages, <a
class="indexterm" href="s1-rpm-impressing.html">Practical and
Common Examples of RPM Usage</a></dt><dt>tips, <a
class="indexterm" href="s1-rpm-impressing.html">Practical and
Common Examples of RPM Usage</a></dt><dt>uninstalling, <a
class="indexterm"
href="s2-rpm-uninstalling.html">Uninstalling</a></dt><dt>upgrading,
<a class="indexterm"
href="sec-Installing_and_Upgrading.html">Installing and
Upgrading</a></dt><dt>verifying, <a class="indexterm"
href="s2-rpm-verifying.html">Verifying</a></dt><dt>website,
<a class="indexterm" href="s2-rpm-useful-websites.html">Useful
Websites</a></dt></dl></dd><dt>RPM Package Manager (see
RPM)</dt><dt>RSA keys</dt><dd><dl><dt>generating,
<a
class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating
Key Pairs</a></dt></dl></dd><dt>RSA Version 1
keys</dt><dd><dl><dt>generating, <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating
Key Pairs</a></dt></dl></dd><dt> rsyslog , <a
class="indexterm"
href="ch-Viewing_and_Managing_Log_Files.html">Viewing and Managing Log
Files</a></dt></dl></div><div
class="indexdiv"><h3>S</h3><dl><dt>Samba (see
Samba)</dt><dd><dl><dt>Abilities, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-abilities">Samba
Features</a></dt><dt>Account Information Databases, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dd><dl><dt> ldapsam , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> ldapsam_compat ,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> mysqlsam , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt>Plain Text, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> smbpasswd , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> tdbsam , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt> xmlsam , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt></dl></dd><dt>Additional
Resources, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-resources">Additional
Resources</a
</dt><dd><dl><dt>installed documentation,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-resources-installed">Installed
Documentation</a></dt><dt>related books, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-resources-published">Related
Books</a></dt><dt>useful websites, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-resources-community">Useful
Websites</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 Account
Information Databases</a></dt><dt>Browsing, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">Samba Network
Browsing</a></dt><dt>configuration, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-configuring">Configuring a
Samba Server</a>, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-configuring-cmdline">Command
Line Configuration</a></
dt><dd><dl><dt>default,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-configuring">Configuring a
Samba Server</a></dt></dl></dd><dt>CUPS Printing Support,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-cups">Samba with CUPS Printing
Support</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>daemon, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-daemons">Samba Daemons and
Related Services</a></dt><dd><dl><dt>nmbd, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-services">Samba
Daemons</a></dt><dt>overview, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-services">Samba
Daemons</a></dt><dt>smbd, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-services">Samba
Daemons</a></dt><dt>winbindd, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-sa
mba-services">Samba
Daemons</a></dt></dl></dd><dt>encrypted passwords, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt><dt> findsmb , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">Command
Line</a></dt><dt>graphical configuration, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-configuring-gui">Graphical
Configuration</a></dt><dt>Introduction, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#samba-rgs-overview">Introduction to
Samba</a></dt><dt>Network Browsing, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">Samba Network
Browsing</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></d
l></dd><dt>New Database Back Ends, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">Samba Account
Information Databases</a></dt><dt>Programs, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dd><dl><dt> findsmb , <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> net , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> nmblookup , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> pdbedit , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> rpcclient , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbcacls , <a class="indexterm"
href="ch-File
_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbclient , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbcontrol , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbpasswd , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbspool , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbstatus , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbtar , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> testparm , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>
wbinfo , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt></dl></dd><dt>Reference, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s1-Samba">Samba</a></dt><dt>Security
Modes, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">Samba Security
Modes</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 Security Mode (User-Level Security)</a></dt><dt>Domain
Security Mode, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-domain-security-mode">Domain
Security Mode (User-Level Security)</a></dt><dt>Server Security Mode,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-server-security-mode">Server
Security Mode (User-Level Security)</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">User-Level
Security</a></dt></dl></dd><dt>Server Types, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-servers">Samba Server Types and
the smb.conf File</a></dt><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">Domain Member
Server</a></dt><dt>Stand Alone, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-standalone">Stand-alone
Server</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">Starting and
Stopping Samba</a></dt><dt>reloading, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samb
a-startstop">Starting and Stopping
Samba</a></dt><dt>restarting, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-startstop">Starting and
Stopping Samba</a></dt><dt>starting, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-startstop">Starting and
Stopping Samba</a></dt><dt>stopping, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-startstop">Starting and
Stopping
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">Command
Line</a></dt><dt>connecting to with Nautilus, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-connect-share">Connecting to a
Samba Share</a></dt><dt>mounting, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-mounting">Mounting the
Share</a></dt></dl></dd><dt>smb.conf, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-servers">Sa
mba Server Types and the smb.conf
File</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 Domain Member Server</a></dt><dt>Anonymous Print Server
example, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-standalone-anonprint">Anonymous
Print Server</a></dt><dt>Anonymous Read Only example, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-standalone-anonreadonly">Anonymous
Read-Only</a></dt><dt>Anonymous Read/Write example, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s4-samba-standalone-anonreadwrite">Anonymous
Read/Write</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-based Domain Member Server</a></dt><dt>PDC using Active Directory,
<a class="indexterm"
href="ch-File_and_Print_Servers.html#samba-rgs-pdc-ads">Primary Domain
Controller (PDC) with Active Directory</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">Secure
Read/Write File and Print Server</a></dt></dl></dd><dt>
smbclient , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">Command
Line</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>with Windows NT 4.0, 2000, ME, and XP, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd><dt> scp (see
OpenSSH)</dt><dt>secondary nameserver (see BIND)</dt><dt> security
plugin (see Security)</dt><dt>Security-Related
Packages</dt><dd><dl><dt>updating secur
ity-related packages, <a class="indexterm"
href="ch-yum.html#sec-Updating_Packages">Updating
Packages</a></dt></dl></dd><dt>Sendmail, <a
class="indexterm"
href="s2-email-mta-sendmail.html">Sendmail</a></dt><dd><dl><dt>additional
resources, <a class="indexterm"
href="s1-email-additional-resources.html">Additional
Resources</a></dt><dt>aliases, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>common
configuration changes, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">Common
Sendmail Configuration Changes</a></dt><dt>default installation, <a
class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-default">The Default
Sendmail Installation</a></dt><dt>LDAP and, <a
class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-ldap">Using Sendmail
with LDAP</a></dt><dt>limitations, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mt
a-sendmail-purpose">Purpose and
Limitations</a></dt><dt>masquerading, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>purpose,
<a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-purpose">Purpose and
Limitations</a></dt><dt>spam, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-sendmail-stopping-spam">Stopping
Spam</a></dt><dt>with UUCP, <a class="indexterm"
href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">Common
Sendmail Configuration
Changes</a></dt></dl></dd><dt>sendmail, <a
class="indexterm" href="s2-email-switchmail.html">Mail Transport
Agent (MTA) Configuration</a></dt><dt>services configuration, <a
class="indexterm" href="ch-Services_and_Daemons.html">Services and
Daemons</a></dt><dd><dl><dt> ssystemctl , <a
class="indexterm" href="s1-services-running.html">Running
Services</a></dt><dt> systemctl , <a class="indexterm"
href="ch-Services_and_Daemo
ns.html#s1-services-configuring">Configuring
Services</a></dt></dl></dd><dt> sftp (see
OpenSSH)</dt><dt>shadow
passwords</dt><dd><dl><dt>overview of, <a
class="indexterm"
href="s1-users-groups-shadow-utilities.html">Shadow
Passwords</a></dt></dl></dd><dt>slab pools (see
/proc/slabinfo )</dt><dt>slapd (see OpenLDAP)</dt><dt> smbcacls
program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbclient , <a class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">Command
Line</a></dt><dt> smbclient program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbcontrol program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbpasswd program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Program
s</a></dt><dt> smbspool program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbstatus program, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt> smbtar program, <a class="indexterm"
href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution
Programs</a></dt><dt>SpamAssassin</dt><dd><dl><dt>using
with Procmail, <a class="indexterm"
href="s2-email-procmail-recipes.html#s3-email-mda-spam">Spam
Filters</a></dt></dl></dd><dt> ssh (see
OpenSSH)</dt><dt>SSH
protocol</dt><dd><dl><dt>authentication, <a
class="indexterm"
href="ch-OpenSSH.html#s2-ssh-protocol-authentication">Authentication</a></dt><dt>configuration
files, <a class="indexterm"
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">Configuration
Files</a></dt><dd><dl><dt>system-wide configuration files,
<a class="indexterm" href="s1-ssh-configuration.html#s
2-ssh-configuration-configs">Configuration
Files</a></dt><dt>user-specific configuration files, <a
class="indexterm"
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">Configuration
Files</a></dt></dl></dd><dt>connection sequence, <a
class="indexterm" href="ch-OpenSSH.html#s2-ssh-conn">Event Sequence
of an SSH Connection</a></dt><dt>features, <a
class="indexterm" href="ch-OpenSSH.html#s2-ssh-features">Main
Features</a></dt><dt>insecure protocols, <a
class="indexterm"
href="s2-ssh-configuration-requiring.html">Requiring SSH for Remote
Connections</a></dt><dt>layers</dt><dd><dl><dt>channels,
<a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-protocol-connection">Channels</a></dt><dt>transport
layer, <a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-protocol-conn-transport">Transport
Layer</a></dt></dl></dd><dt>port forwarding, <a
class="indexterm" href="s2-ssh-beyondshell-tcpip.html">Port
Forwarding</a></dt><dt>requiring for remote login, <a
class="indexterm" href="s
2-ssh-configuration-requiring.html">Requiring SSH for Remote
Connections</a></dt><dt>security risks, <a
class="indexterm" href="ch-OpenSSH.html#s2-ssh-why">Why Use
SSH?</a></dt><dt>version 1, <a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-versions">Protocol
Versions</a></dt><dt>version 2, <a class="indexterm"
href="ch-OpenSSH.html#s2-ssh-versions">Protocol
Versions</a></dt><dt>X11 forwarding, <a class="indexterm"
href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">X11
Forwarding</a></dt></dl></dd><dt> ssh-add , <a
class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Configuring
ssh-agent</a></dt><dt> ssh-agent , <a class="indexterm"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Configuring
ssh-agent</a></dt><dt>SSL, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-mod_ssl">Setting Up an SSL
Server</a></dt><dd><dl><dt>(see also Apache HTTP
Server)</dt></dl></dd><dt>SSL server (see Apache H
TTP 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#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="index
term"
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">Securing Email Client
Communications</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-init"> /etc/sysconfig/init
</a></dt><dt> /etc/sysconfig/ip6tables-config , <a
class="indexterm"
href="ch-The_sysconfig_Directory.html#s2-sysconfig-ip6tables"> /etc/sysconf
ig/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="ch-Network_Interfaces.html">Network Interfaces</a>, <a
class="indexterm"
href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/
Directory</a></dt><dd><dl><dt>(see also
network)</dt></dl></dd><dt> /etc/sysconfig/networking/ directory,
<a class="indexterm"
href="s1-sysconfig-etcsysconf-dir.html">Directorie
s 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/sysconfig/spamassassin ,
<a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-syscon
fig-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 information about, <a
class="indexterm" href="ch-The_sysconfig_Directory.html">The
sysconfig Directory</a></dt><dt>additional resources, <a
class="indexterm"
href="s1-sysconfig-additional-resources.html">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm" href="s1-sysconfig-additional-resource
s.html#s2-sysconfig-installed-documentation">Installed
Documentation</a></dt></dl></dd><dt>directories in, <a
class="indexterm"
href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/
Directory</a></dt><dt>files found in, <a class="indexterm"
href="ch-The_sysconfig_Directory.html#s1-sysconfig-files">Files in the
/etc/sysconfig/ Directory</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 (see system request
key)</dt><dt>system information</dt><dd><dl><dt>file
systems, <a class="indexterm"
href="s1-sysinfo-filesystems.html">File
Systems</a></dt><dd><dl><dt> /dev/shm , <a
class="indexterm" href="s1-sysinfo-filesystems.html">File
Systems</a></dt></dl></dd><dt>gathering, <a
class="indexterm" href="ch-System_Monitoring_Too
ls.html">System Monitoring Tools</a></dt><dt>hardware, <a
class="indexterm"
href="s1-sysinfo-hardware.html">Hardware</a></dt><dt>memory
usage, <a class="indexterm"
href="s1-sysinfo-memory-usage.html">Memory
Usage</a></dt><dt>processes, <a class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">System
Processes</a></dt><dd><dl><dt>currently running, <a
class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">System
Processes</a></dt></dl></dd></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 (see
Authentication Configuration Tool )</dt><dt>system-c
onfig-kdump (see kdump)</dt><dt>system-config-users (see user configuration
and group configuration)</dt><dt> systemctl (see services
configuration)</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 Distribution
Programs</a></dt><dt>time, <a class="indexterm"
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Date
and Time Configuration Tool</a>, <a class="indexterm"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">Configuring
the Date and Time</a></dt><dd><dl><dt>(see also Date and
Time)</dt></dl></dd><dt>time zone, <a
class="indexterm"
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Date
and Time Configuration Tool</a></dt><dd><dl><dt>(see also
Date and Time)</dt></dl></dd><dt>TLB cache (see
hugepages)</dt><dt>TLS, <a class="indexterm"
href="ch-Web_Servers.html#s2-apache-mod_ssl">Setting Up an SSL
Server</a></dt><dd><dl><dt>(see also Apache HTTP
Server)</dt></dl></dd><dt>tool</dt><dd><dl><dt>
Authentication Configuration Tool , <a class="indexterm"
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">The
Authentication Configuration Tool</a></dt></dl></dd><dt> top
, <a class="indexterm"
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">System
Processes</a></dt></dl></div><div
class="indexdiv"><h3>U</h3><dl><dt>updating currently
installed packages</dt><dd><dl><dt>available updates, <a
class="indexterm"
href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating
Packages with Software Update</a></dt></dl></dd><dt>updating
packages with PackageKit</dt><dd><dl><dt>PolicyKit, <a
class="indexterm"
href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating
Packages with Software Upda
te</a></dt></dl></dd><dt>User Accounts (see user
configuration)</dt><dt>user
configuration</dt><dd><dl><dt>adding users, <a
class="indexterm"
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">Adding
a New User</a>, <a class="indexterm"
href="s1-users-configui.html#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>changing full name, <a class="indexterm"
href="s1-users-configui.html#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>changing home directory, <a
class="indexterm"
href="s1-users-configui.html#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>changing login shell, <a class="indexterm"
href="s1-users-configui.html#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>changing password, <a class="indexterm"
href="s1-users-configui.html#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>command line configuration, <a
class="indexterm" href="s1-users-tools
.html#s2-users-cmd-line">Command Line
Configuration</a></dt><dd><dl><dt>passwd, <a
class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt><dt>useradd, <a class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>filtering list of users,
<a class="indexterm" href="s1-users-configui.html">User Manager
Tool</a></dt><dt>modify groups for a user, <a
class="indexterm"
href="s1-users-configui.html#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>modifying users, <a class="indexterm"
href="s1-users-configui.html#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>password</dt><dd><dl><dt>forcing
expiration of, <a class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>removing users, <a
class="indexterm"
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">Rem
oving a User</a></dt><dt>viewing list of users, <a
class="indexterm"
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts">User
Accounts Tool</a>, <a class="indexterm"
href="s1-users-configui.html">User Manager
Tool</a></dt></dl></dd><dt>User Manager (see user
configuration)</dt><dt>user private groups (see
groups)</dt><dd><dl><dt>and shared directories, <a
class="indexterm"
href="s1-users-groups-private-groups.html#s2-users-groups-rationale">Group
Directories</a></dt></dl></dd><dt>useradd
command</dt><dd><dl><dt>user account creation using, <a
class="indexterm"
href="s1-users-tools.html#s2-users-cmd-line">Command Line
Configuration</a></dt></dl></dd><dt>users (see user
configuration)</dt><dd><dl><dt>/etc/passwd, <a
class="indexterm"
href="s1-users-groups-standard-users.html">Standard
Users</a></dt><dt>additional resources, <a
class="indexterm"
href="s1-users-groups-additional-resources.html">Additional
Resources</a></dt><dd><dl><dt>installed
documentation, <a class="indexterm"
href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">Installed
Documentation</a></dt></dl></dd><dt>introducing, <a
class="indexterm" href="ch-Managing_Users_and_Groups.html">Managing
Users and Groups</a></dt><dt>standard, <a class="indexterm"
href="s1-users-groups-standard-users.html">Standard
Users</a></dt><dt>tools for management
of</dt><dd><dl><dt>User Manager, <a class="indexterm"
href="s1-users-tools.html">User and Group Management
Tools</a></dt><dt>useradd, <a class="indexterm"
href="s1-users-tools.html">User and Group Management
Tools</a></dt></dl></dd><dt>UID, <a
class="indexterm" href="ch-Managing_Users_and_Groups.html">Managing
Users and Groups</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>V</h3><dl><dt>virtual file
system (see proc file system)</dt><dt>virtual files (see proc file
system)</dt><dt>virtual host (see Apache HTTP Server)</dt><dt>
vsftpd , <a class="indexterm" href="s2-ftp-servers
.html">FTP Servers</a></dt><dd><dl><dt>(see also
FTP)</dt><dt>additional resources, <a class="indexterm"
href="s2-ftp-resources.html">Additional
Resources</a></dt><dd><dl><dt>installed documentation, <a
class="indexterm"
href="s2-ftp-resources.html#s3-ftp-installed-documentation">Installed
Documentation</a></dt><dt>useful websites, <a
class="indexterm"
href="s2-ftp-resources.html#s3-ftp-useful-websites">Useful
Websites</a></dt></dl></dd><dt>condrestart, <a
class="indexterm" href="s2-ftp-vsftpd-start.html">Starting and
Stopping vsftpd </a></dt><dt>configuration
file</dt><dd><dl><dt> /etc/vsftpd/vsftpd.conf , <a
class="indexterm" href="s2-ftp-vsftpd-conf.html"> vsftpd
Configuration Options</a></dt><dt>access controls, <a
class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-login">Log In Options
and Access Controls</a></dt><dt>anonymous user options, <a
class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-anon">Anonymous User
Options</a></dt>
<dt>daemon options, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-daemon">Daemon
Options</a></dt><dt>directory options, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-dir">Directory
Options</a></dt><dt>file transfer options, <a
class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-file">File Transfer
Options</a></dt><dt>format of, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html"> vsftpd Configuration
Options</a></dt><dt>local user options, <a
class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-usr">Local User
Options</a></dt><dt>logging options, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-log">Logging
Options</a></dt><dt>login options, <a class="indexterm"
href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-login">Log In Options
and Access Controls</a></dt><dt>network options, <a
class="indexterm" href="s2-ftp-vsftpd-conf.html#s3-ftp-vsftpd-conf-opt-ne
t">Network Options</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>restarting, <a
class="indexterm" href="s2-ftp-vsftpd-start.html">Starting and
Stopping vsftpd
</a></dt><dt>RPM</dt><dd><dl><dt>files installed
by, <a class="indexterm" href="s3-ftp-vsftpd-conf.html">Files
Installed with vsftpd </a></dt></dl></dd><dt>security
features, <a class="indexterm" href="s2-ftp-servers.html">FTP
Servers</a></dt><dt>starting, <a class="indexterm"
href="s2-ftp-vsftpd-start.html">Starting and Stopping vsftpd
</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>status, <a class="indexterm"
href="s2-ftp-vsftpd-start.html">Starting and Stopping vsftpd
</a></dt><dt>stopping, <a class="indexterm"
href="s2-ftp-vsftpd-start.html">Starting and Stopping 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 Distribution
Programs</a></dt><dt>web server (see Apache HTTP
Server)</dt><dt>Windows
2000</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd><dt>Windows
98</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd><dt>Windows
ME</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd><dt>Windows NT
4.0</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">Encrypted
Pa
sswords</a></dt></dl></dd><dt>Windows
XP</dt><dd><dl><dt>connecting to shares using Samba, <a
class="indexterm"
href="ch-File_and_Print_Servers.html#s3-samba-encrypted-passwords">Encrypted
Passwords</a></dt></dl></dd></dl></div><div
class="indexdiv"><h3>X</h3><dl><dt>X.500 (see
OpenLDAP)</dt><dt>X.500 Lite (see
OpenLDAP)</dt></dl></div><div
class="indexdiv"><h3>Y</h3><dl><dt>Yum</dt><dd><dl><dt>Additional
Resources, <a class="indexterm"
href="sec-Additional_Resources.html">Additional
Resources</a></dt><dt>configuring plugins, <a
class="indexterm"
href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling,
Configuring and Disabling Yum Plugins</a></dt><dt>configuring Yum and
Yum repositories, <a class="indexterm"
href="sec-Configuring_Yum_and_Yum_Repositories.html">Configuring Yum and Yum
Repositories</a></dt><dt>disabling plugins, <a
class="indexterm"
href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling,
Configu
ring and Disabling Yum Plugins</a></dt><dt>displaying packages with
Yum</dt><dd><dl><dt>yum info, <a class="indexterm"
href="sec-Displaying_Package_Information.html">Displaying Package
Information</a></dt></dl></dd><dt>enabling plugins, <a
class="indexterm"
href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling,
Configuring and Disabling Yum Plugins</a></dt><dt>installing a package
group with Yum, <a class="indexterm"
href="sec-Installing.html">Installing
Packages</a></dt><dt>installing with Yum, <a
class="indexterm" href="sec-Installing.html">Installing
Packages</a></dt><dt>listing packages with
Yum</dt><dd><dl><dt>Glob expressions, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum grouplist, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum list, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum list all, <a class="indexterm"
href=
"sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum list available, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum list installed, <a
class="indexterm" href="sec-Listing_Packages.html">Listing
Packages</a></dt><dt>yum repolist, <a class="indexterm"
href="sec-Listing_Packages.html">Listing
Packages</a></dt></dl></dd><dt>packages and package groups,
<a class="indexterm"
href="sec-Packages_and_Package_Groups.html">Packages and Package
Groups</a></dt><dt>plugins</dt><dd><dl><dt>presto,
<a class="indexterm" href="sec-Plugin_Descriptions.html">Plugin
Descriptions</a></dt><dt>refresh-packagekit, <a
class="indexterm" href="sec-Plugin_Descriptions.html">Plugin
Descriptions</a></dt><dt>rhnplugin, <a class="indexterm"
href="sec-Plugin_Descriptions.html">Plugin
Descriptions</a></dt><dt>security, <a class="indexterm"
href="sec-Plugin_Descriptions.html">Plugin
Descriptions</a></dt></dl></dd><dt>repository, <a
class="indexterm" href="sec-Cre
ating_a_Yum_Repository.html">Creating a Yum
Repository</a></dt><dt>searching packages with
Yum</dt><dd><dl><dt>yum search, <a class="indexterm"
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">Searching
Packages</a></dt></dl></dd><dt>setting [main] options, <a
class="indexterm"
href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">Setting
[main] Options</a></dt><dt>setting [repository] options, <a
class="indexterm"
href="sec-Setting_repository_Options.html">Setting [repository]
Options</a></dt><dt>uninstalling package groups with Yum, <a
class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt><dt>uninstalling packages with Yum, <a
class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt><dd><dl><dt>yum remove package_name, <a
class="indexterm" href="sec-Removing.html">Removing
Packages</a></dt></dl></dd><dt>variables, <a
class="indexterm" href="sec-Using_Yum_Variables.html">Using Yum
Variables</a></dt><dt>Yum
plugins, <a class="indexterm" href="sec-Yum_Plugins.html">Yum
Plugins</a></dt><dt>Yum
repositories</dt><dd><dl><dt>configuring Yum and Yum repositories,
<a class="indexterm"
href="sec-Configuring_Yum_and_Yum_Repositories.html">Configuring Yum and Yum
Repositories</a></dt></dl></dd></dl></dd><dt>Yum
repositories</dt><dd><dl><dt>viewing Yum repositories with
PackageKit, <a class="indexterm"
href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">Setting
the Software Sources</a></dt></dl></dd><dt>Yum
Updates</dt><dd><dl><dt>checking for updates, <a
class="indexterm"
href="ch-yum.html#sec-Checking_For_Updates">Checking For
Updates</a></dt><dt>updating a single package, <a
class="indexterm" href="ch-yum.html#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating all packages and dependencies, <a
class="indexterm" href="ch-yum.html#sec-Updating_Packages">Updating
Packages</a></dt><dt>updating packages, <a
class="indexterm" href="ch-yum.html#sec-Updating_Pack
ages">Updating Packages</a></dt><dt>updating security-related
packages, <a class="indexterm"
href="ch-yum.html#sec-Updating_Packages">Updating
Packages</a></dt></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="app-Revision_History.html"><strong>Prev</strong>Appendix D. Revision
History</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/lease-database.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/lease-database.html
new file mode 100644
index 0000000..fa8dbc7
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/lease-database.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>10.2.2. Lease Database</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP
Server" /><link rel="prev"
href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP
Server" /><link rel="next" href="ch10s02s03.html"
title="10.2.3. Starting and Stopping the 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="s1-dhcp-configuring-server.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n"
href="ch10s02s03.html"><strong>Next</strong></a></li></ul><div
class="section" id="lease-database"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="lease-database">10.2.2. Lease
Database</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">
+ All times in the lease database are in Coordinated Universal Time (UTC), not local
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>Prev</strong>10.2. Configuring
a DHCP Server</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch10s02s03.html"><strong>Next</strong>10.2.3. Starting and
Stopping the Server</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Basic_System_Configuration.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Basic_System_Configuration.html
new file mode 100644
index 0000000..fee7242
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Basic_System_Configuration.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>Part I. Basic System 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="pref-Acknowledgments.html"
title="5. Acknowledgments" /><link rel="next"
href="ch-Language_and_Keyboard_Configuration.html"
title="Chapter 1. Language and Keyboard Configuration"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pref-Acknowledgments.html"><strong>Prev</strong></a></li><li
class="next"><a acces
skey="n"
href="ch-Language_and_Keyboard_Configuration.html"><strong>Next</strong></a></li></ul><div
class="part" id="part-Basic_System_Configuration"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part I. Basic System
Configuration</h1></div></div></div><div
class="partintro" id="id408974"><div></div><div
class="para">
+ This part covers basic system administration tasks such as keyboard configuration,
date and time configuration, and managing users and groups.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a
href="ch-Language_and_Keyboard_Configuration.html">1. Language and Keyboard
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Language_and_Keyboard_Configuration.html#sect-Language_and_Keyboard_Configuration-Language">1.1.
Changing the Language</a></span></dt><dt><span
class="section"><a
href="sect-Language_and_Keyboard_Configuration-Layouts.html">1.2. Changing
the Keyboard
Layout</a></span></dt></dl></dd><dt><span
class="chapter"><a
href="ch-Date_and_Time_Configuration.html">2. Date and Time
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">2.1.
Date and Time Configuration Tool</a></span></dt><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html">2.2.
Command Line Configuration</a></span></dt><dd><dl><
dt><span class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">2.2.1.
Configuring the Date and Time</a></span></dt><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">2.2.2.
Configuring the Network Time
Protocol</a></span></dt></dl></dd><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Additional_Resources.html">2.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="sect-Date_and_Time_Configuration-Additional_Resources.html#sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation">2.3.1.
Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Managing_Users_and_Groups.html">3. Managing Users and
Groups</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-Managing_Users_and_Groups.html
#sect-Managing_Users_and_Groups-User_Accounts">3.1. User Accounts
Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Configuring_an_Account">3.1.1.
Configuring an Account</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Adding_a_New_User">3.1.2.
Adding a New User</a></span></dt><dt><span
class="section"><a
href="ch-Managing_Users_and_Groups.html#sect-Managing_Users_and_Groups-User_Accounts-Removing_a_User">3.1.3.
Removing a User</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-configui.html">3.2. User
Manager Tool</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-configui.html#s2-redhat-config-users-user-new">3.2.1. Adding a
New User</a></span></dt><dt><span
class="section"><a
href="s2-redhat-config-users-group-new.html">3.2.2. Adding a New
Group</a></span></dt><dt><span
class="section"><a
href="s2-redhat-config-users-group-properties.html">3.2.3. Modifying Group
Properties</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-users-tools.html">3.3. User and
Group Management
Tools</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-tools.html#s2-users-cmd-line">3.3.1. Command Line
Configuration</a></span></dt><dt><span
class="section"><a
href="s2-redhat-config-users-process.html">3.3.2. Explaining the
Process</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-users-groups-standard-users.html">3.4. Standard
Users</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-standard-groups.html">3.5. Standard
Groups</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-private-groups.html">3.6. User Private
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-groups-private-groups.html#s2-users-groups-rationale">3.6.1.
Group
Directories</a></span></dt></dl></dd><dt><spa
n class="section"><a
href="s1-users-groups-shadow-utilities.html">3.7. Shadow
Passwords</a></span></dt><dt><span
class="section"><a
href="s1-users-groups-additional-resources.html">3.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">3.8.1.
Installed
Documentation</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>Prev</strong>5. Acknowledgments</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Language_and_Keyboard_Configuration.html"><strong>Next</strong>Chapter 1. Language
and Keyboard Configuration</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Infrastructure_Services.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Infrastructure_Services.html
new file mode 100644
index 0000000..d747700
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Infrastructure_Services.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>Part IV. Infrastructure Services</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="s1-networkscripts-resources.html"
title="6.6. Additional Resources" /><link rel="next"
href="ch-Services_and_Daemons.html" title="Chapter 7. Services and
Daemons" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Services_and_Daemons.html"><strong>Next</strong></a></li></ul><div
class="part" id="part-Infrastructure_Services"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part IV. Infrastructure
Services</h1></div></div></div><div class="partintro"
id="id388214"><div></div><div class="para">
+ This part provides information how to configure services and daemons, configure
authentication, and enable remote logins.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a href="ch-Services_and_Daemons.html">7.
Services and
Daemons</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s1-services-configuring">7.1. Configuring
Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">7.1.1.
Enabling the Service</a></span></dt><dt><span
class="section"><a
href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">7.1.2.
Disabling the
Service</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-services-running.html">7.2.
Running Services</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-running.html#s3-services-running-checking">7.2.1. Checking
the Service Status</a></span></dt><dt><span
class="section"><a
href="s3-services-running-running.html">7.2.2. Running the
Service</a></span></dt><dt><span cla
ss="section"><a
href="s3-services-running-stopping.html">7.2.3. Stopping the
Service</a></span></dt><dt><span
class="section"><a
href="s3-services-running-restarting.html">7.2.4. Restarting the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-services-additional-resources.html">7.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-services-additional-resources.html#s2-services-additional-resources-installed">7.3.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-services-additional-resources-books.html">7.3.2. Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Configuring_Authentication.html">8. Configuring
Authentication</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool">8.1.
The Authentication Configuration
Tool</a></span></dt><dd><dl><dt><span
class="section"><a href="c
h-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1.
Identity & Authentication</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">8.1.2.
Advanced Options</a></span></dt><dt><span
class="section"><a
href="ch-Configuring_Authentication.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3.
Command Line
Version</a></span></dt></dl></dd><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Introduction.html">8.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">8.2.1.
What is SSSD?</a></span></dt><dt><span
class="section"><a
href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html">8.2.2. SSSD
Features</a></span></dt><dt><span
class="section"><a href="chap-SSSD
_User_Guide-Setting_Up_SSSD.html">8.2.3. Setting Up
SSSD</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Configuring_Services.html">8.2.4. Configuring
Services</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Configuring_Domains.html">8.2.5. Configuring
Domains</a></span></dt><dt><span
class="section"><a
href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">8.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">8.2.7.
Configuring a Proxy Domain</a></span></dt><dt><span
class="section"><a
href="chap-SSSD_User_Guide-Troubleshooting.html">8.2.8.
Troubleshooting</a></span></dt><dt><span
class="section"><a
href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">8.2.9.
SSSD Configuration File
Format</a></span></dt></dl></dd></dl></dd><dt><span
c
lass="chapter"><a href="ch-OpenSSH.html">9.
OpenSSH</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-OpenSSH.html#s1-ssh-protocol">9.1. The SSH
Protocol</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-why">9.1.1.
Why Use SSH?</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-features">9.1.2. Main
Features</a></span></dt><dt><span
class="section"><a
href="ch-OpenSSH.html#s2-ssh-versions">9.1.3. Protocol
Versions</a></span></dt><dt><span
class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">9.1.4.
Event Sequence of an SSH
Connection</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-configuration.html">9.2. An
OpenSSH
Configuration</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-configuration.html#s2-ssh-configuration-configs">9.2.1.
Configuration Files</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-sshd.html">9.2.2. Starting an OpenSSH
Server</a></span>
</dt><dt><span class="section"><a
href="s2-ssh-configuration-requiring.html">9.2.3. Requiring SSH for Remote
Connections</a></span></dt><dt><span
class="section"><a
href="s2-ssh-configuration-keypairs.html">9.2.4. Using a Key-Based
Authentication</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-clients.html">9.3. OpenSSH
Clients</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-clients.html#s2-ssh-clients-ssh">9.3.1. Using the ssh
Utility</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-scp.html">9.3.2.
Using the <code class="command">scp</code>
Utility</a></span></dt><dt><span
class="section"><a href="s2-ssh-clients-sftp.html">9.3.3.
Using the <code class="command">sftp</code>
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-ssh-beyondshell.html">9.4. More
Than a Secure
Shell</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">9.4.1. X11
Forwarding</a
</span></dt><dt><span
class="section"><a
href="s2-ssh-beyondshell-tcpip.html">9.4.2. Port
Forwarding</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-openssh-additional-resources.html">9.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-openssh-additional-resources.html#s2-openssh-installed-docs">9.5.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-openssh-useful-websites.html">9.5.2. Useful
Websites</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>Prev</strong>6.6. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Services_and_Daemons.html"><strong>Next</strong>Chapter 7. Services
and Daemons</a></li></ul></bo
dy></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Kernel_Module_and_Driver_Configuration.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Kernel_Module_and_Driver_Configuration.html
new file mode 100644
index 0000000..67a582f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Kernel_Module_and_Driver_Configuration.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>Part VII. Kernel, Module and Driver 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="configuring-automatic-reporting.html"
title="19.8. Configuring Automatic Reporting" /><link rel="next"
href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 20. Manually
Upgrading the Kernel" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="configuring-automatic-reporting.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n"
href="ch-Manually_Upgrading_the_Kernel.html"><strong>Next</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">Part VII. Kernel, Module and Driver
Configuration</h1></div></div></div><div
class="partintro" id="id400034"><div></div><div
class="para">
+ This part covers various tools that assist administrators with kernel customization.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a
href="ch-Manually_Upgrading_the_Kernel.html">20. Manually Upgrading the
Kernel</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">20.1.
Overview of Kernel Packages</a></span></dt><dt><span
class="section"><a href="s1-kernel-preparing.html">20.2.
Preparing to Upgrade</a></span></dt><dt><span
class="section"><a href="s1-kernel-download.html">20.3.
Downloading the Upgraded Kernel</a></span></dt><dt><span
class="section"><a
href="s1-kernel-perform-upgrade.html">20.4. Performing the
Upgrade</a></span></dt><dt><span
class="section"><a
href="sec-Verifying_the_Initial_RAM_Disk_Image.html">20.5. Verifying the
Initial RAM Disk Image</a></span></dt><dt><span
class="section"><a href="s1-kernel-boot-loader.html">20.6.
Verifying the Boot
Loader</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-kernel-boot-loader.htm
l#s3-kernel-boot-loader-grub">20.6.1. Configuring the GRUB Boot
Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-iseries.html">20.6.2. Configuring the OS/400 Boot
Loader</a></span></dt><dt><span
class="section"><a
href="s2-kernel-boot-loader-pseries.html">20.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">21. 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">21.1.
Listing Currently-Loaded Modules</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Information_About_a_Module.html">21.2. Displaying
Information About a Module</a></span></dt><dt><span
class="section"><a href="sec-Loading_a_Module.html">21.3.
Loading a Module</a></span></dt><dt><span
class="section"><a href="sec-Unloading_a_Module.html">21.4.
Unloading a Module</a><
/span></dt><dt><span class="section"><a
href="sec-Setting_Module_Parameters.html">21.5. Setting Module
Parameters</a></span></dt><dt><span
class="section"><a
href="sec-Persistent_Module_Loading.html">21.6. Persistent Module
Loading</a></span></dt><dt><span
class="section"><a
href="sec-Specific_Kernel_Module_Capabilities.html">21.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">21.7.1.
Using Multiple Ethernet Cards</a></span></dt><dt><span
class="section"><a
href="sec-Using_Channel_Bonding.html">21.7.2. Using Channel
Bonding</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html">21.8. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kernel-modules-additional-resources.html#s2-kernel-modules-additional-resources-installed">21.8.1.
Installed Documentation</a></span></dt>
<dt><span class="section"><a
href="s2-kernel-modules-additional-resources-websites.html">21.8.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-kdump.html">22. The kdump Crash
Recovery Service</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-kdump.html#s1-kdump-configuration">22.1. Configuring the kdump
Service</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-gui">22.1.1. Using the Kernel Dump
Configuration Utility</a></span></dt><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-cli">22.1.2. Configuring kdump on
the Command Line</a></span></dt><dt><span
class="section"><a
href="ch-kdump.html#s2-kdump-configuration-testing">22.1.3. Testing the
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-kdump-crash.html">22.2. Analyzing
the Core Dump</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-kdump-crash.html#s2-kdump-cras
h-running">22.2.1. Running the crash
Utility</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-log.html">22.2.2.
Displaying the Message Buffer</a></span></dt><dt><span
class="section"><a
href="s2-kdump-crash-backtrace.html">22.2.3. Displaying a
Backtrace</a></span></dt><dt><span
class="section"><a
href="s2-kdump-crash-processes.html">22.2.4. Displaying a Process
Status</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-memory.html">22.2.5.
Displaying Virtual Memory Information</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-files.html">22.2.6.
Displaying Open Files</a></span></dt><dt><span
class="section"><a href="s2-kdump-crash-exit.html">22.2.7.
Exiting the
Utility</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-kdump-resources.html">22.3.
Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-kdump-resources.html#s2-kdump-resources-installed">22.3.1. Installed
Documentation</a></span><
/dt><dt><span class="section"><a
href="s2-kdump-resources-online.html">22.3.2. Useful
Websites</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="configuring-automatic-reporting.html"><strong>Prev</strong>19.8. Configuring
Automatic Reporting</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Manually_Upgrading_the_Kernel.html"><strong>Next</strong>Chapter 20. Manually
Upgrading the Kernel</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Monitoring_and_Automation.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Monitoring_and_Automation.html
new file mode 100644
index 0000000..62214e7
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Monitoring_and_Automation.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>Part VI. Monitoring and Automation</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="s2-ftp-resources.html" title="15.2.6. Additional
Resources" /><link rel="next"
href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring
Tools" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="ch-Sys
tem_Monitoring_Tools.html"><strong>Next</strong></a></li></ul><div
class="part" id="part-Monitoring_and_Automation"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part VI. Monitoring and
Automation</h1></div></div></div><div
class="partintro" id="id395275"><div></div><div
class="para">
+ This part describes various tools that allow system administrators to monitor system
performance, automate system tasks, and report bugs.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a href="ch-System_Monitoring_Tools.html">16.
System Monitoring
Tools</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">16.1.
System Processes</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-memory-usage.html">16.2.
Memory Usage</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-filesystems.html">16.3.
File Systems</a></span></dt><dt><span
class="section"><a href="s1-sysinfo-hardware.html">16.4.
Hardware</a></span></dt><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html">16.5. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.5.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a
href="ch-Viewing_and_Managing_Log_Files.html">17. Viewing a
nd Managing Log
Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s1-configuring-rsyslog">17.1.
Configuring
rsyslog</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-global-directives">17.1.1.
Global Directives</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-modules">17.1.2.
Modules</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-rules">17.1.3.
Rules</a></span></dt><dt><span
class="section"><a
href="ch-Viewing_and_Managing_Log_Files.html#s2-rsyslog-cmd-options">17.1.4.
<span
class="application"><strong>rsyslog</strong></span> Command
Line
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-logfiles-locating.html">17.2.
Locating Log Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-logfiles-locating.html#configuring-logrotate">17.2.1. Configuring
logrotate</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-logfiles-viewing.html">17.3.
Viewing Log Files</a></span></dt><dt><span
class="section"><a href="s1-logfiles-adding.html">17.4.
Adding a Log File</a></span></dt><dt><span
class="section"><a href="s1-logfiles-examining.html">17.5.
Monitoring Log Files</a></span></dt><dt><span
class="section"><a
href="s1-log-files-additional-resources.html">17.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-log-files-additional-resources.html#s2-log-files-installed-docs">17.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-log-files-useful-websites.html">17.6.2. Useful
Websites</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Automating_System_Tasks.html">18.
Automating System
Tasks</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">18.1. Cron
and Anacron</a></span>
</dt><dd><dl><dt><span class="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-service">18.1.1.
Starting and Stopping the Service</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.2.
Configuring Anacron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">18.1.3.
Configuring Cron Jobs</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">18.1.4.
Controlling Access to Cron</a></span></dt><dt><span
class="section"><a
href="ch-Automating_System_Tasks.html#s2-black-white-listing-of-cron-jobs">18.1.5.
Black/White Listing of Cron
Jobs</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-autotasks-at-batch.html">18.2. At
and Batch</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-at-batch.html#s2-autotasks-at-configuring">18.2.1.
Configuring At Jobs</a></s
pan></dt><dt><span class="section"><a
href="s2-autotasks-batch-configuring.html">18.2.2. Configuring Batch
Jobs</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-viewing.html">18.2.3. Viewing Pending
Jobs</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-commandline-options.html">18.2.4. Additional Command Line
Options</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-controlling-access.html">18.2.5. Controlling
Access to At and Batch</a></span></dt><dt><span
class="section"><a
href="s2-autotasks-at-batch-service.html">18.2.6. Starting and Stopping the
Service</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html">18.3. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">18.3.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-abrt.ht
ml">19. Automatic Bug-Reporting Tool
(ABRT)</a></span></dt><dd><dl><dt><span
class="section"><a href="ch-abrt.html#id443090">19.1.
Overview</a></span></dt><dt><span
class="section"><a href="ch19s02.html">19.2. Installing and
Running ABRT</a></span></dt><dt><span
class="section"><a href="abrt-plugins.html">19.3. ABRT
Plugins</a></span></dt><dd><dl><dt><span
class="section"><a
href="abrt-plugins.html#analyzer-plugins">19.3.1. Analyzer
Plugins</a></span></dt><dt><span
class="section"><a href="reporter-plugins.html">19.3.2.
Reporter Plugins</a></span></dt><dt><span
class="section"><a
href="configuring-plugins-in-the-gui.html">19.3.3. Plugin Configuration in
the GUI</a></span></dt></dl></dd><dt><span
class="section"><a href="generating-backtrace.html">19.4.
Generating
Backtraces</a></span></dt><dd><dl><dt><span
class="section"><a
href="generating-backtrace.html#troubleshooting">19.4.1. Troubleshooting
Backtrace
Generation</a></span></dt></dl></dd><dt><span
class="section"><a hre
f="ch19s05.html">19.5. Using the Command Line
Interface</a></span></dt><dd><dl><dt><span
class="section"><a href="ch19s05.html#id483939">19.5.1.
Viewing Crashes</a></span></dt><dt><span
class="section"><a href="ch19s05s02.html">19.5.2. Reporting
Crashes</a></span></dt><dt><span
class="section"><a href="ch19s05s03.html">19.5.3. Deleting
Crashes</a></span></dt></dl></dd><dt><span
class="section"><a href="configuring.html">19.6. Configuring
ABRT</a></span></dt><dt><span
class="section"><a
href="configuring-centralized-crash-collection.html">19.7. Configuring
Centralized Crash
Collection</a></span></dt><dd><dl><dt><span
class="section"><a
href="configuring-centralized-crash-collection.html#id462013">19.7.1. Testing
ABRT's Crash Detection</a></span></dt><dt><span
class="section"><a href="testing-upload-method.html">19.7.2.
Testing the Upload
Method</a></span></dt></dl></dd><dt><span
class="section"><a
href="configuring-automatic-reporting.html">19.8. Configuring Automatic
Reporti
ng</a></span></dt></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-ftp-resources.html"><strong>Prev</strong>15.2.6. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-System_Monitoring_Tools.html"><strong>Next</strong>Chapter 16. System
Monitoring Tools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Networking.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Networking.html
new file mode 100644
index 0000000..a185dbb
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Networking.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>Part III. Networking</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev"
href="ch-Graphical_Package_Management-sec-Additional_Resources.html"
title="5.4. Additional Resources" /><link rel="next"
href="ch-Network_Interfaces.html" title="Chapter 6. Network
Interfaces" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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_Resources.html"><strong>Pr
ev</strong></a></li><li class="next"><a
accesskey="n"
href="ch-Network_Interfaces.html"><strong>Next</strong></a></li></ul><div
class="part" id="part-Networking"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part III. Networking</h1></div></div></div><div
class="partintro" id="id407004"><div></div><div
class="para">
+ This part describes how to configure the network on Fedora.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a href="ch-Network_Interfaces.html">6.
Network Interfaces</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Network_Interfaces.html#s1-networkscripts-files">6.1. Network
Configuration Files</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-interfaces.html">6.2. Interface Configuration
Files</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">6.2.1.
Ethernet Interfaces</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-chan.html">6.2.2. Channel Bonding
Interfaces</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-alias.html">6.2.3. Alias and Clone
Files</a></span></dt><dt><span
class="section"><a
href="s2-networkscripts-interfaces-ppp0.html">6.2.4. Dialup
Interfaces</a></span></dt><dt><span
class="section"><a href="s2-netw
orkscripts-interfaces-other.html">6.2.5. Other
Interfaces</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-networkscripts-control.html">6.3.
Interface Control Scripts</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-static-routes.html">6.4. Configuring Static
Routes</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-functions.html">6.5. Network Function
Files</a></span></dt><dt><span
class="section"><a
href="s1-networkscripts-resources.html">6.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-networkscripts-resources.html#s2-networkscripts-docs-inst">6.6.1.
Installed
Documentation</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>Prev</strong>5.4. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li cla
ss="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Network_Interfaces.html"><strong>Next</strong>Chapter 6. Network
Interfaces</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Package_Management.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Package_Management.html
new file mode 100644
index 0000000..66be885
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Package_Management.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>Part II. Package Management</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="s1-users-groups-additional-resources.html"
title="3.8. Additional Resources" /><link rel="next"
href="ch-yum.html" title="Chapter 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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="ch-yum.htm
l"><strong>Next</strong></a></li></ul><div
class="part" id="part-Package_Management"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part II. Package
Management</h1></div></div></div><div
class="partintro" id="id406967"><div></div><div
class="para">
+ All software on a Fedora system is divided into RPM packages, which can be installed,
upgraded, or removed. This part describes how to manage packages on Fedora using 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="toc"><p><strong>Table of
Contents</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. Checking For
and Updating
Packages</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-yum.html#sec-Checking_For_Updates">4.1.1. Checking For
Updates</a></span></dt><dt><span
class="section"><a
href="ch-yum.html#sec-Updating_Packages">4.1.2. Updating
Packages</a></span></dt><dt><span
class="section"><a
href="ch-yum.html#sec-Preserving_Configuration_File_Changes">4.1.3.
Preserving Configuration File
Changes</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html">4.2. Packages and Package
Groups</a></span></dt><dd><dl><dt><span
class="section"><a
href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">4.2.1.
Searching Packages</a></span></dt><dt><span
class="section"><a href="sec
-Listing_Packages.html">4.2.2. Listing
Packages</a></span></dt><dt><span
class="section"><a
href="sec-Displaying_Package_Information.html">4.2.3. Displaying Package
Information</a></span></dt><dt><span
class="section"><a href="sec-Installing.html">4.2.4.
Installing Packages</a></span></dt><dt><span
class="section"><a href="sec-Removing.html">4.2.5. Removing
Packages</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Configuring_Yum_and_Yum_Repositories.html">4.3. Configuring Yum and
Yum Repositories</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.
Setting [main] Options</a></span></dt><dt><span
class="section"><a
href="sec-Setting_repository_Options.html">4.3.2. Setting [repository]
Options</a></span></dt><dt><span
class="section"><a href="sec-Using_Yum_Variables.html">4.3.3.
Using Yum Variables</a></span></dt><dt><span
class="section"><a href="sec-Creating_a_Yum_Repository.h
tml">4.3.4. Creating a Yum
Repository</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Yum_Plugins.html">4.4. Yum
Plugins</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.
Enabling, Configuring and Disabling Yum
Plugins</a></span></dt><dt><span
class="section"><a
href="sec-Installing_More_Yum_Plugins.html">4.4.2. Installing Additional Yum
Plugins</a></span></dt><dt><span
class="section"><a href="sec-Plugin_Descriptions.html">4.4.3.
Plugin
Descriptions</a></span></dt></dl></dd><dt><span
class="section"><a href="sec-Additional_Resources.html">4.5.
Additional
Resources</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.
Updating Packages with Software
Update</a></span></dt><dd><dl><dt><span
class="section"><a hr
ef="ch-PackageKit.html#sec-Setting_preferences_for_checking_for_updates">5.1.1.
Setting the Update-Checking Interval</a></span></dt><dt><span
class="section"><a
href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">5.1.2.
Setting the Software
Sources</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-Using_Add_Remove_Software.html">5.2. Using Add/Remove
Software</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.
Refreshing Software Sources (Yum
Repositories)</a></span></dt><dt><span
class="section"><a
href="sec-Finding_Packages_with_Filters.html">5.2.2. Finding Packages with
Filters</a></span></dt><dt><span
class="section"><a
href="sec-Installing_and_Removing_Packages_and_Dependencies.html">5.2.3.
Installing and Removing Packages (and
Dependencies)</a></span></dt><dt><span
class="section"><a
href="sec-Installing_and_Removing_Package_Groups.html">5.
2.4. Installing and Removing Package
Groups</a></span></dt><dt><span
class="section"><a
href="sec-Viewing_the_Transaction_Log.html">5.2.5. Viewing the Transaction
Log</a></span></dt></dl></dd><dt><span
class="section"><a
href="sec-PackageKit_Architecture.html">5.3. PackageKit
Architecture</a></span></dt><dt><span
class="section"><a
href="ch-Graphical_Package_Management-sec-Additional_Resources.html">5.4.
Additional
Resources</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>Prev</strong>3.8. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-yum.html"><strong>Next</strong>Chapter 4. Yum</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Servers.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Servers.html
new file mode 100644
index 0000000..2dbeb64
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/part-Servers.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>Part V. Servers</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="s2-openssh-useful-websites.html"
title="9.5.2. Useful Websites" /><link rel="next"
href="ch-DHCP_Servers.html" title="Chapter 10. DHCP Servers"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-openssh-useful-websites.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="ch-DHCP_Server
s.html"><strong>Next</strong></a></li></ul><div
class="part" id="part-Servers"><div
class="titlepage"><div><div text-align="center"><h1
class="title">Part V. Servers</h1></div></div></div><div
class="partintro" id="id388251"><div></div><div
class="para">
+ This part discusses various topics related to servers such as how to set up a Web
server or share files and directories over the network.
+ </div><div class="toc"><p><strong>Table of
Contents</strong></p><dl><dt><span
class="chapter"><a href="ch-DHCP_Servers.html">10. DHCP
Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DHCP_Servers.html#s1-dhcp-why">10.1. Why Use
DHCP?</a></span></dt><dt><span
class="section"><a
href="s1-dhcp-configuring-server.html">10.2. Configuring a DHCP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-dhcp-configuring-server.html#config-file">10.2.1. Configuration
File</a></span></dt><dt><span
class="section"><a href="lease-database.html">10.2.2. Lease
Database</a></span></dt><dt><span
class="section"><a href="ch10s02s03.html">10.2.3. Starting
and Stopping the Server</a></span></dt><dt><span
class="section"><a href="dhcp-relay-agent.html">10.2.4. DHCP
Relay Agent</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-dhcp-configuring-client.html">10.3. Configuring a DHCP
Client</a></span></dt><dt><span
class="section"><a href="sect-Configu
ring_a_Multihomed_DHCP_Server.html">10.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">10.4.1.
Host
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">10.5.
DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span
class="section"><a
href="s1-dhcp-additional-resources.html">10.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">10.6.1.
Installed
Documentation</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-DNS_Servers.html">11. DNS
Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNS_Servers.html#s1-Introduction_to_DNS">11.1. Introduction to
DNS</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-zones">11.1.1. Nameserver
Zones</a></
span></dt><dt><span class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-nameservers">11.1.2. Nameserver
Types</a></span></dt><dt><span
class="section"><a
href="ch-DNS_Servers.html#s2-dns-introduction-bind">11.1.3. BIND as a
Nameserver</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-BIND.html">11.2.
BIND</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-BIND.html#s2-bind-namedconf">11.2.1. Configuring the named
Service</a></span></dt><dt><span
class="section"><a href="s2-bind-zone.html">11.2.2. Editing
Zone Files</a></span></dt><dt><span
class="section"><a href="s2-bind-rndc.html">11.2.3. Using the
rndc Utility</a></span></dt><dt><span
class="section"><a href="s2-bind-dig.html">11.2.4. Using the
dig Utility</a></span></dt><dt><span
class="section"><a href="s2-bind-features.html">11.2.5.
Advanced Features of BIND</a></span></dt><dt><span
class="section"><a href="s2-bind-mistakes.html">11.2.6.
Common Mistakes to Avoid</a></span></dt><dt><s
pan class="section"><a
href="s2-bind-additional-resources.html">11.2.7. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Web_Servers.html">12. Web
Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">12.1. The Apache HTTP
Server</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-features">12.1.1. New
Features</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-changes">12.1.2. Notable
Changes</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-version2-migrating">12.1.3. Updating the
Configuration</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-running">12.1.4. Running the httpd
Service</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-editing">12.1.5. Editing the
Configuration Files</a></span></dt><dt
<span class="section"><a
href="ch-Web_Servers.html#s2-apache-dso">12.1.6. Working with
Modules</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-virtualhosts">12.1.7. Setting Up Virtual
Hosts</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-mod_ssl">12.1.8. Setting Up an SSL
Server</a></span></dt><dt><span
class="section"><a
href="ch-Web_Servers.html#s2-apache-resources">12.1.9. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Mail_Servers.html">13. Mail
Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s1-email-protocols">13.1. Email
Protocols</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-send">13.1.1. Mail Transport
Protocols</a></span></dt><dt><span
class="section"><a
href="ch-Mail_Servers.html#s2-email-protocols-client">13.1.2. Mail Access
Protocols</a></span></dt></dl></dd><dt>
<span class="section"><a href="s1-email-types.html">13.2.
Email Program
Classifications</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-types.html#s2-email-types-mta">13.2.1. Mail Transport
Agent</a></span></dt><dt><span
class="section"><a href="s2-email-types-mda.html">13.2.2.
Mail Delivery Agent</a></span></dt><dt><span
class="section"><a href="s2-email-types-mua.html">13.2.3.
Mail User Agent</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mta.html">13.3. Mail
Transport Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mta.html#s2-email-mta-postfix">13.3.1.
Postfix</a></span></dt><dt><span
class="section"><a href="s2-email-mta-sendmail.html">13.3.2.
Sendmail</a></span></dt><dt><span
class="section"><a href="s2-email-mta-fetchmail.html">13.3.3.
Fetchmail</a></span></dt><dt><span
class="section"><a href="s2-email-switchmail.html">13.3.4.
Mail Transport Agent (MTA)
Configuration</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mda.html">13.4. Mail
Delivery Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mda.html#s2-email-procmail-configuration">13.4.1. Procmail
Configuration</a></span></dt><dt><span
class="section"><a
href="s2-email-procmail-recipes.html">13.4.2. Procmail
Recipes</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-email-mua.html">13.5. Mail User
Agents</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-mua.html#s2-email-security">13.5.1. Securing
Communication</a></span></dt></dl></dd><dt><span
class="section"><a
href="s1-email-additional-resources.html">13.6. Additional
Resources</a></span></dt><dd><dl><dt><span
class="section"><a
href="s1-email-additional-resources.html#s2-email-installed-docs">13.6.1.
Installed Documentation</a></span></dt><dt><span
class="section"><a
href="s2-email-useful-websites.html">13.6.2. Useful
Websites</a></span></dt><dt><span
class="section"><a href="s2-email-relat
ed-books.html">13.6.3. Related
Books</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-Directory_Servers.html">14.
Directory Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s1-OpenLDAP">14.1.
OpenLDAP</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-introduction">14.1.1. Introduction to
LDAP</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-installation">14.1.2. Installing the
OpenLDAP Suite</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-configuration">14.1.3. Configuring an
OpenLDAP Server</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-running">14.1.4. Running an OpenLDAP
Server</a></span></dt><dt><span
class="section"><a
href="ch-Directory_Servers.html#s2-ldap-pam">14.1.5. Configuring a System to
Authenticate Using OpenLDAP</a></span></dt><dt><span
class="sec
tion"><a
href="ch-Directory_Servers.html#s2-ldap-resources">14.1.6. Additional
Resources</a></span></dt></dl></dd></dl></dd><dt><span
class="chapter"><a href="ch-File_and_Print_Servers.html">15.
File Servers</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s1-Samba">15.1.
Samba</a></span></dt><dd><dl><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#samba-rgs-overview">15.1.1. Introduction
to Samba</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-daemons">15.1.2. Samba Daemons
and Related Services</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-connect-share">15.1.3.
Connecting to a Samba Share</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-configuring">15.1.4.
Configuring a Samba Server</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-startstop">15.1.5. S
tarting and Stopping Samba</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-servers">15.1.6. Samba Server
Types and the <code class="filename">smb.conf</code>
File</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-security-modes">15.1.7. Samba
Security Modes</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-account-info-dbs">15.1.8. Samba
Account Information Databases</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-network-browsing">15.1.9. Samba
Network Browsing</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-cups">15.1.10. Samba with CUPS
Printing Support</a></span></dt><dt><span
class="section"><a
href="ch-File_and_Print_Servers.html#s2-samba-programs">15.1.11. Samba
Distribution Programs</a></span></dt><dt><span
class="section"><a href="ch-File_and_Print_Servers.html#s2
-samba-resources">15.1.12. Additional
Resources</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-FTP.html">15.2.
FTP</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-FTP.html#s2-ftp-protocol">15.2.1.
The File Transfer Protocol</a></span></dt><dt><span
class="section"><a href="s2-ftp-servers.html">15.2.2. FTP
Servers</a></span></dt><dt><span
class="section"><a href="s3-ftp-vsftpd-conf.html">15.2.3.
Files Installed with <code class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-start.html">15.2.4. Starting and Stopping <code
class="command">vsftpd</code>
</a></span></dt><dt><span class="section"><a
href="s2-ftp-vsftpd-conf.html">15.2.5. <code
class="command">vsftpd</code> Configuration
Options</a></span></dt><dt><span
class="section"><a href="s2-ftp-resources.html">15.2.6.
Additional
Resources</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p" hr
ef="s2-openssh-useful-websites.html"><strong>Prev</strong>9.5.2. Useful
Websites</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-DHCP_Servers.html"><strong>Next</strong>Chapter 10. DHCP
Servers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01.html
new file mode 100644
index 0000000..bebfefb
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01.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>Preface</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="index.html" title="Deployment Guide" /><link
rel="prev" href="index.html" title="Deployment Guide"
/><link rel="next" href="sect-Preface-Book_Organization.html"
title="2. How to Read this Book" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Preface-Book_Organization.html"><strong>Next
</strong></a></li></ul><div xml:lang="en-US"
class="preface" id="id608297" lang="en-US"><div
class="titlepage"><div><div><h1 id="id608297"
class="title">Preface</h1></div></div></div><div
class="para">
+ The <em class="citetitle">Deployment Guide</em> contains
information on how to customize the Fedora 15 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">
+ This manual discusses many intermediate topics such as the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Installing and managing packages using the graphical <span
class="application"><strong>PackageKit</strong></span> and
command line <span
class="application"><strong>Yum</strong></span> package
managers
+ </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 user-space crash data
with the <span class="application"><strong>Automatic Bug Reporting
Tool</strong></span>, and 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"
id="sect-Preface-Target_Audience">1. Target
Audience</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 <em class="citetitle">Fedora 15
Installation Guide</em>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="index.html"><strong>Prev</strong>Deployment
Guide</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Preface-Book_Organization.html"><strong>Next</strong>2. How
to Read this Book</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03.html
new file mode 100644
index 0000000..f7d46f5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>3. Document Conventions</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="pr01.html" title="Preface" /><link rel="prev"
href="sect-Preface-Book_Organization.html" title="2. How to Read this
Book" /><link rel="next" href="pr01s03s02.html"
title="3.2. Pull-quote Conventions" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03s02.html">
<strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="section" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="id567841">3. Document
Conventions</h2></div></div></div><div
class="para">
+ This manual uses several conventions to highlight certain words and phrases and draw
attention to specific pieces of information.
+ </div><div class="para">
+ In PDF and paper editions, this manual uses typefaces drawn from the <a
href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>
set. The Liberation Fonts set is also used in HTML editions if the set is installed on
your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat
Enterprise Linux 5 and later includes the Liberation Fonts set by default.
+ </div><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id426550">3.1. Typographic
Conventions</h3></div></div></div><div
class="para">
+ Four typographic conventions are used to call attention to specific words and phrases.
These conventions, and the circumstances they apply to, are as follows.
+ </div><div class="para">
+ <code class="literal">Mono-spaced Bold</code>
+ </div><div class="para">
+ Used to highlight system input, including shell commands, file names and paths. Also
used to highlight keycaps and key combinations. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ To see the contents of the file <code
class="filename">my_next_bestselling_novel</code> in your current
working directory, enter the <code class="command">cat
my_next_bestselling_novel</code> command at the shell prompt and press <span
class="keycap"><strong>Enter</strong></span> to execute the
command.
+ </div></blockquote></div><div class="para">
+ The above includes a file name, a shell command and a keycap, all presented in
mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps by the hyphen connecting each part
of a key combination. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ Press <span
class="keycap"><strong>Enter</strong></span> to execute the
command.
+ </div><div class="para">
+ Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F2</strong></span> to switch to the
first virtual terminal. Press <span
class="keycap"><strong>Ctrl</strong></span>+<span
class="keycap"><strong>Alt</strong></span>+<span
class="keycap"><strong>F1</strong></span> to return to your
X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights
two key combinations (each a set of three keycaps with each set pressed simultaneously).
+ </div><div class="para">
+ If source code is discussed, class names, methods, functions, variable names and
returned values mentioned within a paragraph will be presented as above, in <code
class="literal">mono-spaced bold</code>. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ File-related classes include <code
class="classname">filesystem</code> for file systems, <code
class="classname">file</code> for files, and <code
class="classname">dir</code> for directories. Each class has its own
associated set of permissions.
+ </div></blockquote></div><div class="para">
+ <span class="application"><strong>Proportional
Bold</strong></span>
+ </div><div class="para">
+ This denotes words or phrases encountered on a system, including application names;
dialog box text; labeled buttons; check-box and radio button labels; menu titles and
sub-menu titles. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ Choose <span
class="guimenu"><strong>System</strong></span> → <span
class="guisubmenu"><strong>Preferences</strong></span> →
<span class="guimenuitem"><strong>Mouse</strong></span>
from the main menu bar to launch <span
class="application"><strong>Mouse
Preferences</strong></span>. In the <span
class="guilabel"><strong>Buttons</strong></span> tab, click
the <span class="guilabel"><strong>Left-handed
mouse</strong></span> check box and click <span
class="guibutton"><strong>Close</strong></span> to switch
the primary mouse button from the left to the right (making the mouse suitable for use in
the left hand).
+ </div><div class="para">
+ To insert a special character into a <span
class="application"><strong>gedit</strong></span> file,
choose <span
class="guimenu"><strong>Applications</strong></span> →
<span
class="guisubmenu"><strong>Accessories</strong></span> →
<span class="guimenuitem"><strong>Character
Map</strong></span> from the main menu bar. Next, choose <span
class="guimenu"><strong>Search</strong></span> → <span
class="guimenuitem"><strong>Find…</strong></span> from the
<span class="application"><strong>Character
Map</strong></span> menu bar, type the name of the character in the <span
class="guilabel"><strong>Search</strong></span> field and
click <span
class="guibutton"><strong>Next</strong></span>. The
character you sought will be highlighted in the <span
class="guilabel"><strong>Character Table</strong></span>.
Double-click this highlighted character to place it in the <span
class="guilabel"><strong>Text to copy</strong></span> field
and then click the <span class="guibutton"><stron
g>Copy</strong></span> button. Now switch back to your document and choose
<span class="guimenu"><strong>Edit</strong></span> →
<span class="guimenuitem"><strong>Paste</strong></span>
from the <span
class="application"><strong>gedit</strong></span> menu
bar.
+ </div></blockquote></div><div class="para">
+ The above text includes application names; system-wide menu names and items;
application-specific menu names; and buttons and text found within a GUI interface, all
presented in proportional bold and all distinguishable by context.
+ </div><div class="para">
+ <code class="command"><em
class="replaceable"><code>Mono-spaced Bold
Italic</code></em></code> or <span
class="application"><strong><em
class="replaceable"><code>Proportional Bold
Italic</code></em></strong></span>
+ </div><div class="para">
+ Whether mono-spaced bold or proportional bold, the addition of italics indicates
replaceable or variable text. Italics denotes text you do not input literally or displayed
text that changes depending on circumstance. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ To connect to a remote machine using ssh, type <code
class="command">ssh <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>domain.name</code></em></code>
at a shell prompt. If the remote machine is <code
class="filename">example.com</code> and your username on that machine
is john, type <code class="command">ssh john(a)example.com</code>.
+ </div><div class="para">
+ The <code class="command">mount -o remount <em
class="replaceable"><code>file-system</code></em></code>
command remounts the named file system. For example, to remount the <code
class="filename">/home</code> file system, the command is <code
class="command">mount -o remount /home</code>.
+ </div><div class="para">
+ To see the version of a currently installed package, use the <code
class="command">rpm -q <em
class="replaceable"><code>package</code></em></code>
command. It will return a result as follows: <code class="command"><em
class="replaceable"><code>package-version-release</code></em></code>.
+ </div></blockquote></div><div class="para">
+ Note the words in bold italics above — username, domain.name, file-system, package,
version and release. Each word is a placeholder, either for text you enter when issuing a
command or for text displayed by the system.
+ </div><div class="para">
+ Aside from standard usage for presenting the title of a work, italics denotes the
first use of a new and important term. For example:
+ </div><div class="blockquote"><blockquote
class="blockquote"><div class="para">
+ Publican is a <em class="firstterm">DocBook</em> publishing
system.
+ </div></blockquote></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Preface-Book_Organization.html"><strong>Prev</strong>2. How
to Read this Book</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03s02.html"><strong>Next</strong>3.2. Pull-quote
Conventions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03s02.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03s02.html
new file mode 100644
index 0000000..ed9925c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03s02.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>3.2. Pull-quote Conventions</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="pr01s03.html" title="3. Document Conventions" /><link
rel="prev" href="pr01s03.html" title="3. Document
Conventions" /><link rel="next" href="pr01s03s03.html"
title="3.3. Notes and Warnings" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03s03.html"><strong>Next</strong></a></li><
/ul><div class="section"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id420638">3.2. Pull-quote
Conventions</h3></div></div></div><div
class="para">
+ Terminal output and source code listings are set off visually from the surrounding
text.
+ </div><div class="para">
+ Output sent to a terminal is set in <code
class="computeroutput">mono-spaced roman</code> and presented thus:
+ </div><pre class="screen">books Desktop documentation
drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</pre><div
class="para">
+ Source-code listings are also set in <code
class="computeroutput">mono-spaced roman</code> but add syntax
highlighting as follows:
+ </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>Prev</strong>3. Document
Conventions</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03s03.html"><strong>Next</strong>3.3. Notes and
Warnings</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03s03.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03s03.html
new file mode 100644
index 0000000..33851e1
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/pr01s03s03.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>3.3. Notes and Warnings</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="pr01s03.html" title="3. Document Conventions" /><link
rel="prev" href="pr01s03s02.html" title="3.2. Pull-quote
Conventions" /><link rel="next"
href="sect-Preface-Feedback.html" title="4. Feedback"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="pr01s03s02.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Preface-Feedback.html"><strong>Nex
t</strong></a></li></ul><div
class="section"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="id542294">3.3. Notes and
Warnings</h3></div></div></div><div class="para">
+ Finally, we use three visual styles to draw attention to information that might
otherwise be overlooked.
+ </div><div class="note"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a
note should have no negative consequences, but you might miss out on a trick that makes
your life easier.
+ </div></div></div><div class="important"><div
class="admonition_header"><h2>Important</h2></div><div
class="admonition"><div class="para">
+ Important boxes detail things that are easily missed: configuration changes that only
apply to the current session, or services that need restarting before an update will
apply. Ignoring a box labeled 'Important' will not cause data loss but may cause
irritation and frustration.
+ </div></div></div><div class="warning"><div
class="admonition_header"><h2>Warning</h2></div><div
class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="pr01s03s02.html"><strong>Prev</strong>3.2. Pull-quote
Conventions</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Preface-Feedback.html"><strong>Next</strong>4. Feedback</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/pref-Acknowledgments.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/pref-Acknowledgments.html
new file mode 100644
index 0000000..1eca95e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/pref-Acknowledgments.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="pr01.html" title="Preface" /><link rel="prev"
href="sect-Preface-Feedback.html" title="4. Feedback" /><link
rel="next" href="part-Basic_System_Configuration.html"
title="Part I. Basic System 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="sect-Preface-Feedback.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="part-Basic_System_C
onfiguration.html"><strong>Next</strong></a></li></ul><div
class="section" id="pref-Acknowledgments"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="pref-Acknowledgments">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/h...;.
+ </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, KarstenWade, Lucy Ringland,
Marcela Mašláňová, Mark Johnson, Michael Behm, Michael Behm, Miroslav Lichvár, Radek
Vokál, Rahul Kavalapara, Rahul Sundaram, Sandra Moore, Zbyšek Mráz and Jan Včelák, among
many others.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Preface-Feedback.html"><strong>Prev</strong>4. Feedback</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="part-Basic_System_Configuration.html"><strong>Next</strong>Part I. Basic
System Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/reporter-plugins.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/reporter-plugins.html
new file mode 100644
index 0000000..4672d8c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/reporter-plugins.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>19.3.2. Reporter Plugins</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="abrt-plugins.html" title="19.3. ABRT Plugins" /><link
rel="prev" href="abrt-plugins.html" title="19.3. ABRT
Plugins" /><link rel="next"
href="configuring-plugins-in-the-gui.html" title="19.3.3. Plugin
Configuration in the GUI" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="abrt-plugins.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="confi
guring-plugins-in-the-gui.html"><strong>Next</strong></a></li></ul><div
class="section" id="reporter-plugins"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="reporter-plugins">19.3.2. Reporter
Plugins</h3></div></div></div><div class="para">
+ These plugins gather the crash data acquired by the analyzer plugins, combine the
data with any user input (such as comments about the crash, reproducibility, etc.), and
provide a specific output. Each of these plugins is configurable in its corresponding
configuration file placed in the <code
class="filename">/etc/abrt/plugins/</code> directory or in the <span
class="application"><strong>ABRT</strong></span> GUI
application (for more information on reporter plugin configuration in the <span
class="application"><strong>ABRT</strong></span> GUI
application, refer to <a class="xref"
href="configuring-plugins-in-the-gui.html">Section 19.3.3, “Plugin
Configuration in the GUI”</a>).
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span
class="term">MailX</span></dt><dd><div
class="para">
+ — Sends a crash report via the <span
class="application"><strong>mailx</strong></span> utility
to a specified email address.
+ </div></dd><dt class="varlistentry"><span
class="term">Report Uploader</span></dt><dd><div
class="para">
+ — Uploads a tarball with crash data into a <code
class="systemitem">FTP</code>/<code
class="systemitem">SCP</code> server
+ </div></dd><dt class="varlistentry"><span
class="term">Bugzilla</span></dt><dd><div
class="para">
+ — Reports crashes into Bugzilla in the form of Bugzilla database entries.
+ </div></dd><dt class="varlistentry"><span
class="term">Logger</span></dt><dd><div
class="para">
+ — Creates a crash report and saves it to a specified local file.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="abrt-plugins.html"><strong>Prev</strong>19.3. ABRT
Plugins</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="configuring-plugins-in-the-gui.html"><strong>Next</strong>19.3.3. Plugin
Configuration in the GUI</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-BIND.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-BIND.html
new file mode 100644
index 0000000..45ee4c1
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-BIND.html
@@ -0,0 +1,338 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-DNS_Servers.html" title="Chapter 11. DNS Servers"
/><link rel="prev" href="ch-DNS_Servers.html"
title="Chapter 11. DNS Servers" /><link rel="next"
href="s2-bind-zone.html" title="11.2.2. Editing Zone 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="ch-DNS_Servers.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-zone.html"><
strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="section" id="s1-BIND"
lang="en-US"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-BIND">11.2. BIND</h2></div></div></div><a
id="id647341" class="indexterm"></a><div
class="para">
+ This chapter covers <code class="systemitem">BIND</code>
(Berkeley Internet Name Domain), the DNS server included in Fedora. It focuses on the
structure of its configuration files, and describes how to administer it both locally and
remotely.
+ </div><div class="section"
id="s2-bind-namedconf"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-namedconf">11.2.1. Configuring the named
Service</h3></div></div></div><a id="id647336"
class="indexterm"></a><div class="para">
+ When the <code class="systemitem">named</code> service is
started, it reads the configuration from the files as described in <a
class="xref"
href="s1-BIND.html#table-bind-namedconf-files">Table 11.1, “The named service
configuration files”</a>.
+ </div><a id="id647306"
class="indexterm"></a><a id="id647291"
class="indexterm"></a><a id="id647278"
class="indexterm"></a><div class="table"
id="table-bind-namedconf-files"><h6>Table 11.1. The named service
configuration files</h6><div class="table-contents"><table
summary="The named service configuration files"
border="1"><colgroup><col width="38%"
class="path" /><col width="63%" class="description"
/></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc/named.conf</code>
+ </td><td>
+ The main configuration file.
+ </td></tr><tr><td>
+ <code class="filename">/etc/named/</code>
+ </td><td>
+ An auxiliary directory for configuration files that are included in the main
configuration file.
+ </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>Running BIND in a chroot
environment</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"
id="s3-bind-namedconf-state">11.2.1.1. Common Statement
Types</h4></div></div></div><div class="para">
+ The following types of statements are commonly used in <code
class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id646940" class="indexterm"></a>
+ <code class="option">acl</code>
</span></dt><dd><div class="para">
+ The <code class="option">acl</code> (Access Control List)
statement allows you to define groups of hosts, so that they can be permitted or denied
access to the nameserver. It takes the following form:
+ </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">Table 11.2, “Predefined
access control lists”</a>.
+ </div><div class="table"
id="table-bind-namedconf-common-acl"><h6>Table 11.2. Predefined access
control lists</h6><div class="table-contents"><table
summary="Predefined access control lists"
border="1"><colgroup><col width="25%"
class="keyword" /><col width="75%" class="description"
/></colgroup><thead><tr><th>
+ Keyword
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">any</code>
+ </td><td>
+ Matches every IP address.
+ </td></tr><tr><td>
+ <code class="option">localhost</code>
+ </td><td>
+ Matches any IP address that is in use by the local system.
+ </td></tr><tr><td>
+ <code class="option">localnets</code>
+ </td><td>
+ Matches any IP address on any network to which the local system is connected.
+ </td></tr><tr><td>
+ <code class="option">none</code>
+ </td><td>
+ Does not match any IP address.
+ </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">Example 11.1, “Using
acl in conjunction with options”</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>Example 11.1. Using acl in
conjunction with options</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="id646716"
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>Example 11.2. Including
a file to /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="id646654" 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">Table 11.3, “Commonly
used options”</a> below.
+ </div><div class="table"
id="table-bind-namedconf-common-options"><h6>Table 11.3. Commonly used
options</h6><div class="table-contents"><table
summary="Commonly used options" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow-query</code>
+ </td><td>
+ Specifies which hosts are allowed to query the nameserver for authoritative
resource records. It accepts an access control lists, a collection of IP addresses, or
networks in the CIDR notation. All hosts are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">allow-query-cache</code>
+ </td><td>
+ Specifies which hosts are allowed to query the nameserver for
non-authoritative data such as recursive queries. Only <code
class="literal">localhost</code> and <code
class="literal">localnets</code> are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">blackhole</code>
+ </td><td>
+ Specifies which hosts are <span
class="emphasis"><em>not</em></span> allowed to query the
nameserver. This option should be used when particular host or network floods the server
with requests. The default option is <code
class="literal">none</code>.
+ </td></tr><tr><td>
+ <code class="option">directory</code>
+ </td><td>
+ Specifies a working directory for the <code
class="systemitem">named</code> service. The default option is <code
class="literal">/var/named/</code>.
+ </td></tr><tr><td>
+ <code class="option">dnssec-enable</code>
+ </td><td>
+ Specifies whether to return DNSSEC related resource records. The default
option is <code class="literal">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">dnssec-validation</code>
+ </td><td>
+ Specifies whether to prove that resource records are authentic via DNSSEC. The
default option is <code class="option">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">forwarders</code>
+ </td><td>
+ Specifies a list of valid IP addresses for nameservers to which the requests
should be forwarded for resolution.
+ </td></tr><tr><td>
+ <code class="option">forward</code>
+ </td><td>
+ <div class="para">
+ Specifies the behavior of the <code
class="option">forwarders</code> directive. It accepts the following
options:
+ </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>
+ <code class="option">listen-on</code>
+ </td><td>
+ Specifies the IPv4 network interface on which to listen for queries. On a DNS
server that also acts as a gateway, you can use this option to answer queries originating
from a single network only. All IPv4 interfaces are used by default.
+ </td></tr><tr><td>
+ <code class="option">listen-on-v6</code>
+ </td><td>
+ Specifies the IPv6 network interface on which to listen for queries. On a DNS
server that also acts as a gateway, you can use this option to answer queries originating
from a single network only. All IPv6 interfaces are used by default.
+ </td></tr><tr><td>
+ <code class="option">max-cache-size</code>
+ </td><td>
+ Specifies the maximum amount of memory to be used for server caches. When the
limit is reached, the server causes records to expire prematurely so that the limit is not
exceeded. In a server with multiple views, the limit applies separately to the cache of
each view. The default option is <code class="literal">32M</code>.
+ </td></tr><tr><td>
+ <code class="option">notify</code>
+ </td><td>
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated.
It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will
notify all secondary nameservers.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">no</code> — The server will
<span class="emphasis"><em>not</em></span> notify any
secondary nameserver.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">master-only</code> — The server
will notify primary server for the zone only.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">explicit</code> — The server
will notify only the secondary servers that are specified in the <code
class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">pid-file</code>
+ </td><td>
+ Specifies the location of the process ID file created by the <code
class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="option">recursion</code>
+ </td><td>
+ Specifies whether to act as a recursive server. The default option is <code
class="literal">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">statistics-file</code>
+ </td><td>
+ Specifies an alternate location for statistics files. The <code
class="filename">/var/named/named.stats</code> file is used by
default.
+ </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">Section 11.2.7.1,
“Installed Documentation”</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>Example 11.3. Using the
options statement</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="id646159"
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">Table 11.4, “Commonly
used options”</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">Section 11.2.2, “Editing Zone Files”</a>.
+ </div><div class="table"
id="table-bind-namedconf-common-zone"><h6>Table 11.4. Commonly used
options</h6><div class="table-contents"><table
summary="Commonly used options" border="1"><colgroup><col
width="25%" class="option" /><col width="75%"
class="description" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow-query</code>
+ </td><td>
+ 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>
+ <code class="option">allow-transfer</code>
+ </td><td>
+ 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>
+ <code class="option">allow-update</code>
+ </td><td>
+ <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">Section 11.2.5.3,
“Transaction SIGnatures (TSIG)”</a>.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="option">file</code>
+ </td><td>
+ 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>
+ <code class="option">masters</code>
+ </td><td>
+ 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>
+ <code class="option">notify</code>
+ </td><td>
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated.
It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will
notify all secondary nameservers.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">no</code> — The server will
<span class="emphasis"><em>not</em></span> notify any
secondary nameserver.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">master-only</code> — The server
will notify primary server for the zone only.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="option">explicit</code> — The server
will notify only the secondary servers that are specified in the <code
class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">type</code>
+ </td><td>
+ <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">Example 11.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>Example 11.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">Example 11.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>Example 11.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"
id="s3-bind-namedconf-state-other">11.2.1.2. Other Statement
Types</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><dt
class="varlistentry"><span class="term"> <a
id="id645600" 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">
+ Refer to <a class="xref"
href="s2-bind-rndc.html">Section 11.2.3, “Using the rndc Utility”</a>
for more information on the <code class="command">rndc</code>
utility and its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id645546"
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>
— The type of algorithm to be used (for example, <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>
— The encrypted key.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref"
href="s2-bind-rndc.html">Section 11.2.3, “Using the rndc Utility”</a>
for more information on the <code class="command">rndc</code>
utility and its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id645460"
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">Section 11.2.7.1,
“Installed Documentation”</a>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id645356"
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="id645297"
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">Section 11.2.5.4, “DNS
Security Extensions (DNSSEC)”</a> for more information on this topic.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id645254"
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">Section 11.2.5.1,
“Multiple 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"
id="s3-bind-namedconf-comm">11.2.1.3. Comment
Tags</h4></div></div></div><a id="id645182"
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><dt
class="varlistentry"><span class="term"><code
class="literal">//</code></span></dt><dd><div
class="para">
+ Any text after the <code class="literal">//</code>
characters to the end of the line is considered a comment. For example:
+ </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">
+ Any text after the <code class="literal">#</code> character
to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting">notify yes; # notify all
secondary nameservers</pre></dd><dt
class="varlistentry"><span class="term"><code
class="literal">/*</code> and <code
class="literal">*/</code></span></dt><dd><div
class="para">
+ Any block of text enclosed in <code
class="literal">/*</code> and <code
class="literal">*/</code> is considered a comment. For example:
+ </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>Prev</strong>Chapter 11. DNS
Servers</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-zone.html"><strong>Next</strong>11.2.2. Editing
Zone Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-FTP.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-FTP.html
new file mode 100644
index 0000000..35d5409
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-FTP.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>15.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-File_and_Print_Servers.html" title="Chapter 15. File Servers"
/><link rel="prev" href="ch-File_and_Print_Servers.html"
title="Chapter 15. File Servers" /><link rel="next"
href="s2-ftp-servers.html" title="15.2.2. FTP Servers"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-File_and_Print_Servers.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey=
"n"
href="s2-ftp-servers.html"><strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="section" id="s1-FTP"
lang="en-US"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-FTP">15.2. FTP</h2></div></div></div><a
id="id506211" class="indexterm"></a><a
id="id422508" 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"
id="s2-ftp-protocol">15.2.1. The File Transfer
Protocol</h3></div></div></div><a id="id630333"
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"
id="s3-ftp-protocol-multiport">15.2.1.1. Multiple Ports, Multiple
Modes</h4></div></div></div><a id="id422180"
class="indexterm"></a><a id="id568273"
class="indexterm"></a><a id="id605691"
class="indexterm"></a><a id="id544173"
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">
+ The following defines these modes:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">active
mode</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">passive mode</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">Section 15.2.5.8,
“Network Options”</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>Prev</strong>Chapter 15. File
Servers</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-servers.html"><strong>Next</strong>15.2.2. FTP
Servers</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-autotasks-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-autotasks-additional-resources.html
new file mode 100644
index 0000000..3eaf3bf
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-autotasks-additional-resources.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>18.3. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Automating_System_Tasks.html" title="Chapter 18. Automating System
Tasks" /><link rel="prev"
href="s2-autotasks-at-batch-service.html" title="18.2.6. Starting and
Stopping the Service" /><link rel="next"
href="ch-abrt.html" title="Chapter 19. Automatic Bug-Reporting Tool
(ABRT)" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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"><s
trong>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="ch-abrt.html"><strong>Next</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"
id="s1-autotasks-additional-resources">18.3. Additional
Resources</h2></div></div></div><a id="id599251"
class="indexterm"></a><a id="id532118"
class="indexterm"></a><a id="id541576"
class="indexterm"></a><div class="para">
+ To learn more about configuring automated tasks, refer to the following resources.
+ </div><div class="section"
id="s2-autotasks-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-autotasks-installed-docs">18.3.1. Installed
Documentation</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>Prev</strong>18.2.6. Starting
and Stopping the Service</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-abrt.html"><strong>Next</strong>Chapter 19. Automatic
Bug-Reporting Tool (ABRT)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-autotasks-at-batch.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-autotasks-at-batch.html
new file mode 100644
index 0000000..726673a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-autotasks-at-batch.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2. At and 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Automating_System_Tasks.html" title="Chapter 18. Automating System
Tasks" /><link rel="prev"
href="ch-Automating_System_Tasks.html" title="Chapter 18. Automating System
Tasks" /><link rel="next"
href="s2-autotasks-batch-configuring.html" title="18.2.2. Configuring Batch
Jobs" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Automating_System_Tasks.html"><strong>
Prev</strong></a></li><li class="next"><a
accesskey="n"
href="s2-autotasks-batch-configuring.html"><strong>Next</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"
id="s1-autotasks-at-batch">18.2. At and
Batch</h2></div></div></div><a id="id626469"
class="indexterm"></a><a id="id573223"
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"
id="s2-autotasks-at-configuring">18.2.1. Configuring At
Jobs</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">
+ The argument <em
class="replaceable"><code>time</code></em> can be one of
the following:
+ </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 — Specifies 12:00 a.m.
+ </div></li><li class="listitem"><div
class="para">
+ noon — Specifies 12:00 p.m.
+ </div></li><li class="listitem"><div
class="para">
+ teatime — Specifies 4:00 p.m.
+ </div></li><li class="listitem"><div
class="para">
+ month-name day year format — For example, January 15 2002 specifies the 15th day of
January in the year 2002. The year is optional.
+ </div></li><li class="listitem"><div
class="para">
+ MMDDYY, MM/DD/YY, or MM.DD.YY formats — For example, 011502 for the 15th day of
January in the year 2002.
+ </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">Section 18.2.3, “Viewing Pending
Jobs”</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">Section 18.2.5,
“Controlling Access to At and Batch”</a> for details.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Automating_System_Tasks.html"><strong>Prev</strong>Chapter 18. Automating
System Tasks</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-batch-configuring.html"><strong>Next</strong>18.2.2. Configuring
Batch Jobs</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-check-rpm-sig.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-check-rpm-sig.html
new file mode 100644
index 0000000..2584667
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-check-rpm-sig.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.3. Checking a Package's Signature</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-RPM.html" title="Appendix A. RPM" /><link
rel="prev" href="s2-rpm-verifying.html"
title="A.2.7. Verifying" /><link rel="next"
href="s2-keys-checking.html" title="A.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-keys-checking.html"><
strong>Next</strong></a></li></ul><div
xml:lang="en-US" class="section" id="s1-check-rpm-sig"
lang="en-US"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-check-rpm-sig">A.3. Checking a Package's
Signature</h2></div></div></div><a id="id566216"
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="id593228" class="indexterm"></a><a
id="id552969" class="indexterm"></a><a
id="id552982" 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"
id="s2-keys-importing">A.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>Prev</strong>A.2.7. Verifying</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-keys-checking.html"><strong>Next</strong>A.3.2. Verifying
Signature of Packages</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-additional-resources.html
new file mode 100644
index 0000000..dfe6f72
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-additional-resources.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>10.6. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-DHCP_Servers.html" title="Chapter 10. DHCP Servers"
/><link rel="prev" href="s1-dhcp_for_ipv6_dhcpv6.html"
title="10.5. DHCP for IPv6 (DHCPv6)" /><link rel="next"
href="ch-DNS_Servers.html" title="Chapter 11. DNS Servers"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" hr
ef="ch-DNS_Servers.html"><strong>Next</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"
id="s1-dhcp-additional-resources">10.6. Additional
Resources</h2></div></div></div><a id="id506800"
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"
id="s2-dhcp-installed-docs">10.6.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">dhcpd</code> man page — Describes how
the DHCP daemon works.
+ </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> man page —
Describes a persistent database of leases.
+ </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> man page — Explains
the DHCP Relay Agent and its configuration options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/dhcp-<em
class="replaceable"><code>version</code></em>/</code>
— Contains sample files, README files, and release notes for current versions of the DHCP
service.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>Prev</strong>10.5. DHCP
for IPv6 (DHCPv6)</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-DNS_Servers.html"><strong>Next</strong>Chapter 11. DNS
Servers</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-configuring-client.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-configuring-client.html
new file mode 100644
index 0000000..44849a4
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-configuring-client.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>10.3. Configuring a DHCP Client</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-DHCP_Servers.html" title="Chapter 10. DHCP Servers"
/><link rel="prev" href="dhcp-relay-agent.html"
title="10.2.4. DHCP Relay Agent" /><link rel="next"
href="sect-Configuring_a_Multihomed_DHCP_Server.html"
title="10.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>Prev</strong></a></li><li
class
="next"><a accesskey="n"
href="sect-Configuring_a_Multihomed_DHCP_Server.html"><strong>Next</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"
id="s1-dhcp-configuring-client">10.3. Configuring a DHCP
Client</h2></div></div></div><a id="id463316"
class="indexterm"></a><a id="id463330"
class="indexterm"></a><div class="para">
+ To configure a DHCP client manually, modify the <code
class="filename">/etc/sysconfig/network</code> file to enable
networking and the configuration file for each network device in the <code
class="filename">/etc/sysconfig/network-scripts</code> directory. In
this directory, each device should have a configuration file named <code
class="filename">ifcfg-eth0</code>, where <code
class="filename">eth0</code> is the network device name.
+ </div><div class="para">
+ The <code
class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code> file
should contain the following lines:
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ A configuration file is needed for each device to be configured to use DHCP.
+ </div><div class="para">
+ Other options for the network script includes:
+ </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>,
where <code class="literal"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — Modify <code
class="filename">/etc/resolv.conf</code> with information from the
server. If using DHCP, then <code class="command">yes</code> is the
default.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — Do not modify <code
class="filename">/etc/resolv.conf</code>.
+ </div></li></ul></div></li></ul></div><div
class="note"><div
class="admonition_header"><h2>Advanced
configurations</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>Prev</strong>10.2.4. DHCP
Relay Agent</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Configuring_a_Multihomed_DHCP_Server.html"><strong>Next</strong>10.4. Configuring
a Multihomed DHCP Server</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-configuring-server.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-configuring-server.html
new file mode 100644
index 0000000..61634fe
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp-configuring-server.html
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Configuring a 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-DHCP_Servers.html" title="Chapter 10. DHCP Servers"
/><link rel="prev" href="ch-DHCP_Servers.html"
title="Chapter 10. DHCP Servers" /><link rel="next"
href="lease-database.html" title="10.2.2. Lease Database"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-DHCP_Servers.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="lease-database.ht
ml"><strong>Next</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"
id="s1-dhcp-configuring-server">10.2. Configuring a DHCP
Server</h2></div></div></div><a id="id536541"
class="indexterm"></a><div class="para">
+ The <code class="filename">dhcp</code> package contains an ISC
DHCP server. First, install the package as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">yum install dhcp</code></pre><div
class="para">
+ Installing the <code class="filename">dhcp</code> package
creates a file, <code class="filename">/etc/dhcp/dhcpd.conf</code>,
which is merely an empty configuration file:
+ </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">
+ The sample configuration file can be found at <code
class="filename">/usr/share/doc/dhcp-<em
class="replaceable"><code>version</code></em>/dhcpd.conf.sample</code>.
You should use this file to help you configure <code
class="filename">/etc/dhcp/dhcpd.conf</code>, which is explained in
detail below.
+ </div><div class="para">
+ DHCP also uses the file <code
class="filename">/var/lib/dhcpd/dhcpd.leases</code> to store the client
lease database. Refer to <a class="xref"
href="lease-database.html">Section 10.2.2, “Lease Database”</a> for
more information.
+ </div><div class="section" id="config-file"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="config-file">10.2.1. Configuration
File</h3></div></div></div><a id="id447643"
class="indexterm"></a><a id="id447657"
class="indexterm"></a><div class="para">
+ The first step in configuring a DHCP server is to create the configuration file that
stores the network information for the clients. Use this file to declare options and
global options for client systems.
+ </div><div class="para">
+ The configuration file can contain extra tabs or blank lines for easier formatting.
Keywords are case-insensitive and lines beginning with a hash sign (#) are considered
comments.
+ </div><div class="para">
+ There are two types of statements in the configuration file:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Parameters — State how to perform a task, whether to perform a task, or what
network configuration options to send to the client.
+ </div></li><li class="listitem"><div
class="para">
+ Declarations — Describe the topology of the network, describe the clients, provide
addresses for the clients, or apply a group of parameters to a group of declarations.
+ </div></li></ul></div><a id="id444426"
class="indexterm"></a><div class="para">
+ The parameters that start with the keyword option are referred to as <em
class="firstterm">options</em>. These options control DHCP options;
whereas, parameters configure values that are not optional or control how the DHCP server
behaves.
+ </div><a id="id507684"
class="indexterm"></a><div class="para">
+ Parameters (including options) declared before a section enclosed in curly brackets
({ }) are considered global parameters. Global parameters apply to all the sections below
it.
+ </div><div class="important"><div
class="admonition_header"><h2>Restart the DHCP daemon for the changes
to take effect</h2></div><div class="admonition"><div
class="para">
+ If the configuration file is changed, the changes do not take effect until the DHCP
daemon is restarted. To do so, type the following at a shell prompt as <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>Use the
omshell command</h2></div><div class="admonition"><div
class="para">
+ Instead of changing a DHCP configuration file and restarting the service each time,
using the <code class="command">omshell</code> command provides an
interactive way to connect to, query, and change the configuration of a DHCP server. By
using <code class="command">omshell</code>, all changes can be made
while the server is running. For more information on <code
class="command">omshell</code>, refer to the <code
class="command">omshell</code> man page.
+ </div></div></div><div class="para">
+ In <a class="xref"
href="s1-dhcp-configuring-server.html#subnet">Example 10.1, “Subnet
declaration”</a>, the <code class="filename">routers</code>,
<code class="filename">subnet-mask</code>, <code
class="filename">domain-search</code>, <code
class="filename">domain-name-servers</code>, and <code
class="filename">time-offset</code> options are used for any <code
class="filename">host</code> statements declared below it.
+ </div><a id="id624778"
class="indexterm"></a><div class="para">
+ Additionally, a <code class="filename">subnet</code> can be
declared, a <code class="filename">subnet</code> declaration must be
included for every subnet in the network. If it is not, the DHCP server fails to start.
+ </div><div class="para">
+ In this example, there are global options for every DHCP client in the subnet and a
<code class="filename">range</code> declared. Clients are assigned
an IP address within the <code class="filename">range</code>.
+ </div><div class="example"
id="subnet"><h6>Example 10.1. Subnet declaration</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">
+ To configure a DHCP server that leases a dynamic IP address to a system within a
subnet, modify <a class="xref"
href="s1-dhcp-configuring-server.html#dynamic-ip">Example 10.2, “Range
parameter”</a> with your values. It declares a default lease time, maximum lease
time, and network configuration values for the clients. This example assigns IP addresses
in the <code class="filename">range</code> 192.168.1.10 and
192.168.1.100 to client systems.
+ </div><div class="example"
id="dynamic-ip"><h6>Example 10.2. Range parameter</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">Example 10.3, “Static IP
address using DHCP”</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">
+ Note that the optional parameter <code
class="filename">host-name</code> can also be used to assign a host
name to the client.
+ </div><div class="example"
id="static-ip"><h6>Example 10.3. Static IP address using
DHCP</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="id509304" 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">Example 10.4,
“Shared-network declaration”</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>Example 10.4. Shared-network
declaration</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="id608111" class="indexterm"></a><div
class="para">
+ As demonstrated in <a class="xref"
href="s1-dhcp-configuring-server.html#group">Example 10.5, “Group
declaration”</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>Example 10.5. Group declaration</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>Using
the sample configuration file</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">
+ ... where <em
class="replaceable"><code>version-number</code></em> is the
DHCP version number.
+ </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>Prev</strong>Chapter 10. DHCP
Servers</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="lease-database.html"><strong>Next</strong>10.2.2. Lease
Database</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html
new file mode 100644
index 0000000..8f9fe5a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.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>10.5. DHCP for IPv6 (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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-DHCP_Servers.html" title="Chapter 10. DHCP Servers"
/><link rel="prev"
href="sect-Configuring_a_Multihomed_DHCP_Server.html"
title="10.4. Configuring a Multihomed DHCP Server" /><link
rel="next" href="s1-dhcp-additional-resources.html"
title="10.6. Additional Resources" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sect-Configuring_a_Multihomed_DHCP_Server.html">
<strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-dhcp-additional-resources.html"><strong>Next</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"
id="s1-dhcp_for_ipv6_dhcpv6">10.5. DHCP for IPv6
(DHCPv6)</h2></div></div></div><a id="id528562"
class="indexterm"></a><a id="id528574"
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">
+ The DHCPv6 server configuration file can be found at <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">
+ To start the DHCPv6 service, use the following command:
+ </div><pre class="screen"><code
class="command">systemctl start
dhcpd6.service</code></pre><div class="para">
+ A simple DHCPv6 server configuration file can look like this:
+ </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>Prev</strong>10.4. Configuring
a Multihomed DHCP Server</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-dhcp-additional-resources.html"><strong>Next</strong>10.6. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-additional-resources.html
new file mode 100644
index 0000000..81c4953
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-additional-resources.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>13.6. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Mail_Servers.html" title="Chapter 13. Mail Servers"
/><link rel="prev" href="s1-email-mua.html"
title="13.5. Mail User Agents" /><link rel="next"
href="s2-email-useful-websites.html" title="13.6.2. Useful Websites"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-mua.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-email-useful
-websites.html"><strong>Next</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"
id="s1-email-additional-resources">13.6. Additional
Resources</h2></div></div></div><a id="id437752"
class="indexterm"></a><a id="id530365"
class="indexterm"></a><a id="id530380"
class="indexterm"></a><a id="id433169"
class="indexterm"></a><div class="para">
+ The following is a list of additional documentation about email applications.
+ </div><div class="section"
id="s2-email-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-installed-docs">13.6.1. Installed
Documentation</h3></div></div></div><a id="id589772"
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">
+ When learning how Procmail works and creating new recipes, the following Procmail
man pages are invaluable:
+ </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> — Explains the
<code class="filename">rc</code> file format used to construct
recipes.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailex</code> — Gives a number
of useful, real-world examples of Procmail recipes.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">procmailsc</code> — Explains the
weighted scoring technique used by Procmail to match a particular recipe to a message.
+ </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>Prev</strong>13.5. Mail User
Agents</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-useful-websites.html"><strong>Next</strong>13.6.2. Useful
Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mda.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mda.html
new file mode 100644
index 0000000..542d185
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mda.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>13.4. Mail Delivery Agents</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Mail_Servers.html" title="Chapter 13. Mail Servers"
/><link rel="prev" href="s2-email-switchmail.html"
title="13.3.4. Mail Transport Agent (MTA) Configuration" /><link
rel="next" href="s2-email-procmail-recipes.html"
title="13.4.2. Procmail Recipes" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="ne
xt"><a accesskey="n"
href="s2-email-procmail-recipes.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-email-mda"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-email-mda">13.4. Mail Delivery
Agents</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="id533355"
class="indexterm"></a><a id="id535224"
class="indexterm"></a><div class="para">
+ Procmail delivers and filters email as it is placed in the mail spool file of the
localhost. It is powerful, gentle on system resources, and widely used. Procmail can play
a critical role in delivering email to be read by email client applications.
+ </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"
id="s2-email-procmail-configuration">13.4.1. Procmail
Configuration</h3></div></div></div><a id="id461057"
class="indexterm"></a><a id="id482239"
class="indexterm"></a><div class="para">
+ The Procmail configuration file contains important environmental variables. These
variables specify things such as which messages to sort and what to do with the messages
that do not match any recipes.
+ </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">
+ In this example, <code class="command"><em
class="replaceable"><code>env-variable</code></em>
</code> is the name of the variable and <code class="command"><em
class="replaceable"><code>value</code></em> </code>
defines the variable.
+ </div><div class="para">
+ There are many environment variables not used by most Procmail users and many of the
more important environment variables are already defined by a default value. Most of the
time, the following variables are used:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">DEFAULT</code> — Sets the default
mailbox where messages that do not match any recipes are placed.
+ </div><div class="para">
+ The default <code class="command">DEFAULT</code> value is the
same as <code class="command">$ORGMAIL</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">INCLUDERC</code> — Specifies additional
<code class="filename">rc</code> files containing more recipes for
messages to be checked against. This breaks up the Procmail recipe lists into individual
files that fulfill different roles, such as blocking spam and managing email lists, that
can then be turned off or on by using comment characters in the user's <code
class="filename">~/.procmailrc</code> file.
+ </div><div class="para">
+ For example, lines in a user's <code
class="filename">.procmailrc</code> file may look like this:
+ </div><pre class="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> — Sets the current
working directory for Procmail. If set, all other Procmail paths are relative to this
directory.
+ </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">
+ By default, a value of <code
class="command">/var/spool/mail/$LOGNAME</code> is used.
+ </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>Prev</strong>13.3.4. Mail
Transport Agent (MTA) Configuration</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-procmail-recipes.html"><strong>Next</strong>13.4.2. Procmail
Recipes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mta.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mta.html
new file mode 100644
index 0000000..e263113
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mta.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>13.3. Mail Transport Agents</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Mail_Servers.html" title="Chapter 13. Mail Servers"
/><link rel="prev" href="s2-email-types-mua.html"
title="13.2.3. Mail User Agent" /><link rel="next"
href="s2-email-mta-sendmail.html" title="13.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-email-mta
-sendmail.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-email-mta"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-email-mta">13.3. Mail Transport
Agents</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"
id="s2-email-mta-postfix">13.3.1. Postfix</h3></div></div></div><a
id="id446061" class="indexterm"></a><a
id="id446075" class="indexterm"></a><div
class="para">
+ Originally developed at IBM by security expert and programmer Wietse Venema, Postfix
is a Sendmail-compatible MTA that is designed to be secure, fast, and easy to configure.
+ </div><div class="para">
+ To improve security, Postfix uses a modular design, where small processes with
limited privileges are launched by a <em
class="firstterm">master</em> daemon. The smaller, less privileged
processes perform very specific tasks related to the various stages of mail delivery and
run in a change rooted environment to limit the effects of attacks.
+ </div><div class="para">
+ Configuring Postfix to accept network connections from hosts other than the local
computer takes only a few minor changes in its configuration file. Yet for those with more
complex needs, Postfix provides a variety of configuration options, as well as third party
add-ons that make it a very versatile and full-featured MTA.
+ </div><div class="para">
+ The configuration files for Postfix are human readable and support upward of 250
directives. Unlike Sendmail, no macro processing is required for changes to take effect
and the majority of the most commonly used options are described in the heavily commented
files.
+ </div><div class="section"
id="s3-email-mta-postfix-default"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-mta-postfix-default">13.3.1.1. The Default Postfix
Installation</h4></div></div></div><a id="id431588"
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> — Maps email
addresses to relay hosts.
+ </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">Section 13.3.1.2, “Basic
Postfix Configuration”</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"
id="s3-email-mta-postfix-conf">13.3.1.2. Basic Postfix
Configuration</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">
+ Edit the <code class="filename">/etc/postfix/main.cf</code>
file with a text editor, such as <code class="command">vi</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">
+ Uncomment the <code class="command">myorigin =
$mydomain</code> line.
+ </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">
+ Uncomment the <code class="command">mydestination = $myhostname,
localhost.$mydomain</code> line.
+ </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">
+ Uncomment the <code class="command">inet_interfaces =
all</code> line.
+ </div></li><li class="listitem"><div
class="para">
+ Comment the <code class="command">inet_interfaces =
localhost</code> line.
+ </div></li><li class="listitem"><div
class="para">
+ Restart the <code class="command">postfix</code> service.
+ </div></li></ul></div><div class="para">
+ Once these steps are complete, the host accepts outside emails for delivery.
+ </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"
id="using-postfix-with-ldap">13.3.1.3. Using Postfix with
LDAP</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"
id="aliases-example">13.3.1.3.1. The /etc/aliases lookup
example</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">
+ where <em
class="parameter"><code>ldap.example.com</code></em>,
<em class="parameter"><code>example</code></em>, and
<em class="parameter"><code>com</code></em> are
parameters that need to be replaced with specification of an existing available <code
class="systemitem">LDAP</code> server.
+ </div><div class="note"><div
class="admonition_header"><h2>The /etc/postfix/ldap-aliases.cf
file</h2></div><div class="admonition"><div
class="para">
+ The <code
class="filename">/etc/postfix/ldap-aliases.cf</code> file can specify
various parameters, including parameters that enable <code
class="systemitem">LDAP</code> <code
class="systemitem">SSL</code> and <code
class="systemitem">STARTTLS</code>. For more information, refer to the
<code class="command">ldap_table(5)</code> man page.
+ </div></div></div><div class="para">
+ For more information on <code class="systemitem">LDAP</code>,
refer to <a class="xref"
href="ch-Directory_Servers.html#s1-OpenLDAP">Section 14.1,
“OpenLDAP”</a>.
+ </div></div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-email-types-mua.html"><strong>Prev</strong>13.2.3. Mail
User Agent</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-mta-sendmail.html"><strong>Next</strong>13.3.2. Sendmail</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mua.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mua.html
new file mode 100644
index 0000000..71e9b3a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-mua.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.5. Mail User Agents</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Mail_Servers.html" title="Chapter 13. Mail Servers"
/><link rel="prev" href="s2-email-procmail-recipes.html"
title="13.4.2. Procmail Recipes" /><link rel="next"
href="s1-email-additional-resources.html" title="13.6. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-procmail-recipes.html"><strong>Prev</strong></a></li><li
class="next"><a
accesskey="n"
href="s1-email-additional-resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-email-mua"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-email-mua">13.5. Mail User
Agents</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"
id="s2-email-security">13.5.1. Securing
Communication</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="id540036"
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"
id="s3-email-security-clients">13.5.1.1. Secure Email
Clients</h4></div></div></div><a id="id625740"
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"
id="s3-email-security-servers">13.5.1.2. Securing Email Client
Communications</h4></div></div></div><a id="id553170"
class="indexterm"></a><a id="id553188"
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>Avoid using self-signed
certificates</h2></div><div class="admonition"><div
class="para">
+ Self-signed certificates should be used for testing purposes only. Any server used
in a production environment should use an SSL certificate granted by a CA.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate for <code
class="systemitem">IMAP</code> or <code
class="systemitem">POP</code>, change to the <code
class="filename">/etc/pki/dovecot/</code> directory, edit the
certificate parameters in the <code
class="filename">/etc/pki/dovecot/dovecot-openssl.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">
+ Once finished, make sure you have the following configurations in your <code
class="filename">/etc/dovecot/conf.d/10-ssl.conf</code> file:
+ </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>Installing the stunnel
package</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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate, change to the <code
class="filename">/etc/pki/tls/certs/</code> directory, and type the
following command:
+ </div><pre class="screen">certs]# <code
class="command">make stunnel.pem</code></pre><div
class="para">
+ Answer all of the questions to complete the process.
+ </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>Prev</strong>13.4.2. Procmail
Recipes</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-additional-resources.html"><strong>Next</strong>13.6. Additional
Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-types.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-types.html
new file mode 100644
index 0000000..09e6a5a
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-email-types.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>13.2. Email Program Classifications</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Mail_Servers.html" title="Chapter 13. Mail Servers"
/><link rel="prev" href="ch-Mail_Servers.html"
title="Chapter 13. Mail Servers" /><link rel="next"
href="s2-email-types-mda.html" title="13.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-email
-types-mda.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-email-types"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-email-types">13.2. Email Program
Classifications</h2></div></div></div><a
id="id626421" class="indexterm"></a><div
class="para">
+ In general, all email applications fall into at least one of three classifications.
Each classification plays a specific role in the process of moving and managing email
messages. While most users are only aware of the specific email program they use to
receive and send messages, each one is important for ensuring that email arrives at the
correct destination.
+ </div><div class="section"
id="s2-email-types-mta"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-types-mta">13.2.1. Mail Transport
Agent</h3></div></div></div><a id="id532964"
class="indexterm"></a><a id="id569711"
class="indexterm"></a><a id="id569726"
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">
+ While the delivery of messages between machines may seem rather straightforward, the
entire process of deciding if a particular MTA can or should accept a message for delivery
is quite complicated. In addition, due to problems from spam, use of a particular MTA is
usually restricted by the MTA's configuration or the access configuration for the
network on which the MTA resides.
+ </div><div class="para">
+ Many modern email client programs can act as an MTA when sending email. However, this
action should not be confused with the role of a true MTA. The sole reason email client
programs are capable of sending email like an MTA is because the host running the
application does not have its own MTA. This is particularly true for email client programs
on non-UNIX-based operating systems. However, these client programs only send outbound
messages to an MTA they are authorized to use and do not directly deliver the message to
the intended recipient's email server.
+ </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">Section 13.3, “Mail Transport
Agents”</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Mail_Servers.html"><strong>Prev</strong>Chapter 13. Mail
Servers</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-types-mda.html"><strong>Next</strong>13.2.2. Mail
Delivery Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kdump-crash.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kdump-crash.html
new file mode 100644
index 0000000..f9e60a4
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kdump-crash.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>22.2. 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-kdump.html" title="Chapter 22. The kdump Crash Recovery
Service" /><link rel="prev" href="ch-kdump.html"
title="Chapter 22. The kdump Crash Recovery Service" /><link
rel="next" href="s2-kdump-crash-log.html"
title="22.2.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="ch-kdump.html"><strong>Prev</strong></a></li><li
class="next"><a
accesskey="n"
href="s2-kdump-crash-log.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-kdump-crash"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kdump-crash">22.2. Analyzing the Core
Dump</h2></div></div></div><a id="id571551"
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="id575799"
class="indexterm"></a><div class="note"><div
class="admonition_header"><h2>Make sure you have relevant packages
installed</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">Section 4.2.4, “Installing
Packages”</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"
id="s2-kdump-crash-running">22.2.1. Running the crash
Utility</h3></div></div></div><a id="id627314"
class="indexterm"></a><div class="para">
+ To start the utility, type the command in the following form at a shell prompt:
+ </div><pre class="screen"><code
class="command">crash /var/crash/<em
class="replaceable"><code>timestamp</code></em>/vmcore
/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>Example 22.3. 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="ch-kdump.html"><strong>Prev</strong>Chapter 22. The kdump
Crash Recovery Service</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kdump-crash-log.html"><strong>Next</strong>22.2.2. Displaying
the Message Buffer</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kdump-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kdump-resources.html
new file mode 100644
index 0000000..04eefaf
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kdump-resources.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>22.3. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-kdump.html" title="Chapter 22. The kdump Crash Recovery
Service" /><link rel="prev" href="s2-kdump-crash-exit.html"
title="22.2.7. Exiting the Utility" /><link rel="next"
href="s2-kdump-resources-online.html" title="22.3.2. Useful Websites"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-kdump-crash-exit.html"><strong>Prev</strong></a></li><li
class="next"><a ac
cesskey="n"
href="s2-kdump-resources-online.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-kdump-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kdump-resources">22.3. Additional
Resources</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"
id="s2-kdump-resources-installed">22.3.1. Installed
Documentation</h3></div></div></div><a id="id480347"
class="indexterm"></a><a id="id607428"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><code
class="command">man
kdump.conf</code></span></dt><dd><div
class="para">
+ The manual page for the <code
class="filename">/etc/kdump.conf</code> configuration file containing
the full documentation of available options.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
makedumpfile</code></span></dt><dd><div
class="para">
+ The manual page for the <code
class="command">makedumpfile</code> core collector containing the full
documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
kexec</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">kexec</code>
containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
crash</code></span></dt><dd><div class="para">
+ The manual page for the <span
class="application"><strong>crash</strong></span> utility
containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code
class="filename">/usr/share/doc/kexec-tools-<em
class="replaceable"><code>version</code></em>/kexec-kdump-howto.txt</code></span></dt><dd><div
class="para">
+ An overview of the <code class="systemitem">kdump</code> and
<code class="command">kexec</code> installation and usage.
+ </div></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-kdump-crash-exit.html"><strong>Prev</strong>22.2.7. Exiting
the Utility</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kdump-resources-online.html"><strong>Next</strong>22.3.2. Useful
Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-boot-loader.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-boot-loader.html
new file mode 100644
index 0000000..4a628e2
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-boot-loader.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>20.6. Verifying the 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 20. Manually
Upgrading the Kernel" /><link rel="prev"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="20.5. Verifying
the Initial RAM Disk Image" /><link rel="next"
href="s2-kernel-boot-loader-iseries.html" title="20.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="previous"><a accesskey="p" href
="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-boot-loader-iseries.html"><strong>Next</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"
id="s1-kernel-boot-loader">20.6. Verifying the Boot
Loader</h2></div></div></div><a id="id567048"
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>Table 20.1. Boot loaders by
architecture</h6><div class="table-contents"><table
summary="Boot loaders by architecture"
border="1"><colgroup><col class="architecture"
width="33%" /><col class="bootloader" width="33%"
/><col class="refer-to" width="33%"
/></colgroup><thead><tr><th>
+ Architecture
+ </th><th>
+ Boot Loader
+ </th><th>
+ Refer to
+ </th></tr></thead><tbody><tr><td>
+ x86
+ </td><td>
+ GRUB
+ </td><td>
+ <a class="xref"
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Section 20.6.1,
“Configuring the GRUB Boot Loader”</a>
+ </td></tr><tr><td>
+ AMD AMD64 <span
class="emphasis"><em>or</em></span> Intel 64
+ </td><td>
+ GRUB
+ </td><td>
+ <a class="xref"
href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Section 20.6.1,
“Configuring the GRUB Boot Loader”</a>
+ </td></tr><tr><td>
+ IBM eServer System i
+ </td><td>
+ OS/400
+ </td><td>
+ <a class="xref"
href="s2-kernel-boot-loader-iseries.html">Section 20.6.2, “Configuring the
OS/400 Boot Loader”</a>
+ </td></tr><tr><td>
+ IBM eServer System p
+ </td><td>
+ YABOOT
+ </td><td>
+ <a class="xref"
href="s2-kernel-boot-loader-pseries.html">Section 20.6.3, “Configuring the
YABOOT Boot Loader”</a>
+ </td></tr><tr><td>
+ IBM System z
+ </td><td>
+ z/IPL
+ </td><td>
+ </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"
id="s3-kernel-boot-loader-grub">20.6.1. Configuring the GRUB Boot
Loader</h3></div></div></div><a id="id557788"
class="indexterm"></a><a id="id552574"
class="indexterm"></a><div class="para">
+ GRUB's configuration file, <code
class="filename">/boot/grub/grub.conf</code>, contains a few lines with
directives, such as <code class="computeroutput">default</code>,
<code class="computeroutput">timeout</code>, <code
class="computeroutput">splashimage</code> and <code
class="computeroutput">hiddenmenu</code> (the last directive has no
argument). The remainder of the file contains 4-line <em
class="firstterm">stanzas</em> that each refer to an installed kernel.
These stanzas always start with a <code
class="computeroutput">title</code> entry, after which the associated
<code class="computeroutput">root</code>, <code
class="computeroutput">kernel</code> and <code
class="computeroutput">initrd</code> directives should always be
indented. Ensure that each stanza starts with a <code
class="computeroutput">title</code> that contains a version number (in
parentheses) that matches the version number in the <code
class="computeroutput">kernel /vmlinuz-<em
class="replaceable">
<code>version_number</code></em></code> line of the same stanza.
+ </div><div class="example"
id="ex-_boot_grub_grub.conf"><h6>Example 20.1. /boot/grub/grub.conf</h6><div
class="example-contents"><pre class="programlisting">#
grub.conf generated by anaconda
+<em class="lineannotation"><span
class="lineannotation">[comments omitted]</span></em>
+default=1
+timeout=0
+splashimage=(hd0,0)/boot/grub/splash.xpm.gz
+hiddenmenu
+
+title Fedora (2.6.38.6-27.fc15.x86_64)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.38.6-27.fc15.x86_64 ro
root=UUID=e8148266-4a56-4f4d-b6df-9eafea4586b2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM
LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
+ initrd /boot/initramfs-2.6.38.6-27.fc15.x86_64.img
+title Fedora (2.6.38.6-26.rc1.fc15.x86_64)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.38.6-26.fc15.x86_64 ro
root=UUID=e8148266-4a56-4f4d-b6df-9eafea4586b2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM
LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
+ initrd
/boot/initramfs-2.6.38.6-26.fc15.x86_64.img</pre></div></div><br
class="example-break" /><div class="para">
+ 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>. This is the case in <a
class="xref"
href="s1-kernel-boot-loader.html#ex-_boot_grub_grub.conf">Example 20.1,
“/boot/grub/grub.conf”</a>, therefore the <code
class="computeroutput">initrd <code
class="filename">/initramfs-2.6.38.6-27.fc15.x86_64.img</code></code>
line in the first kernel stanza means that the <code
class="systemitem">initramfs</code> image is actually located at
<code
class="filename">/boot/initramfs-2.6.38.6-27.fc15.x86_64.img</code>
when the root file system is mounted, and likewise for the kernel path (for example:
<code class="computeroutput">kernel <code
class="filename">/vmlinuz-2.6.38.6-27.fc15.x86_64</code></code>)
in each stanza of <code class="filename">grub.conf</code>.
+ </div><div class="note"
id="note-The_initrd_directive_in_grub.conf_refers_to_an_initramfs_image"><div
class="admonition_header"><h2>The initrd directive in grub.conf refers
to an initramfs image</h2></div><div
class="admonition"><div class="para">
+ In kernel boot stanzas in <code
class="filename">grub.conf</code>, 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 <span
class="emphasis"><em><code
class="filename">initramfs</code> </em></span> file
corresponding to the same kernel version. This directive is called <code
class="computeroutput">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. Thus the <code
class="filename">grub.conf</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_ver
sion</code></em>.img</code>
+ </div><div class="para">
+ <span
class="application"><strong>Dracut</strong></span> is a new
utility available in Fedora 15, and much-improved over <code
class="command">mkinitrd</code>. 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">Section 20.5, “Verifying
the Initial RAM Disk Image”</a>.
+ </div></div></div><div class="para">
+ You should ensure that the kernel version number as given on the <code
class="computeroutput">kernel <code
class="filename">/vmlinuz-<em
class="replaceable"><code>kernel_version</code></em></code></code>
line matches the version number of the <code
class="systemitem">initramfs</code> image given on the <code
class="computeroutput">initrd <code
class="filename">/initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code></code>
line of each stanza. Refer to <a class="xref"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html#procedure-Verifying_the_Initial_RAM_Disk_Image">Procedure 20.1,
“Verifying the Initial RAM Disk Image”</a> for more information.
+ </div><div class="para">
+ The <code class="computeroutput">default=</code> directive
tells GRUB which kernel to boot <span class="emphasis"><em>by
default</em></span>. Each <code
class="computeroutput">title</code> in <code
class="filename">grub.conf</code> represents a bootable kernel. GRUB
counts the <code class="computeroutput">title</code>d stanzas
representing bootable kernels starting with <code
class="constant">0</code>. In <a class="xref"
href="s1-kernel-boot-loader.html#ex-_boot_grub_grub.conf">Example 20.1,
“/boot/grub/grub.conf”</a>, the line <code
class="computeroutput">default=1</code> indicates that GRUB will boot,
by default, the <span
class="emphasis"><em>second</em></span> kernel entry, i.e.
<code class="computeroutput">title Fedora
(2.6.38.6-26.fc15.x86_64)</code>.
+ </div><div class="para">
+ In <a class="xref"
href="s1-kernel-boot-loader.html#ex-_boot_grub_grub.conf">Example 20.1,
“/boot/grub/grub.conf”</a> GRUB is therefore configured to boot an older kernel,
when we compare by version numbers. In order to boot the newer kernel, which is the
<span class="emphasis"><em>first</em></span> <code
class="computeroutput">title</code> entry in <code
class="filename">grub.conf</code>, we would need to change the <code
class="computeroutput">default</code> value to <code
class="constant">0</code>.
+ </div><div class="para">
+ After installing a new kernel with <code
class="command">rpm</code>, verify that <code
class="filename">/boot/grub/grub.conf</code> is correct, change the
<code class="computeroutput">default=</code> value to the new kernel
(while remembering to count from <code class="constant">0</code>),
and reboot the computer into the new kernel. Ensure your hardware is detected by watching
the boot process output.
+ </div><div class="para">
+ If GRUB presents an error and is unable to boot into the default kernel, it is often
easiest to try to boot into an alternative or older kernel so that you can fix the
problem.
+ </div><div class="important"><div
class="admonition_header"><h2>Causing the GRUB boot menu to
display</h2></div><div class="admonition"><div
class="para">
+ If you set the <code class="computeroutput">timeout</code>
directive in <code class="filename">grub.conf</code> to <code
class="constant">0</code>, GRUB 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 will present you with the GRUB menu.
+ </div></div></div><div class="para">
+ Alternatively, use the boot media you created earlier to boot the system.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Prev</strong>20.5. Verifying
the Initial RAM Disk Image</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-boot-loader-iseries.html"><strong>Next</strong>20.6.2. Configuring
the OS/400 Boot Loader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-download.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-download.html
new file mode 100644
index 0000000..2ac26ce
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-download.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>20.3. Downloading the Upgraded Kernel</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 20. Manually
Upgrading the Kernel" /><link rel="prev"
href="s1-kernel-preparing.html" title="20.2. Preparing to Upgrade"
/><link rel="next" href="s1-kernel-perform-upgrade.html"
title="20.4. Performing the Upgrade" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-preparing.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n"
href="s1-kernel-perform-upgrade.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-kernel-download"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kernel-download">20.3. Downloading the Upgraded
Kernel</h2></div></div></div><a id="id469553"
class="indexterm"></a><a id="id469567"
class="indexterm"></a><a id="id428367"
class="indexterm"></a><a id="id463512"
class="indexterm"></a><div class="para">
+ There are several ways to determine if an updated kernel is available for the system.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Security Advisories — Refer to <a
href="http://fedoraproject.org/wiki/FSA">http://fedoraprojec...
for information on Security Advisories, including kernel upgrades that fix security
issues.
+ </div></li><li class="listitem"><div
class="para">
+ Via Fedora Update System — Download and install the kernel RPM packages. For more
information, refer to <a
href="http://admin.fedoraproject.org/updates/">http://admin....;.
+ </div></li></ul></div><div class="para">
+ To install the kernel manually, continue to <a class="xref"
href="s1-kernel-perform-upgrade.html">Section 20.4, “Performing the
Upgrade”</a>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-preparing.html"><strong>Prev</strong>20.2. Preparing
to Upgrade</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-perform-upgrade.html"><strong>Next</strong>20.4. Performing
the Upgrade</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-modules-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-modules-additional-resources.html
new file mode 100644
index 0000000..ee929f6
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-modules-additional-resources.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>21.8. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. Working with
Kernel Modules" /><link rel="prev"
href="sec-Using_Channel_Bonding.html" title="21.7.2. Using Channel
Bonding" /><link rel="next"
href="s2-kernel-modules-additional-resources-websites.html"
title="21.8.2. Useful Websites" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Using_Channel_Bonding.html"
<strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-modules-additional-resources-websites.html"><strong>Next</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"
id="s1-kernel-modules-additional-resources">21.8. Additional
Resources</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"
id="s2-kernel-modules-additional-resources-installed">21.8.1. Installed
Documentation</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><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><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>Prev</strong>21.7.2. Using
Channel Bonding</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-modules-additional-resources-websites.html"><strong>Next</strong>21.8.2. Useful
Websites</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-perform-upgrade.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-perform-upgrade.html
new file mode 100644
index 0000000..6cc52cb
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-perform-upgrade.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>20.4. Performing the Upgrade</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 20. Manually
Upgrading the Kernel" /><link rel="prev"
href="s1-kernel-download.html" title="20.3. Downloading the Upgraded
Kernel" /><link rel="next"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="20.5. Verifying
the Initial RAM Disk Image" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-down
load.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Next</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"
id="s1-kernel-perform-upgrade">20.4. Performing the
Upgrade</h2></div></div></div><a id="id422717"
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">Section 20.5, “Verifying
the Initial RAM Disk Image”</a> for details.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-download.html"><strong>Prev</strong>20.3. Downloading
the Upgraded Kernel</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Next</strong>20.5. Verifying
the Initial RAM Disk Image</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-preparing.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-preparing.html
new file mode 100644
index 0000000..8002511
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-kernel-preparing.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>20.2. Preparing to Upgrade</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 20. Manually
Upgrading the Kernel" /><link rel="prev"
href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 20. Manually
Upgrading the Kernel" /><link rel="next"
href="s1-kernel-download.html" title="20.3. Downloading the Upgraded
Kernel" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-download.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-kernel-preparing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-kernel-preparing">20.2. Preparing to
Upgrade</h2></div></div></div><a id="id561074"
class="indexterm"></a><a id="id561083"
class="indexterm"></a><a id="id604191"
class="indexterm"></a><a id="id592311"
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 2.6.38.6-27.fc15 installed
+kernel-doc.noarch 2.6.38.6-27.fc15 installed
+kernel-headers.x86_64 2.6.38.6-27.fc15 installed</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">Section 20.1,
“Overview of 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>Prev</strong>Chapter 20. Manually
Upgrading the Kernel</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-download.html"><strong>Next</strong>20.3. Downloading
the Upgraded Kernel</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-log-files-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-log-files-additional-resources.html
new file mode 100644
index 0000000..83b1683
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-log-files-additional-resources.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>17.6. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing
and Managing Log Files" /><link rel="prev"
href="s1-logfiles-examining.html" title="17.5. Monitoring Log Files"
/><link rel="next" href="s2-log-files-useful-websites.html"
title="17.6.2. Useful Websites" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-logfiles-examining.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n"
href="s2-log-files-useful-websites.html"><strong>Next</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"
id="s1-log-files-additional-resources">17.6. Additional
Resources</h2></div></div></div><div
class="para">
+ To learn more about <span
class="application"><strong>rsyslog</strong></span>,
<span
class="application"><strong>logrotate</strong></span>, and
log files in general, refer to the following resources.
+ </div><div class="section"
id="s2-log-files-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-log-files-installed-docs">17.6.1. Installed
Documentation</h3></div></div></div><a id="id555128"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">rsyslogd</code> manual page — Type
<code class="command">man rsyslogd</code> to learn more about
<code class="command">rsyslogd</code> and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">rsyslog.conf</code> manual page — Type
<code class="command">man rsyslog.conf</code> to learn more about
the <code class="command">/etc/rsyslog.conf</code> configuration
file and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">/usr/share/doc/rsyslog-<em
class="replaceable"><code><version-number></code></em>/
</code> — After installing the <span
class="package">rsyslog</span> package, this directory contains
extensive documentation in the <code class="systemitem">html</code>
format.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">logrotate</code> manual page — Type
<code class="command">man logrotate</code> to learn more about
<code class="command">logrotate</code> and its many options.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-logfiles-examining.html"><strong>Prev</strong>17.5. Monitoring
Log Files</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-log-files-useful-websites.html"><strong>Next</strong>17.6.2. Useful
Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-adding.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-adding.html
new file mode 100644
index 0000000..7a5b635
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-adding.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. Adding a Log 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing
and Managing Log Files" /><link rel="prev"
href="s1-logfiles-viewing.html" title="17.3. Viewing Log Files"
/><link rel="next" href="s1-logfiles-examining.html"
title="17.5. Monitoring Log 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="s1-logfiles-viewing.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-logfiles-examining.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-logfiles-adding"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-logfiles-adding">17.4. Adding a Log
File</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">Figure 17.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>Figure 17.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>Reading zipped log
files</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>Prev</strong>17.3. Viewing
Log Files</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-logfiles-examining.html"><strong>Next</strong>17.5. Monitoring
Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-examining.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-examining.html
new file mode 100644
index 0000000..d5be9dc
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-examining.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Monitoring Log 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing
and Managing Log Files" /><link rel="prev"
href="s1-logfiles-adding.html" title="17.4. Adding a Log File"
/><link rel="next" href="s1-log-files-additional-resources.html"
title="17.6. Additional Resources" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-logfiles-adding.html"><strong>Prev</strong></a
</li><li class="next"><a
accesskey="n"
href="s1-log-files-additional-resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-logfiles-examining"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-logfiles-examining">17.5. Monitoring Log
Files</h2></div></div></div><a id="id568051"
class="indexterm"></a><a id="id568066"
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">Figure 17.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>Figure 17.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>Prev</strong>17.4. Adding
a Log File</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-log-files-additional-resources.html"><strong>Next</strong>17.6. Additional
Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-locating.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-locating.html
new file mode 100644
index 0000000..fbff945
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-locating.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>17.2. Locating Log 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing
and Managing Log Files" /><link rel="prev"
href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing
and Managing Log Files" /><link rel="next"
href="s1-logfiles-viewing.html" title="17.3. Viewing Log 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="ch-Viewing_and_Managing_Log_Fil
es.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-logfiles-viewing.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-logfiles-locating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-logfiles-locating">17.2. Locating Log
Files</h2></div></div></div><a id="id635206"
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="id629541"
class="indexterm"></a><a id="id610557"
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"
id="configuring-logrotate">17.2.1. Configuring
logrotate</h3></div></div></div><div
class="para">
+ The following is a sample <code
class="filename">/etc/logrotate.conf</code> configuration file:
+ </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>
— Enables compression of rotated log files. Similar directives include:
+ <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> — Specifies
the command to be used for compressing.
+ </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> — Specifies
what extension is to be used for compressing.
+ </div></li><li class="listitem"><div
class="para">
+ <em
class="parameter"><code>compressoptions</code></em> — Lets
you specify any options that may be passed to the used compression program.
+ </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>Prev</strong>Chapter 17. Viewing
and Managing Log Files</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-logfiles-viewing.html"><strong>Next</strong>17.3. Viewing
Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-viewing.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-viewing.html
new file mode 100644
index 0000000..e425bc0
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-logfiles-viewing.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>17.3. Viewing Log 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing
and Managing Log Files" /><link rel="prev"
href="s1-logfiles-locating.html" title="17.2. Locating Log Files"
/><link rel="next" href="s1-logfiles-adding.html"
title="17.4. Adding a Log 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-logfiles-locating.html"><strong>Prev</strong></a></li><li
cla
ss="next"><a accesskey="n"
href="s1-logfiles-adding.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-logfiles-viewing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-logfiles-viewing">17.3. Viewing Log
Files</h2></div></div></div><a id="id629245"
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="id569299"
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>Installing the gnome-system-log
package</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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</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">Figure 17.1, “ Log File
Viewer ”</a>.
+ </div><a id="id607834"
class="indexterm"></a><a id="id624112"
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="Log File Viewer" /><div
class="longdesc"><div class="para">
+ Log File Viewer
+ </div></div></div></div><h6>Figure 17.1. Log File
Viewer </h6></div><br class="figure-break" /><a
id="id474842" 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="Log File Viewer —
filters" /><div class="longdesc"><div
class="para">
+ Log File Viewer — filters
+ </div></div></div></div><h6>Figure 17.2. Log File
Viewer — filters </h6></div><br class="figure-break" /><div
class="para">
+ Adding or editing a filter lets you define its parameters as is shown in <a
class="xref"
href="s1-logfiles-viewing.html#fig-redhat-filter-sample">Figure 17.3, “ Log
File Viewer — defining a filter ”</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="Log File Viewer —
defining a filter" /><div class="longdesc"><div
class="para">
+ Log File Viewer — defining a filter
+ </div></div></div></div><h6>Figure 17.3. Log File
Viewer — defining a filter </h6></div><br class="figure-break"
/><div class="para">
+ When defining a filter, you can edit the following parameters:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <span
class="guilabel"><strong>Name</strong></span> — Specifies
the name of the filter.
+ </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>Effect</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>Figure 17.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>Prev</strong>17.2. Locating
Log Files</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-logfiles-adding.html"><strong>Next</strong>17.4. Adding
a Log File</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-control.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-control.html
new file mode 100644
index 0000000..4f908bd
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-control.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>6.3. Interface Control Scripts</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Network_Interfaces.html" title="Chapter 6. Network
Interfaces" /><link rel="prev"
href="s2-networkscripts-interfaces-other.html" title="6.2.5. Other
Interfaces" /><link rel="next"
href="s1-networkscripts-static-routes.html" title="6.4. Configuring Static
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="s2-networkscripts-interfaces-other.html"><strong>Prev</s
trong></a></li><li class="next"><a
accesskey="n"
href="s1-networkscripts-static-routes.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-networkscripts-control"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-control">6.3. Interface Control
Scripts</h2></div></div></div><a id="id617542"
class="indexterm"></a><a id="id617564"
class="indexterm"></a><a id="id617586"
class="indexterm"></a><a id="id617599"
class="indexterm"></a><div class="para">
+ The interface control scripts activate and deactivate system interfaces. There are two
primary interface control scripts that call on control scripts located in the <code
class="filename">/etc/sysconfig/network-scripts/</code> directory:
<code class="command">/sbin/ifdown</code> and <code
class="command">/sbin/ifup</code>.
+ </div><div class="para">
+ The <code class="filename">ifup</code> and <code
class="filename">ifdown</code> interface scripts are symbolic links to
scripts in the <code class="filename">/sbin/</code> directory. When
either of these scripts are called, they require the value of the interface to be
specified, such as:
+ </div><pre class="screen"><code
class="command">ifup eth0</code></pre><div
class="warning"><div class="admonition_header"><h2>Use
the ifup and ifdown interface scripts</h2></div><div
class="admonition"><div class="para">
+ The <code class="filename">ifup</code> and <code
class="filename">ifdown</code> interface scripts are the only scripts
that the user should use to bring up and take down network interfaces.
+ </div><div class="para">
+ The following scripts are described for reference purposes only.
+ </div></div></div><div class="para">
+ Two files used to perform a variety of network initialization tasks during the process
of bringing up a network interface are <code
class="filename">/etc/rc.d/init.d/functions</code> and <code
class="filename">/etc/sysconfig/network-scripts/network-functions</code>.
Refer to <a class="xref"
href="s1-networkscripts-functions.html">Section 6.5, “Network Function
Files”</a> for more information.
+ </div><div class="para">
+ After verifying that an interface has been specified and that the user executing the
request is allowed to control the interface, the correct script brings the interface up or
down. The following are common interface control scripts found within the <code
class="filename">/etc/sysconfig/network-scripts/</code> directory:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="filename">ifup-aliases</code>
</span></dt><dd><div class="para">
+ Configures IP aliases from interface configuration files when more than one IP
address is associated with an interface.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-ippp</code>
and <code class="filename">ifdown-ippp</code>
</span></dt><dd><div class="para">
+ Brings ISDN interfaces up and down.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-ipv6</code>
and <code class="filename">ifdown-ipv6</code>
</span></dt><dd><div class="para">
+ Brings IPv6 interfaces up and down.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-plip</code>
</span></dt><dd><div class="para">
+ Brings up a PLIP interface.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-plusb</code>
</span></dt><dd><div class="para">
+ Brings up a USB interface for network connections.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-post</code>
and <code class="filename">ifdown-post</code>
</span></dt><dd><div class="para">
+ Contains commands to be executed after an interface is brought up or down.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-ppp</code>
and <code class="filename">ifdown-ppp</code>
</span></dt><dd><div class="para">
+ Brings a PPP interface up or down.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifup-routes</code>
</span></dt><dd><div class="para">
+ Adds static routes for a device as its interface is brought up.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="filename">ifdown-sit</code>
and <code class="filename">ifup-sit</code>
</span></dt><dd><div class="para">
+ Contains function calls related to bringing up and down an IPv6 tunnel within an
IPv4 connection.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code
class="filename">ifup-wireless</code>
</span></dt><dd><div class="para">
+ Brings up a wireless interface.
+ </div></dd></dl></div><div
class="warning"><div class="admonition_header"><h2>Be
careful when removing or modifying network scripts!</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 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">
+ Here, <em
class="replaceable"><code>action</code></em> can be either
<code class="command">start</code>, <code
class="command">stop</code>, or <code
class="command">restart</code>.
+ </div><div class="para">
+ To view a list of configured devices and currently active network interfaces, use the
following command:
+ </div><pre class="screen"><code
class="command">service network
status</code></pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-networkscripts-interfaces-other.html"><strong>Prev</strong>6.2.5. Other
Interfaces</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-networkscripts-static-routes.html"><strong>Next</strong>6.4. Configuring
Static Routes</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-functions.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-functions.html
new file mode 100644
index 0000000..fde04a3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-functions.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>6.5. Network Function 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Network_Interfaces.html" title="Chapter 6. Network
Interfaces" /><link rel="prev"
href="s1-networkscripts-static-routes.html" title="6.4. Configuring Static
Routes" /><link rel="next"
href="s1-networkscripts-resources.html" title="6.6. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-networkscripts-static-routes.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n"
href="s1-networkscripts-resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-networkscripts-functions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-functions">6.5. Network Function
Files</h2></div></div></div><a id="id618347"
class="indexterm"></a><div class="para">
+ Fedora makes use of several files that contain important common functions used to
bring interfaces up and down. Rather than forcing each interface control file to contain
these functions, they are grouped together in a few files that are called upon when
necessary.
+ </div><div class="para">
+ The <code
class="filename">/etc/sysconfig/network-scripts/network-functions</code>
file contains the most commonly used IPv4 functions, which are useful to many interface
control scripts. These functions include contacting running programs that have requested
information about changes in the status of an interface, setting hostnames, finding a
gateway device, verifying whether or not a particular device is down, and adding a default
route.
+ </div><div class="para">
+ As the functions required for IPv6 interfaces are different from IPv4 interfaces, a
<code
class="filename">/etc/sysconfig/network-scripts/network-functions-ipv6</code>
file exists specifically to hold this information. The functions in this file configure
and delete static IPv6 routes, create and remove tunnels, add and remove IPv6 addresses to
an interface, and test for the existence of an IPv6 address on an interface.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-networkscripts-static-routes.html"><strong>Prev</strong>6.4. Configuring
Static Routes</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-networkscripts-resources.html"><strong>Next</strong>6.6. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-interfaces.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-interfaces.html
new file mode 100644
index 0000000..79d2c81
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-interfaces.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.2. Interface Configuration 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Network_Interfaces.html" title="Chapter 6. Network
Interfaces" /><link rel="prev"
href="ch-Network_Interfaces.html" title="Chapter 6. Network
Interfaces" /><link rel="next"
href="s2-networkscripts-interfaces-chan.html" title="6.2.2. Channel Bonding
Interfaces" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-Network_Interfaces.html"><strong>Prev</strong></a></li
<li class="next"><a accesskey="n"
href="s2-networkscripts-interfaces-chan.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-networkscripts-interfaces"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-interfaces">6.2. Interface Configuration
Files</h2></div></div></div><a id="id428756"
class="indexterm"></a><a id="id428769"
class="indexterm"></a><div class="para">
+ Interface configuration files control the software interfaces for individual
network devices. As the system boots, it uses these files to determine what interfaces to
bring up and how to configure them. These files are usually named <code
class="filename">ifcfg-<em
class="replaceable"><code>name</code></em> </code>,
where <em class="replaceable"><code>name</code></em>
refers to the name of the device that the configuration file controls.
+ </div><div class="section"
id="s2-networkscripts-interfaces-eth0"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-networkscripts-interfaces-eth0">6.2.1. Ethernet
Interfaces</h3></div></div></div><a id="id529451"
class="indexterm"></a><a id="id529468"
class="indexterm"></a><div class="para">
+ One of the most common interface files is <code
class="filename">ifcfg-eth0</code>, which controls the first Ethernet
<em class="firstterm">network interface card</em> or <em
class="firstterm">NIC</em> 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">
+ The following is a sample <code
class="filename">ifcfg-eth0</code> file for a system using a fixed IP
address:
+ </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">
+ The values required in an interface configuration file can change based on other
values. For example, the <code class="filename">ifcfg-eth0</code>
file for an interface using DHCP looks different because IP information is provided by the
DHCP server:
+ </div><pre class="programlisting">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ The <span class="application"><strong>Network Administration
Tool</strong></span> (<code
class="command">system-config-network</code>) is an easy way to make
changes to the various network interface configuration files.
+ </div><div class="para">
+ However, it is also possible to manually edit the configuration files for a given
network interface.
+ </div><div class="para">
+ Below is a listing of the configurable parameters in an Ethernet interface
configuration file:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="command">BONDING_OPTS=<em
class="replaceable"><code>parameters</code></em>
</code> </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">Section 6.2.2, “Channel Bonding
Interfaces”</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="command">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="command">BOOTPROTO=<em
class="replaceable"><code>protocol</code></em>
</code> </span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>protocol</code></em>
</code> is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">none</code> — No boot-time protocol
should be used.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">bootp</code> — The BOOTP protocol
should be used.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">dhcp</code> — The DHCP protocol
should be used.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">BROADCAST=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the broadcast address. This directive is deprecated, as the value is calculated
automatically with <code class="command">ifcalc</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">DEVICE=<em
class="replaceable"><code>name</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>name</code></em> </code> 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="command">DHCP_HOSTNAME</code>
</span></dt><dd><div class="para">
+ Use this option only if the DHCP server requires the client to specify a hostname
before receiving an IP address.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">DNS<em
class="replaceable"><code>{1,2}</code></em>=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is a name server address to be placed in <code
class="filename">/etc/resolv.conf</code> if the <code
class="command">PEERDNS</code> directive is set to <code
class="command">yes</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">ETHTOOL_OPTS=<em
class="replaceable"><code>options</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>options</code></em> </code>
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"><code
class="command">ETHTOOL_OPTS="autoneg off speed 100 duplex
full"</code></pre><div class="para">
+ Instead of a custom initscript, use <code
class="command">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="note"><div
class="admonition_header"><h2>Set "autoneg off" 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="command">autoneg off</code>
option. This needs to be stated first, as the option entries are order-dependent.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">GATEWAY=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <em
class="replaceable"><code>address</code></em> is the IP
address of the network router or gateway device (if any).
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">HWADDR=<em
class="replaceable"><code>MAC-address</code></em>
</code> </span></dt><dd><div class="para">
+ where <em
class="replaceable"><code>MAC-address</code></em> is the
hardware address of the Ethernet device in the form <em
class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em>.
This directive must be used in machines containing more than one NIC to ensure that the
interfaces are assigned the correct device names regardless of the configured load order
for each NIC's module. This directive should <span class="bold
bold"><strong>not</strong></span> be used in conjunction with
<code class="command">MACADDR</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">IPADDR=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the IP address.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">MACADDR=<em
class="replaceable"><code>MAC-address</code></em>
</code> </span></dt><dd><div class="para">
+ where <em
class="replaceable"><code>MAC-address</code></em> is the
hardware address of the Ethernet device in the form <em
class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em>.
This directive is used to assign a MAC address to an interface, overriding the one
assigned to the physical NIC. This directive should <span class="bold
bold"><strong>not</strong></span> be used in conjunction with
<code class="command">HWADDR</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">MASTER=<em
class="replaceable"><code>bond-interface</code></em>
</code> </span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>bond-interface</code></em>
</code> is the channel bonding interface to which the Ethernet interface is linked.
+ </div><div class="para">
+ This directive is used in conjunction with the <code
class="command">SLAVE</code> directive.
+ </div><div class="para">
+ Refer to <a class="xref"
href="s2-networkscripts-interfaces-chan.html">Section 6.2.2, “Channel Bonding
Interfaces”</a> for more information about channel bonding interfaces.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">NETMASK=<em
class="replaceable"><code>mask</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>mask</code></em> </code> is
the netmask value.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">NETWORK=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the network address. This directive is deprecated, as the value is calculated
automatically with <code class="command">ifcalc</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">ONBOOT=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — This device should be
activated at boot-time.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — This device should not
be activated at boot-time.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">PEERDNS=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — Modify <code
class="filename">/etc/resolv.conf</code> if the DNS directive is set.
If using DHCP, then <code class="command">yes</code> is the
default.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — Do not modify <code
class="filename">/etc/resolv.conf</code>.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">SLAVE=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — This device is
controlled by the channel bonding interface specified in the <code
class="command">MASTER</code> directive.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — This device is <span
class="emphasis"><em>not</em></span> controlled by the
channel bonding interface specified in the <code
class="command">MASTER</code> directive.
+ </div></li></ul></div><div class="para">
+ This directive is used in conjunction with the <code
class="command">MASTER</code> directive.
+ </div><div class="para">
+ Refer to <a class="xref"
href="s2-networkscripts-interfaces-chan.html">Section 6.2.2, “Channel Bonding
Interfaces”</a> for more about channel bonding interfaces.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">SRCADDR=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the specified source IP address for outgoing packets.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">USERCTL=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — Non-<code
class="systemitem">root</code> users are allowed to control this
device.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — Non-<code
class="systemitem">root</code> users are not allowed to control this
device.
+ </div></li></ul></div></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Network_Interfaces.html"><strong>Prev</strong>Chapter 6. Network
Interfaces</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-networkscripts-interfaces-chan.html"><strong>Next</strong>6.2.2. Channel
Bonding Interfaces</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-resources.html
new file mode 100644
index 0000000..27e5ed5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-resources.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>6.6. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Network_Interfaces.html" title="Chapter 6. Network
Interfaces" /><link rel="prev"
href="s1-networkscripts-functions.html" title="6.5. Network Function
Files" /><link rel="next"
href="part-Infrastructure_Services.html" title="Part IV. Infrastructure
Services" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-functions.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n"
href="part-Infrastructure_Services.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-networkscripts-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-networkscripts-resources">6.6. Additional
Resources</h2></div></div></div><a id="id618403"
class="indexterm"></a><div class="para">
+ The following are resources which explain more about network interfaces.
+ </div><div class="section"
id="s2-networkscripts-docs-inst"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-networkscripts-docs-inst">6.6.1. Installed
Documentation</h3></div></div></div><div
class="variablelist"><dl><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 guide to available options for network configuration files, including IPv6
options not covered in this chapter.
+ </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">
+ This file contains a wealth of information about the <code
class="command">ip</code> command, which can be used to manipulate
routing tables, among other things. Use the <span
class="application"><strong>ggv</strong></span> or <span
class="application"><strong>kghostview</strong></span>
application to view this file.
+ </div></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-networkscripts-functions.html"><strong>Prev</strong>6.5. Network
Function Files</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="part-Infrastructure_Services.html"><strong>Next</strong>Part IV. Infrastructure
Services</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-static-routes.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-static-routes.html
new file mode 100644
index 0000000..0efac14
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-static-routes.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>6.4. Configuring Static 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Network_Interfaces.html" title="Chapter 6. Network
Interfaces" /><link rel="prev"
href="s1-networkscripts-control.html" title="6.3. Interface Control
Scripts" /><link rel="next"
href="s1-networkscripts-functions.html" title="6.5. Network Function
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="s1-networkscripts-control.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-networkscripts-functions.html"><strong>Next</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"
id="s1-networkscripts-static-routes">6.4. Configuring Static
Routes</h2></div></div></div><div class="para">
+ If static routes are required, they can be configured for each interface. This can be
useful if you have multiple interfaces in different subnets. Use the <code
class="command">route</code> command to display the IP routing table.
+ </div><div class="para">
+ 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 eth0 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><div class="formalpara"><h5 class="formalpara"
id="id618058">IP Command Arguments Format</h5>
+ Define a default gateway on the first line. This is only required if the default
gateway is not set via DHCP:
+ </div><pre class="programlisting">default <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</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.
+ </div><div class="para">
+ Define a static route. Each line is parsed as an individual route:
+ </div><pre class="programlisting"><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>
is the network number and netmask for the static route. <em
class="replaceable"><code>X.X.X.X</code></em> and <em
class="replaceable"><code>interface</code></em> are the IP
address and interface for the default gateway respectively. The <em
class="replaceable"><code>X.X.X.X</code></em> address does
not have to be the default gateway IP address. In most cases, <em
class="replaceable"><code>X.X.X.X</code></em> will be an IP
address in a different subnet, and <em
class="replaceable"><code>interface</code></em> will be the
interface that is connected to, or can reach, that subnet. Add as many static routes as
required.
+ </div><div class="para">
+ The following is a sample <code
class="filename">route-eth0</code> file using the IP command arguments
format. The default gateway is 192.168.0.1, interface eth0. The two static routes are for
the 10.10.10.0/24 and 172.16.1.0/24 networks:
+ </div><pre class="programlisting">default 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 eth0 interface
in the 192.168.0.0/24 subnet, and an eth1 interface (10.10.10.1) in the 10.10.10.0/24
subnet:
+ </div><pre class="programlisting">10.10.10.0/24 via 10.10.10.1
dev eth1</pre><div class="warning"><div
class="admonition_header"><h2>Duplicate default
gateways</h2></div><div class="admonition"><div
class="para">
+ If the default gateway is already assigned from DHCP, the IP command arguments format
can cause one of two errors during start-up, or when bringing up an interface from the
down state using the <code class="command">ifup</code> command:
"RTNETLINK answers: File exists" or 'Error: either "to" is a
duplicate, or "<em
class="replaceable"><code>X.X.X.X</code></em>" is a
garbage.', where <em
class="replaceable"><code>X.X.X.X</code></em> is the
gateway, or a different IP address. These errors can also occur if you have another route
to another network using the default gateway. Both of these errors are safe to ignore.
+ </div></div></div><div class="formalpara"><h5
class="formalpara" id="id618189">Network/Netmask Directives
Format</h5>
+ 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="programlisting">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 eth0. 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">
+ Subsequent static routes must be numbered sequentially, and must not skip any values.
For example, <code class="computeroutput">ADDRESS0</code>, <code
class="computeroutput">ADDRESS1</code>, <code
class="computeroutput">ADDRESS2</code>, and so on.
+ </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 eth0 interface in the 192.168.0.0/24
subnet, and an eth1 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">
+ Note that if DHCP is used, it can assign these settings automatically.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-networkscripts-control.html"><strong>Prev</strong>6.3. Interface
Control Scripts</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-networkscripts-functions.html"><strong>Next</strong>6.5. Network
Function Files</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-openssh-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-openssh-additional-resources.html
new file mode 100644
index 0000000..64bd9f6
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-openssh-additional-resources.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>9.5. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link
rel="prev" href="s2-ssh-beyondshell-tcpip.html"
title="9.4.2. Port Forwarding" /><link rel="next"
href="s2-openssh-useful-websites.html" title="9.5.2. Useful Websites"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-beyondshell-tcpip.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s
2-openssh-useful-websites.html"><strong>Next</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"
id="s1-openssh-additional-resources">9.5. Additional
Resources</h2></div></div></div><a id="id572379"
class="indexterm"></a><a id="id572391"
class="indexterm"></a><div class="para">
+ The OpenSSH and OpenSSL projects are in constant development, and the most up-to-date
information for them is available from their websites. The man pages for OpenSSH and
OpenSSL tools are also good sources of detailed information.
+ </div><div class="section"
id="s2-openssh-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-openssh-installed-docs">9.5.1. Installed
Documentation</h3></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><code
class="command">man ssh</code></span></dt><dd><div
class="para">
+ The manual page for <span
class="application"><strong>ssh</strong></span> containing
the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
scp</code></span></dt><dd><div class="para">
+ The manual page for <span
class="application"><strong>scp</strong></span> containing
the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
sftp</code></span></dt><dd><div class="para">
+ The manual page for <span
class="application"><strong>sftp</strong></span> containing
the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
sshd</code></span></dt><dd><div class="para">
+ The manual page for <span
class="application"><strong>sshd</strong></span> containing
the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
ssh-keygen</code></span></dt><dd><div
class="para">
+ The manual page for <span
class="application"><strong>ssh-keygen</strong></span>
containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
ssh_config</code></span></dt><dd><div
class="para">
+ The manual page with full description of available SSH client configuration
options.
+ </div></dd><dt class="varlistentry"><span
class="term"><code class="command">man
sshd_config</code></span></dt><dd><div
class="para">
+ The manual page with full description of available SSH daemon configuration
options.
+ </div></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-ssh-beyondshell-tcpip.html"><strong>Prev</strong>9.4.2. Port
Forwarding</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-openssh-useful-websites.html"><strong>Next</strong>9.5.2. Useful
Websites</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-additional-resources.html
new file mode 100644
index 0000000..0a3d812
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-additional-resources.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>C.5. References</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-proc.html" title="Appendix C. The proc File System"
/><link rel="prev" href="s1-proc-sysctl.html"
title="C.4. Using the sysctl Command" /><link rel="next"
href="app-Revision_History.html" title="Appendix D. Revision History"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-proc-sysctl.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="ap
p-Revision_History.html"><strong>Next</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"
id="s1-proc-additional-resources">C.5. References</h2></div></div></div><a
id="id544256" 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">Installed
Documentation</h1></div></div></div><a id="id544291"
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">Useful
Websites</h1></div></div></div><a id="id466791"
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>Prev</strong>C.4. Using the
sysctl Command</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="app-Revision_History.html"><strong>Next</strong>Appendix D. Revision
History</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-directories.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-directories.html
new file mode 100644
index 0000000..6797466
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-directories.html
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-proc.html" title="Appendix C. The proc File System"
/><link rel="prev" href="s2-proc-version.html"
title="C.2.29. /proc/version" /><link rel="next"
href="s2-proc-dir-bus.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-bus.html"><
strong>Next</strong></a></li></ul><div
class="section" id="s1-proc-directories"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-proc-directories">C.3. Directories within
/proc/</h2></div></div></div><a id="id469205"
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"
id="s2-proc-processdirs">C.3.1. Process
Directories</h3></div></div></div><a id="id668816"
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"
id="s3-proc-self">C.3.1.1. /proc/self/
</h4></div></div></div><a id="id643472"
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>Prev</strong>C.2.29.
/proc/version </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-bus.html"><strong>Next</strong>C.3.2.
/proc/bus/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-sysctl.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-sysctl.html
new file mode 100644
index 0000000..1f4294d
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-sysctl.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>C.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-proc.html" title="Appendix C. The proc File System"
/><link rel="prev" href="s2-proc-pid.html" title="C.3.12.
/proc/PID/" /><link rel="next"
href="s1-proc-additional-resources.html" title="C.5. References"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-proc-additional-resou
rces.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-proc-sysctl"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-proc-sysctl">C.4. Using the sysctl
Command</h2></div></div></div><a id="id670398"
class="indexterm"></a><a id="id670412"
class="indexterm"></a><a id="id670427"
class="indexterm"></a><a id="id670449"
class="indexterm"></a><a id="id670209"
class="indexterm"></a><a id="id670228"
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, the <code
class="command">init</code> program runs the <code
class="filename">/etc/rc.d/rc.sysinit</code> script. This script
contains a command to execute <code class="command">sysctl</code>
using <code class="filename">/etc/sysctl.conf</code> 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><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-proc-pid.html"><strong>Prev</strong>C.3.12. /proc/PID/
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-proc-additional-resources.html"><strong>Next</strong>C.5. References</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-topfiles.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-topfiles.html
new file mode 100644
index 0000000..074eff3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-proc-topfiles.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>C.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-proc.html" title="Appendix C. The proc File System"
/><link rel="prev" href="ch-proc.html"
title="Appendix C. The proc File System" /><link rel="next"
href="s2-proc-cmdline.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-cmdline.html"><st
rong>Next</strong></a></li></ul><div
class="section" id="s1-proc-topfiles"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-proc-topfiles">C.2. Top-level Files within the <code
class="filename">proc</code> File
System</h2></div></div></div><a id="id583103"
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"
id="s2-proc-buddyinfo">C.2.1. /proc/buddyinfo
</h3></div></div></div><a id="id595438"
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>Prev</strong>Appendix C. The proc
File System</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-cmdline.html"><strong>Next</strong>C.2.2.
/proc/cmdline </a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-additional-resources.html
new file mode 100644
index 0000000..0232c7d
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-additional-resources.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.5. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-RPM.html" title="Appendix A. RPM" /><link
rel="prev" href="s1-rpm-impressing.html" title="A.4. Practical
and Common Examples of RPM Usage" /><link rel="next"
href="s2-rpm-useful-websites.html" title="A.5.2. Useful Websites"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-rpm-impressing.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s
2-rpm-useful-websites.html"><strong>Next</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"
id="s1-rpm-additional-resources">A.5. Additional
Resources</h2></div></div></div><a id="id603881"
class="indexterm"></a><div class="para">
+ RPM is an extremely complex utility with many options and methods for querying,
installing, upgrading, and removing packages. Refer to the following resources to learn
more about RPM.
+ </div><div class="section"
id="s2-rpm-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-rpm-installed-docs">A.5.1. Installed
Documentation</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>Prev</strong>A.4. Practical
and Common Examples of RPM Usage</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-useful-websites.html"><strong>Next</strong>A.5.2. Useful
Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-impressing.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-impressing.html
new file mode 100644
index 0000000..0595de5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-impressing.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>A.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-RPM.html" title="Appendix A. RPM" /><link
rel="prev" href="s2-keys-checking.html" title="A.3.2. Verifying
Signature of Packages" /><link rel="next"
href="s1-rpm-additional-resources.html" title="A.5. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-keys-checking.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s1-r
pm-additional-resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-rpm-impressing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-rpm-impressing">A.4. Practical and Common Examples of RPM
Usage</h2></div></div></div><a id="id558059"
class="indexterm"></a><a id="id558071"
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">
+ Perhaps you have deleted some files by accident, but you are not sure what you
deleted. To verify your entire system and see what might be missing, you could try the
following command:
+ </div><a id="id436904"
class="indexterm"></a><a id="id575031"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre><div class="para">
+ If some files are missing or appear to have been corrupted, you should probably
either re-install the package or uninstall and then re-install the package.
+ </div></li><li class="listitem"><div
class="para">
+ At some point, you might see a file that you do not recognize. To find out which
package owns it, enter:
+ </div><a id="id481245"
class="indexterm"></a><a id="id481256"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qf /usr/bin/ghostscript</code>
+</pre><div class="para">
+ The output would look like the following:
+ </div><pre
class="screen">ghostscript-8.70-1.fc15.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">
+ and the appropriate package is verified.
+ </div></li><li class="listitem"><div
class="para">
+ Do you want to find out more information about a particular program? You can try the
following command to locate the documentation which came with the package that owns that
program:
+ </div><a id="id543243"
class="indexterm"></a><a id="id543255"
class="indexterm"></a><a id="id469100"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qdf /usr/bin/free</code>
+</pre><div class="para">
+ The output would be similar to the following:
+ </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">
+ You may find a new RPM, but you do not know what it does. To find information about
it, use the following command:
+ </div><a id="id635771"
class="indexterm"></a><a id="id635783"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qip
crontabs-1.10-31.fc15.noarch.rpm</code>
+</pre><div class="para">
+ The output would be similar to the following:
+ </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="id609478"
class="indexterm"></a><a id="id480724"
class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qlp
crontabs-1.10-31.fc15.noarch.rpm</code>
+</pre><div class="para">
+ The output is similar to the following:
+ </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>Prev</strong>A.3.2. Verifying
Signature of Packages</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-rpm-additional-resources.html"><strong>Next</strong>A.5. Additional
Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-using.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-using.html
new file mode 100644
index 0000000..a46e644
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-rpm-using.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>A.2. Using 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-RPM.html" title="Appendix A. RPM" /><link
rel="prev" href="ch-RPM.html" title="Appendix A. RPM"
/><link rel="next" href="sec-Installing_and_Upgrading.html"
title="A.2.2. Installing and Upgrading" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing_and_Upgrading.html"><str
ong>Next</strong></a></li></ul><div
class="section" id="s1-rpm-using"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-rpm-using">A.2. Using
RPM</h2></div></div></div><div class="para">
+ RPM has five basic modes of operation
+ <a id="id444910" 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">Section A.5,
“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"
id="s2-rpm-finding">A.2.1. Finding RPM
Packages</h3></div></div></div><a id="id421286"
class="indexterm"></a><a id="id441688"
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="id579838" class="indexterm"></a>
+ <a id="id636280" 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="id595211" class="indexterm"></a>
+ <a id="id427720" class="indexterm"></a>
+ . Refer to <a class="xref" href="ch-yum.html">Chapter 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://m...;.
+ </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>Prev</strong>Appendix A. RPM</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing_and_Upgrading.html"><strong>Next</strong>A.2.2. Installing
and Upgrading</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-services-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-services-additional-resources.html
new file mode 100644
index 0000000..34dbbfd
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-services-additional-resources.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>7.3. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Services_and_Daemons.html" title="Chapter 7. Services and
Daemons" /><link rel="prev"
href="s3-services-running-restarting.html" title="7.2.4. Restarting the
Service" /><link rel="next"
href="s2-services-additional-resources-books.html" title="7.3.2. Related
Books" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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.html"><strong>Prev</st
rong></a></li><li class="next"><a
accesskey="n"
href="s2-services-additional-resources-books.html"><strong>Next</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"
id="s1-services-additional-resources">7.3. Additional
Resources</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"
id="s2-services-additional-resources-installed">7.3.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="literal">systemctl</code>(1) — The manual page
for the <span
class="application"><strong>systemctl</strong></span>
utility.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s3-services-running-restarting.html"><strong>Prev</strong>7.2.4. Restarting
the Service</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-services-additional-resources-books.html"><strong>Next</strong>7.3.2. Related
Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-services-running.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-services-running.html
new file mode 100644
index 0000000..47e5ce2
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-services-running.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>7.2. Running Services</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Services_and_Daemons.html" title="Chapter 7. Services and
Daemons" /><link rel="prev"
href="ch-Services_and_Daemons.html" title="Chapter 7. Services and
Daemons" /><link rel="next"
href="s3-services-running-running.html" title="7.2.2. Running the
Service" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Services_and_Daemons.html"><strong>Prev</strong></a></li><l
i class="next"><a accesskey="n"
href="s3-services-running-running.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-services-running"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-services-running">7.2. Running
Services</h2></div></div></div><a id="id601997"
class="indexterm"></a><a id="id602014"
class="indexterm"></a><div class="para">
+ The <span
class="application"><strong>systemctl</strong></span>
utility also allows you to determine the status of a particular service, as well as to
start, stop, or restart a service.
+ </div><div class="note"><div
class="admonition_header"><h2>Do not use the service
utility</h2></div><div class="admonition"><div
class="para">
+ Although it is still possible to use the <span
class="application"><strong>service</strong></span> utility
to manage services that have init scripts installed in the <code
class="filename">/etc/rc.d/init.d/</code> directory, it is advised that
you use the <span
class="application"><strong>systemctl</strong></span>
utility.
+ </div></div></div><div class="section"
id="s3-services-running-checking"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s3-services-running-checking">7.2.1. Checking the Service
Status</h3></div></div></div><div class="para">
+ To determine the status of a service, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to determine the status of the <code
class="systemitem">httpd</code> service, type the following at a shell
prompt:
+ </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 class="para">
+ The above command provides a detailed information on the service status. If you only
need to verify that a service is running, use the <code
class="command">systemctl</code> command in the following form
instead:
+ </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="para">
+ For example:
+ </div><pre class="screen">~]$ <code
class="command">systemctl is-active httpd.service</code>
+active</pre><div class="para">
+ To display a list of all active system services, type:
+ </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">[output
truncated]</span></em></pre><div class="para">
+ As you can see, each line consists of the following columns:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="computeroutput">UNIT</code> — Provides
information whether the <code class="systemitem">systemd</code> unit
was properly loaded.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">ACTIVE</code> — Provides a
high-level unit activation state.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">SUB</code> — Provides a
low-level unit activation state.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">JOB</code> — Displays a pending
job for a unit.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">DESCRIPTION</code> — Provides a
brief description of the service.
+ </div></li></ul></div><div class="para">
+ In the example above, the <code class="systemitem">abrtd</code>
service is loaded, active, and running, and it does not have any pending jobs.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Services_and_Daemons.html"><strong>Prev</strong>Chapter 7. Services
and Daemons</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s3-services-running-running.html"><strong>Next</strong>7.2.2. Running
the Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-beyondshell.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-beyondshell.html
new file mode 100644
index 0000000..d5ff93c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-beyondshell.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>9.4. More Than a Secure Shell</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link
rel="prev" href="s2-ssh-clients-sftp.html" title="9.3.3. Using
the sftp Utility" /><link rel="next"
href="s2-ssh-beyondshell-tcpip.html" title="9.4.2. Port Forwarding"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-ssh
-beyondshell-tcpip.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-ssh-beyondshell"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-ssh-beyondshell">9.4. More Than a Secure
Shell</h2></div></div></div><div class="para">
+ A secure command line interface is just the beginning of the many ways SSH can be
used. Given the proper amount of bandwidth, X11 sessions can be directed over an SSH
channel. Or, by using TCP/IP forwarding, previously insecure port connections between
systems can be mapped to specific SSH channels.
+ </div><div class="section"
id="s2-ssh-beyondshell-x11"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-beyondshell-x11">9.4.1. X11
Forwarding</h3></div></div></div><a id="id555740"
class="indexterm"></a><div class="para">
+ To open an X11 session over an SSH connection, use a command in the following form:
+ </div><pre class="screen"><code
class="command">ssh -Y <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code> with <code
class="systemitem">john</code> as a username, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh -Y john(a)penguin.example.com</code>
+john(a)penguin.example.com's password:</pre><div class="para">
+ When an X program is run from the secure shell prompt, the SSH client and server
create a new secure channel, and the X program data is sent over that channel to the
client machine transparently.
+ </div><div class="para">
+ X11 forwarding can be very useful. For example, X11 forwarding can be used to create
a secure, interactive session of the <span
class="application"><strong>Printer
Configuration</strong></span> utility. To do this, connect to the server using
<span class="application"><strong>ssh</strong></span>
and type:
+ </div><pre class="screen">~]$ <code
class="command">system-config-printer
&</code></pre><div class="para">
+ The <span class="application"><strong>Printer Configuration
Tool</strong></span> will appear, allowing the remote user to safely configure
printing on the remote system.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-clients-sftp.html"><strong>Prev</strong>9.3.3. Using
the sftp Utility</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-beyondshell-tcpip.html"><strong>Next</strong>9.4.2. Port
Forwarding</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-clients.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-clients.html
new file mode 100644
index 0000000..bd5b198
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-clients.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>9.3. OpenSSH Clients</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link
rel="prev" href="s2-ssh-configuration-keypairs.html"
title="9.2.4. Using a Key-Based Authentication" /><link
rel="next" href="s2-ssh-clients-scp.html" title="9.3.2. Using the
scp 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-ssh-configuration-keypairs.html"><strong>Prev</strong></a></li><li
class="next"
<a accesskey="n"
href="s2-ssh-clients-scp.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-ssh-clients"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-ssh-clients">9.3. OpenSSH
Clients</h2></div></div></div><a id="id571900"
class="indexterm"></a><div class="note"><div
class="admonition_header"><h2>Make sure you have relevant packages
installed</h2></div><div class="admonition"><div
class="para">
+ To connect to an OpenSSH server from a client
machine, you must have the <span
class="package">openssh-clients</span> and <span
class="package">openssh</span> packages installed. Refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><div class="section"
id="s2-ssh-clients-ssh"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ssh-clients-ssh">9.3.1. Using the ssh
Utility</h3></div></div></div><a id="id432847"
class="indexterm"></a><a id="id432863"
class="indexterm"></a><div class="para">
+ <code class="command">ssh</code> allows you to log in to a
remote machine and execute commands there. It is a secure replacement for the <code
class="command">rlogin</code>, <code
class="command">rsh</code>, and <code
class="command">telnet</code> programs.
+ </div><div class="para">
+ Similarly to <code class="command">telnet</code>, to log in to
a remote machine named <code
class="systemitem">penguin.example.com</code>, type the following
command at a shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">ssh penguin.example.com</code></pre><div
class="para">
+ This will log you in with the same username you are using on a local machine. If you
want to specify a different one, use a command in the <code
class="command">ssh <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code>
form. For example, to log in as <code
class="systemitem">john</code>, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh john(a)penguin.example.com</code></pre><div
class="para">
+ The first time you initiate a connection, you will be presented with a message
similar to this:
+ </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">
+ Type <strong
class="userinput"><code>yes</code></strong> to confirm. You
will see a notice that the server has been added to the list of known hosts, and a prompt
asking for your password:
+ </div><pre class="screen">Warning: Permanently added
'penguin.example.com' (RSA) to the list of known hosts.
+john(a)penguin.example.com's password:</pre><div
class="important"><div
class="admonition_header"><h2>Updating the host key of an SSH
server</h2></div><div class="admonition"><div
class="para">
+ If the SSH server's host key changes, the client notifies the user that the
connection cannot proceed until the server's host key is deleted from the <code
class="filename">~/.ssh/known_hosts</code> file. To do so, open the
file in a text editor, and remove a line containing the remote machine name at the
beginning. Before doing this, however, contact the system administrator of the SSH server
to verify the server is not compromised.
+ </div></div></div><div class="para">
+ After entering the password, you will be provided with a shell prompt for the remote
machine.
+ </div><div class="para">
+ Alternatively, the <code class="command">ssh</code> program can
be used to execute a command on the remote machine without logging in to a shell prompt.
The syntax for that is <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>.
For example, if you want to execute the <code
class="command">whoami</code> command on <code
class="systemitem">penguin.example.com</code>, type:
+ </div><pre class="screen">~]$ <code
class="command">ssh john(a)penguin.example.com whoami</code>
+john(a)penguin.example.com's password:
+john</pre><div class="para">
+ After you enter the correct password, the username will be displayed, and you will
return to your local shell prompt.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-keypairs.html"><strong>Prev</strong>9.2.4. Using
a Key-Based Authentication</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-clients-scp.html"><strong>Next</strong>9.3.2. Using
the scp Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-configuration.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-configuration.html
new file mode 100644
index 0000000..16405a3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-ssh-configuration.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>9.2. An OpenSSH 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link
rel="prev" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH"
/><link rel="next" href="s2-ssh-configuration-sshd.html"
title="9.2.2. Starting an OpenSSH Server" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-OpenSSH.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-ssh-configuration-s
shd.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-ssh-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-ssh-configuration">9.2. An OpenSSH
Configuration</h2></div></div></div><div
class="para">
+ In order to perform tasks described in this section, you must have superuser
privileges. To obtain them, log in as <code
class="systemitem">root</code> by typing:
+ </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"
id="s2-ssh-configuration-configs">9.2.1. Configuration
Files</h3></div></div></div><a id="id627514"
class="indexterm"></a><div class="para">
+ There are two different sets of configuration files: those for client programs (that
is, <code class="command">ssh</code>, <code
class="command">scp</code>, and <code
class="command">sftp</code>), and those for the server (the <code
class="command">sshd</code> daemon).
+ </div><a id="id627546"
class="indexterm"></a><div class="para">
+ System-wide SSH configuration information is stored in the <code
class="filename">/etc/ssh/</code> directory. See <a
class="xref"
href="s1-ssh-configuration.html#table-ssh-configuration-configs-system">Table 9.1,
“System-wide configuration files”</a> for a description of its content.
+ </div><div class="table"
id="table-ssh-configuration-configs-system"><h6>Table 9.1. System-wide
configuration files</h6><div class="table-contents"><table
summary="System-wide configuration files"
border="1"><colgroup><col width="38%"
class="filename" /><col width="63%"
class="description" /></colgroup><thead><tr><th>
+ Configuration File
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc/ssh/moduli</code>
+ </td><td>
+ Contains Diffie-Hellman groups used for the Diffie-Hellman key exchange which is
critical for constructing a secure transport layer. When keys are exchanged at the
beginning of an SSH session, a shared, secret value is created which cannot be determined
by either party alone. This value is then used to provide host authentication.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_config</code>
+ </td><td>
+ The default SSH client configuration file. Note that it is overridden by <code
class="filename">~/.ssh/config</code> if it exists.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/sshd_config</code>
+ </td><td>
+ The configuration file for the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_dsa_key</code>
+ </td><td>
+ The DSA private key used by the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code
class="filename">/etc/ssh/ssh_host_dsa_key.pub</code>
+ </td><td>
+ The DSA public key used by the <code
class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_key</code>
+ </td><td>
+ The RSA private key used by the <code
class="command">sshd</code> daemon for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_key.pub</code>
+ </td><td>
+ The RSA public key used by the <code
class="command">sshd</code> daemon for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_rsa_key</code>
+ </td><td>
+ The RSA private key used by the <code
class="command">sshd</code> daemon for version 2 of the SSH protocol.
+ </td></tr><tr><td>
+ <code
class="filename">/etc/ssh/ssh_host_rsa_key.pub</code>
+ </td><td>
+ The RSA public key used by the <code
class="command">sshd</code> for version 2 of the SSH protocol.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><a id="id531600"
class="indexterm"></a><div class="para">
+ User-specific SSH configuration information is stored in the user's home
directory within the <code class="filename">~/.ssh/</code>
directory. See <a class="xref"
href="s1-ssh-configuration.html#table-ssh-configuration-configs-user">Table 9.2,
“User-specific configuration files”</a> for a description of its content.
+ </div><div class="table"
id="table-ssh-configuration-configs-user"><h6>Table 9.2. User-specific
configuration files</h6><div class="table-contents"><table
summary="User-specific configuration files"
border="1"><colgroup><col width="38%"
class="filename" /><col width="63%"
class="description" /></colgroup><thead><tr><th>
+ Configuration File
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">~/.ssh/authorized_keys</code>
+ </td><td>
+ Holds a list of authorized public keys for servers. When the client connects to a
server, the server authenticates the client by checking its signed public key stored
within this file.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_dsa</code>
+ </td><td>
+ Contains the DSA private key of the user.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_dsa.pub</code>
+ </td><td>
+ The DSA public key of the user.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_rsa</code>
+ </td><td>
+ The RSA private key used by <code
class="command">ssh</code> for version 2 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_rsa.pub</code>
+ </td><td>
+ The RSA public key used by <code class="command">ssh</code>
for version 2 of the SSH protocol
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/identity</code>
+ </td><td>
+ The RSA private key used by <code
class="command">ssh</code> for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/identity.pub</code>
+ </td><td>
+ The RSA public key used by <code class="command">ssh</code>
for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/known_hosts</code>
+ </td><td>
+ Contains DSA host keys of SSH servers accessed by the user. This file is very
important for ensuring that the SSH client is connecting the correct SSH server.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ Refer to the <code class="command">ssh_config</code> and
<code class="command">sshd_config</code> man pages for information
concerning the various directives available in the SSH configuration files.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-OpenSSH.html"><strong>Prev</strong>Chapter 9. OpenSSH</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-configuration-sshd.html"><strong>Next</strong>9.2.2. Starting
an OpenSSH Server</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysconfig-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysconfig-additional-resources.html
new file mode 100644
index 0000000..75c7982
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysconfig-additional-resources.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-The_sysconfig_Directory.html" title="Appendix B. The sysconfig
Directory" /><link rel="prev"
href="s1-sysconfig-etcsysconf-dir.html" title="B.2. Directories in the
/etc/sysconfig/ Directory" /><link rel="next"
href="ch-proc.html" title="Appendix C. 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"><strong>Prev<
/strong></a></li><li class="next"><a
accesskey="n"
href="ch-proc.html"><strong>Next</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"
id="s1-sysconfig-additional-resources">B.3. Additional
Resources</h2></div></div></div><a id="id471735"
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"
id="s2-sysconfig-installed-documentation">B.3.1. Installed
Documentation</h3></div></div></div><a id="id471773"
class="indexterm"></a><div
class="variablelist"><dl><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>Prev</strong>B.2. Directories
in the /etc/sysconfig/ Directory</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-proc.html"><strong>Next</strong>Appendix C. The proc
File System</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.html
new file mode 100644
index 0000000..8222cbd
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.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. 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-The_sysconfig_Directory.html" title="Appendix B. The sysconfig
Directory" /><link rel="prev"
href="ch-The_sysconfig_Directory.html" title="Appendix B. The sysconfig
Directory" /><link rel="next"
href="s1-sysconfig-additional-resources.html" title="B.3. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-The_sysconfig_Directory.html"><strong>Pr
ev</strong></a></li><li class="next"><a
accesskey="n"
href="s1-sysconfig-additional-resources.html"><strong>Next</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"
id="s1-sysconfig-etcsysconf-dir">B.2. Directories in the /etc/sysconfig/
Directory</h2></div></div></div><a id="id589739"
class="indexterm"></a><div class="para">
+ The following directories are normally found in <code
class="filename">/etc/sysconfig/</code>.
+ </div><a id="id669680"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="filename">/etc/sysconfig/cbq/</code>
</span></dt><dd><div class="para">
+ <a id="id669083" 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="id471850" 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="id668734" 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">
+ Various shared network function scripts which should not be edited directly.
+ </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">Chapter 6, <em>Network
Interfaces</em></a>.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-The_sysconfig_Directory.html"><strong>Prev</strong>Appendix B. The
sysconfig Directory</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysconfig-additional-resources.html"><strong>Next</strong>B.3. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-additional-resources.html
new file mode 100644
index 0000000..49b0585
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_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>16.5. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring
Tools" /><link rel="prev" href="s1-sysinfo-hardware.html"
title="16.4. Hardware" /><link rel="next"
href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing
and Managing Log 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="s1-sysinfo-hardware.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n"
href="ch-Viewing_and_Managing_Log_Files.html"><strong>Next</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"
id="s1-sysinfo-additional-resources">16.5. Additional
Resources</h2></div></div></div><div
class="para">
+ To learn more about gathering system information, refer to the following resources.
+ </div><div class="section"
id="s2-sysinfo-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-sysinfo-installed-docs">16.5.1. Installed
Documentation</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">ps --help</code> — Displays a list of
options that can be used with <code class="command">ps</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">top</code> manual page — Execute
<code class="command">man top</code> to learn more about <code
class="command">top</code> and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">free</code> manual page — Execute
<code class="command">man free</code> to learn more about <code
class="command">free</code> and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">df</code> manual page — Execute
<code class="command">man df</code> to learn more about the <code
class="command">df</code> command and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">du</code> manual page — Execute
<code class="command">man du</code> to learn more about the <code
class="command">du</code> command and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">lspci</code> manual page — Execute
<code class="command">man lspci</code> to learn more about the
<code class="command">lspci</code> command and its many options.
+ </div></li><li class="listitem"><div
class="para">
+ <a id="id438441" class="indexterm"></a>
+ <code class="filename">/proc/</code> directory — The
contents of the <code class="filename">/proc/</code> directory can
also be used to gather more detailed system information.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-sysinfo-hardware.html"><strong>Prev</strong>16.4. Hardware</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Viewing_and_Managing_Log_Files.html"><strong>Next</strong>Chapter 17. Viewing
and Managing Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-filesystems.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-filesystems.html
new file mode 100644
index 0000000..29c4d4b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-filesystems.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.3. 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring
Tools" /><link rel="prev"
href="s1-sysinfo-memory-usage.html" title="16.2. Memory Usage"
/><link rel="next" href="s1-sysinfo-hardware.html"
title="16.4. Hardware" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey
="n"
href="s1-sysinfo-hardware.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-sysinfo-filesystems"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysinfo-filesystems">16.3. File
Systems</h2></div></div></div><a id="id593245"
class="indexterm"></a><a id="id417855"
class="indexterm"></a><a id="id558718"
class="indexterm"></a><div class="para">
+ The <code class="command">df</code> command reports the
system's disk space usage. If you Execute the command <code
class="command">df</code> at a shell prompt, the output looks similar
to the following:
+ </div><pre class="screen">Filesystem 1K-blocks
Used Available Use% Mounted on
+rootfs 6726160 3091216 3566620 47% /
+udev 500716 0 500716 0% /dev
+tmpfs 507840 2152 505688 1% /dev/shm
+tmpfs 507840 644 507196 1% /run
+/dev/sda1 6726160 3091216 3566620 47% /
+tmpfs 507840 0 507840 0% /sys/fs/cgroup
+tmpfs 507840 0 507840 0% /media
+/dev/sda4 139412616 105018908 27367684 80% /home
+/dev/sda1 6726160 3091216 3566620 47% /tmp
+/dev/sda1 6726160 3091216 3566620 47% /var/tmp</pre><div
class="para">
+ By default, this utility 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, use the command <code class="command">df -h</code>. The
<code class="command">-h</code> argument stands for human-readable
format. The output looks similar to the following:
+ </div><pre class="screen">Filesystem Size Used Avail
Use% Mounted on
+rootfs 6.5G 3.0G 3.5G 47% /
+udev 489M 0 489M 0% /dev
+tmpfs 496M 2.2M 494M 1% /dev/shm
+tmpfs 496M 644K 496M 1% /run
+/dev/sda1 6.5G 3.0G 3.5G 47% /
+tmpfs 496M 0 496M 0% /sys/fs/cgroup
+tmpfs 496M 0 496M 0% /media
+/dev/sda4 133G 101G 27G 80% /home
+/dev/sda1 6.5G 3.0G 3.5G 47% /tmp
+/dev/sda1 6.5G 3.0G 3.5G 47% /var/tmp</pre><a
id="id591641" class="indexterm"></a><a
id="id436982" class="indexterm"></a><div
class="para">
+ In the list of mounted partitions, there is an entry for <code
class="filename">/dev/shm</code>. This entry represents the
system's virtual memory file system.
+ </div><a id="id509350"
class="indexterm"></a><div class="para">
+ The <code class="command">du</code> command displays the
estimated amount of space being used by files in a directory. If you execute <code
class="command">du</code> at a shell prompt, the disk usage for each of
the subdirectories is displayed in a list. The grand total for the current directory and
subdirectories are also shown as the last line in the list. If you do not want to see the
totals for all the subdirectories, use the command <code
class="command">du -hs</code> to see only the grand total for the
directory in human-readable format. Use the <code class="command">du
--help</code> command to see more options.
+ </div><div class="para">
+ To view the system's partitions and disk space usage in a graphical format, use
the <span class="guilabel"><strong>GNOME System
Monitor</strong></span> by selecting <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
executing the <code class="command">gnome-system-monitor</code>
command at a shell prompt. Select the <span
class="guilabel"><strong>File Systems</strong></span> tab
to view the system's partitions.
+ </div><div class="figure"
id="fig-sysinfo-filesystems"><div
class="figure-contents"><div class="mediaobject"><img
src="images/system-monitor-file-systems.png" alt="GNOME System Monitor —
File Systems tab" /><div class="longdesc"><div
class="para">
+ File Systems tab of the GNOME System Monitor
+ </div></div></div></div><h6>Figure 16.3. GNOME System
Monitor — File Systems tab </h6></div><br class="figure-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-memory-usage.html"><strong>Prev</strong>16.2. Memory
Usage</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-hardware.html"><strong>Next</strong>16.4. Hardware</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-hardware.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-hardware.html
new file mode 100644
index 0000000..3fdd59f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-hardware.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>16.4. Hardware</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring
Tools" /><link rel="prev"
href="s1-sysinfo-filesystems.html" title="16.3. File Systems"
/><link rel="next" href="s1-sysinfo-additional-resources.html"
title="16.5. Additional Resources" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-filesystems.html"><strong>Prev</strong></a></li><li
cla
ss="next"><a accesskey="n"
href="s1-sysinfo-additional-resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-sysinfo-hardware"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-sysinfo-hardware">16.4. Hardware</h2></div></div></div><a
id="id551370" class="indexterm"></a><a
id="id625502" class="indexterm"></a><div
class="para">
+ If you are having trouble configuring your hardware or just want to know what hardware
is in your system, you can use the <code
class="command">lspci</code> command to list all PCI devices. Use the
command <code class="command">lspci -v</code> for more verbose
information or <code class="command">lspci -vv</code> for very
verbose output.
+ </div><div class="para">
+ For example, <code class="command">lspci</code> can be used to
determine the manufacturer, model, and memory size of a system's video card:
+ </div><pre class="screen">00:02.1 Display controller: Intel
Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
+ Subsystem: Lenovo Device 20e4
+ Flags: bus master, fast devsel, latency 0
+ Memory at f4200000 (64-bit, non-prefetchable) [size=1M]
+ Capabilities: [d0] Power Management version 3</pre><div
class="para">
+ The <code class="command">lspci</code> is also useful to
determine the network card in your system if you do not know the manufacturer or model
number.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-sysinfo-filesystems.html"><strong>Prev</strong>16.3. File
Systems</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-additional-resources.html"><strong>Next</strong>16.5. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-memory-usage.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-memory-usage.html
new file mode 100644
index 0000000..dcb155e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-sysinfo-memory-usage.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>16.2. 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring
Tools" /><link rel="prev"
href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring
Tools" /><link rel="next"
href="s1-sysinfo-filesystems.html" title="16.3. 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="ch-System_Monitoring_Tools.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n"
href="s1-sysinfo-filesystems.html"><strong>Next</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"
id="s1-sysinfo-memory-usage">16.2. Memory
Usage</h2></div></div></div><a id="id480510"
class="indexterm"></a><a id="id464684"
class="indexterm"></a><a id="id464694"
class="indexterm"></a><a id="id468422"
class="indexterm"></a><div class="para">
+ The <code class="command">free</code> command displays the total
amount of physical memory and swap space for the system as well as the amount of memory
that is used, free, shared, in kernel buffers, and cached.
+ </div><pre class="screen"> total used
free shared buffers cached
+Mem: 4017660 1619044 2398616 0 59864 637968
+-/+ buffers/cache: 921212 3096448
+Swap: 3071996 0 3071996</pre><div class="para">
+ The command <code class="command">free -m</code> shows the same
information in megabytes, which are easier to read.
+ </div><pre class="screen"> total used
free shared buffers cached
+Mem: 3923 1569 2353 0 58 626
+-/+ buffers/cache: 884 3038
+Swap: 2999 0 2999</pre><div class="para">
+ If you prefer a graphical interface for <code
class="command">free</code>, you can use the <span
class="application"><strong>GNOME System
Monitor</strong></span>. To start it from the desktop, 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
execute <code class="command">gnome-system-monitor</code> at a shell
prompt. Click on the <span
class="guilabel"><strong>Resources</strong></span> tab.
+ </div><div class="figure"
id="fig-sysinfo-memory"><div class="figure-contents"><div
class="mediaobject"><img
src="images/system-monitor-resources.png" alt="GNOME System Monitor —
Resources tab" /><div class="longdesc"><div
class="para">
+ Resources tab of the GNOME System Monitor
+ </div></div></div></div><h6>Figure 16.2. GNOME System
Monitor — Resources tab </h6></div><br class="figure-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-System_Monitoring_Tools.html"><strong>Prev</strong>Chapter 16. System
Monitoring Tools</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-sysinfo-filesystems.html"><strong>Next</strong>16.3. File
Systems</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-configui.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-configui.html
new file mode 100644
index 0000000..8d5b1ba
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-configui.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>3.2. User Manager 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="Chapter 3. Managing Users
and Groups" /><link rel="prev"
href="ch-Managing_Users_and_Groups.html" title="Chapter 3. Managing Users
and Groups" /><link rel="next"
href="s2-redhat-config-users-group-new.html" title="3.2.2. Adding a New
Group" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-Managing_Users_and_Groups.html"><st
rong>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="s2-redhat-config-users-group-new.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-users-configui"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-configui">3.2. User Manager
Tool</h2></div></div></div><a id="id508003"
class="indexterm"></a><a id="id508015"
class="indexterm"></a><a id="id508027"
class="indexterm"></a><a id="id523710"
class="indexterm"></a><a id="id523722"
class="indexterm"></a><a id="id523734"
class="indexterm"></a><div class="para">
+ The <span class="application"><strong>User
Manager</strong></span> allows you to view, modify, add, and delete local
users and groups.
+ </div><div class="figure"
id="fig-Users_Groups-User_Manager"><div
class="figure-contents"><div class="mediaobject"><img
src="images/user-manager.png" alt="The GNOME User Manager"
/><div class="longdesc"><div class="para">
+ The GNOME User Manager allows you to manage users
+ </div></div></div></div><h6>Figure 3.5. The GNOME User
Manager</h6></div><br class="figure-break" /><div
class="para">
+ You can start the <span class="application"><strong>User
Manager</strong></span> by clicking <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guimenuitem"><strong>Other</strong></span>
→ <span class="guimenuitem"><strong>Users and
Groups</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu.
Alternatively, you can enter <code
class="command">system-config-users</code> at the shell prompt to open
the <span class="application"><strong>User
Manager</strong></span>. Viewing and modifying user and group information
requires superuser privileges. If you are not the superuser when you open the <span
class="application"><strong>User Manager</strong></span>,
it will prompt you for the superuser password.
+ </div><a id="id523825"
class="indexterm"></a><a id="id523837"
class="indexterm"></a><div class="para">
+ To view a list of local users on the system, click the <span
class="guilabel"><strong>Users</strong></span> tab. To view
a list of local groups on the system, click the <span
class="guilabel"><strong>Groups</strong></span> tab.
+ </div><div class="para">
+ To find a specific user or group, type the first few letters of the name in the
<span class="guilabel"><strong>Search
filter</strong></span> field. Press <span
class="keycap"><strong>Enter</strong></span> or click the
<span class="guibutton"><strong>Apply
filter</strong></span> button. The filtered list is displayed.
+ </div><div class="para">
+ To sort the users, click on the column User Name and for groups click on Group Name.
The users or groups are sorted according to the value of that column.
+ </div><div class="para">
+ Fedora reserves user IDs below 500 for system users. By default, the <span
class="application"><strong>User Manager</strong></span>
does not display system users. To view all users, including the system users, go to
<span class="guimenu"><strong>Edit</strong></span> →
<span
class="guimenuitem"><strong>Preferences</strong></span> and
uncheck <span class="guilabel"><strong>Hide system users and
groups</strong></span> from the dialog box.
+ </div><div class="section"
id="s2-redhat-config-users-user-new"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-redhat-config-users-user-new">3.2.1. Adding a New
User</h3></div></div></div><a id="id523909"
class="indexterm"></a><div class="para">
+ To add a new user, click the <span
class="guibutton"><strong>Add User</strong></span> button.
A window as shown in <a class="xref"
href="s1-users-configui.html#user-new-fig">Figure 3.6, “Creating a new
user”</a> appears. Type the username and full name for the new user in the
appropriate fields. Type the user's password in the <span
class="guilabel"><strong>Password</strong></span> and
<span class="guilabel"><strong>Confirm
Password</strong></span> fields. The password must be at least six
characters.
+ </div><div class="note"><div
class="admonition_header"><h2>Password security
advice</h2></div><div class="admonition"><div
class="para">
+ It is advisable to use a much longer password, as this makes it more difficult for
an intruder to guess it and access the account without permission. It is also recommended
that the password not be based on a dictionary term: use a combination of letters, numbers
and special characters.
+ </div></div></div><div class="para">
+ Select a login shell from the pulldown list. If you are not sure which shell to
select, accept the default value of <code
class="command">/bin/bash</code>. The default home directory is
<code class="filename">/home/<em
class="replaceable"><code>username</code></em>/</code>.
You can change the home directory that is created for the user, or you can choose not to
create the home directory by unselecting <span
class="guilabel"><strong>Create home
directory</strong></span>.
+ </div><div class="para">
+ If you select to create the home directory, default configuration files are copied
from the <code class="filename">/etc/skel/</code> directory into the
new home directory.
+ </div><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em>
(UPG) scheme. The UPG scheme does not add or change anything in the standard UNIX way of
handling groups; it offers a new convention. Whenever you create a new user, by default, a
unique group with the same name as the user is created. If you do not want to create this
group, unselect <span class="guilabel"><strong>Create a private
group for the user</strong></span>.
+ </div><div class="para">
+ To specify a user ID for the user, select <span
class="guilabel"><strong>Specify user ID
manually</strong></span>. If the option is not selected, the next available
user ID above 500 is assigned to the new user. Because Fedora reserves user IDs below 500
for system users, it is not advisable to manually assign user IDs 1-499.
+ </div><div class="para">
+ Click <span
class="guibutton"><strong>OK</strong></span> to create the
user.
+ </div><div class="figure" id="user-new-fig"><div
class="figure-contents"><div class="mediaobject"><img
src="images/user-manager-add-user.png" alt="Creating a new user"
/><div class="longdesc"><div class="para">
+ Creating a new user with the Create New User dialog
+ </div></div></div></div><h6>Figure 3.6. Creating a
new user</h6></div><br class="figure-break" /><div
class="para">
+ To configure more advanced user properties, such as password expiration, modify the
user's properties after adding the user.
+ </div><h4 id="id524058">Modifying User
Properties</h4><a id="id524062"
class="indexterm"></a><a id="id524074"
class="indexterm"></a><div class="para">
+ To view the properties of an existing user, click on the <span
class="guilabel"><strong>Users</strong></span> tab, select
the user from the user list, and click <span
class="guimenuitem"><strong>Properties</strong></span> from
the menu (or choose <span
class="guimenu"><strong>File</strong></span> → <span
class="guimenuitem"><strong>Properties</strong></span> from
the pulldown menu). A window similar to <a class="xref"
href="s1-users-configui.html#user-properties-fig">Figure 3.7, “User
Properties”</a> appears.
+ </div><div class="figure"
id="user-properties-fig"><div class="figure-contents"><div
class="mediaobject"><img src="images/user-manager-edit-user.png"
alt="User Properties" /><div class="longdesc"><div
class="para">
+ Modifying user properties
+ </div></div></div></div><h6>Figure 3.7. User
Properties</h6></div><br class="figure-break" /><div
class="para">
+ The <span class="guilabel"><strong>User
Properties</strong></span> window is divided into multiple tabbed pages:
+ </div><a id="id524150"
class="indexterm"></a><a id="id524162"
class="indexterm"></a><a id="id524174"
class="indexterm"></a><a id="id524186"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>User
Data</strong></span> — Shows the basic user information configured when you
added the user. Use this tab to change the user's full name, password, home directory,
or login shell.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Account
Info</strong></span> — Select <span
class="guilabel"><strong>Enable account
expiration</strong></span> if you want the account to expire on a certain
date. Enter the date in the provided fields. Select <span
class="guilabel"><strong>Local password is
locked</strong></span> to lock the user account and prevent the user from
logging into the system.
+ </div></li><li class="listitem"><div
class="para">
+ <span class="guilabel"><strong>Password
Info</strong></span> — Displays the date that the user's password last
changed. To force the user to change passwords after a certain number of days, select
<span class="guilabel"><strong>Enable password
expiration</strong></span> and enter a desired value in the <span
class="guilabel"><strong>Days before change
required:</strong></span> field. The number of days before the user's
password expires, the number of days before the user is warned to change passwords, and
days before the account becomes inactive can also be changed.
+ </div></li><li class="listitem"><div
class="para">
+ <span
class="guilabel"><strong>Groups</strong></span> — Allows
you to view and configure the Primary Group of the user, as well as other groups that you
want the user to be a member of.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Managing_Users_and_Groups.html"><strong>Prev</strong>Chapter 3. Managing
Users and Groups</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-redhat-config-users-group-new.html"><strong>Next</strong>3.2.2. Adding
a New Group</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-additional-resources.html
new file mode 100644
index 0000000..5d1625f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-additional-resources.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>3.8. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="Chapter 3. Managing Users
and Groups" /><link rel="prev"
href="s1-users-groups-shadow-utilities.html" title="3.7. Shadow
Passwords" /><link rel="next"
href="part-Package_Management.html" title="Part II. Package
Management" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-shadow-utilities.html"><strong>Prev</str
ong></a></li><li class="next"><a
accesskey="n"
href="part-Package_Management.html"><strong>Next</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"
id="s1-users-groups-additional-resources">3.8. Additional
Resources</h2></div></div></div><a id="id419259"
class="indexterm"></a><a id="id419271"
class="indexterm"></a><div class="para">
+ For more information about users and groups, and tools to manage them, refer to the
following resources.
+ </div><div class="section"
id="s2-users-groups-documentation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-users-groups-documentation">3.8.1. Installed
Documentation</h3></div></div></div><a id="id419297"
class="indexterm"></a><a id="id419313"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ Related man pages — There are a number of man pages for the various applications
and configuration files involved with managing users and groups. Some of the more
important man pages have been listed here:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">User and Group
Administrative Applications</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">man chage</code> — A command to
modify password aging policies and account expiration.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man gpasswd</code> — A command to
administer the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man groupadd</code> — A command to
add groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man grpck</code> — A command to
verify the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man groupdel</code> — A command to
remove groups.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man groupmod</code> — A command to
modify group membership.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man pwck</code> — A command to
verify the <code class="filename">/etc/passwd</code> and <code
class="filename">/etc/shadow</code> files.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man pwconv</code> — A tool to
convert standard passwords to shadow passwords.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man pwunconv</code> — A tool to
convert shadow passwords to standard passwords.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man useradd</code> — A command to
add users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man userdel</code> — A command to
remove users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man usermod</code> — A command to
modify users.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term">Configuration
Files</span></dt><dd><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="command">man 5 group</code> — The file
containing group information for the system.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man 5 passwd</code> — The file
containing user information for the system.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">man 5 shadow</code> — The file
containing passwords and account expiration information for the system.
+ </div></li></ul></div></dd></dl></div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-users-groups-shadow-utilities.html"><strong>Prev</strong>3.7. Shadow
Passwords</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="part-Package_Management.html"><strong>Next</strong>Part II. Package
Management</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-private-groups.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-private-groups.html
new file mode 100644
index 0000000..7f01891
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-private-groups.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>3.6. User Private Groups</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="Chapter 3. Managing Users
and Groups" /><link rel="prev"
href="s1-users-groups-standard-groups.html" title="3.5. Standard
Groups" /><link rel="next"
href="s1-users-groups-shadow-utilities.html" title="3.7. Shadow
Passwords" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-standard-groups.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n"
href="s1-users-groups-shadow-utilities.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-users-groups-private-groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-private-groups">3.6. User Private
Groups</h2></div></div></div><a id="id418782"
class="indexterm"></a><a id="id418794"
class="indexterm"></a><a id="id418806"
class="indexterm"></a><a id="id418824"
class="indexterm"></a><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em>
(<em class="firstterm">UPG</em>) scheme, which makes UNIX groups
easier to manage. A UPG is created whenever a new user is added to the system. It has the
same name as the user for which it was created and that user is the only member of the
UPG.
+ </div><div class="para">
+ UPGs make it safe to set default permissions for a newly created file or directory,
allowing both the user and <span class="emphasis"><em>the group of
that user</em></span> to make modifications to the file or directory.
+ </div><div class="para">
+ The setting which determines what permissions are applied to a newly created file or
directory is called a <em class="firstterm">umask</em> and is
configured in the <code class="filename">/etc/bashrc</code> file.
Traditionally on UNIX systems, the <code
class="command">umask</code> is set to <code
class="command">022</code>, which allows only the user who created the
file or directory to make modifications. Under this scheme, all other users, <span
class="emphasis"><em>including members of the creator's
group</em></span>, are not allowed to make any modifications. However, under
the UPG scheme, this "group protection" is not necessary since every user has
their own private group.
+ </div><div class="section"
id="s2-users-groups-rationale"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-users-groups-rationale">3.6.1. Group
Directories</h3></div></div></div><a id="id418898"
class="indexterm"></a><a id="id418910"
class="indexterm"></a><div class="para">
+ System administrators usually like to create a group for each major project and
assign people to the group when they need to access that project's files. With this
traditional scheme, file managing is difficult; when someone creates a file, it is
associated with the primary group to which they belong. When a single person works on
multiple projects, it becomes difficult to associate the right files with the right group.
However, with the UPG scheme, groups are automatically assigned to files created within a
directory with the <em class="firstterm">setgid</em> bit set. The
setgid bit makes managing group projects that share a common directory very simple because
any files a user creates within the directory are owned by the group which owns the
directory.
+ </div><div class="para">
+ For example, a group of people need to work on files in the <code
class="filename">/opt/myproject/</code> directory. Some people are
trusted to modify the contents of this directory, but not everyone.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ As <code class="systemitem">root</code>, create the <code
class="filename">/opt/myproject/</code> directory by typing the
following at a shell prompt:
+ </div><pre class="screen"><code
class="command">mkdir
/opt/myproject</code></pre></li><li class="step"><div
class="para">
+ Add the <code class="systemitem">myproject</code> group to
the system:
+ </div><pre class="screen"><code
class="command">groupadd myproject</code></pre></li><li
class="step"><div class="para">
+ Associate the contents of the <code
class="filename">/opt/myproject/</code> directory with the <code
class="systemitem">myproject</code> group:
+ </div><pre class="screen"><code
class="command">chown root:myproject
/opt/myproject</code></pre></li><li class="step"><div
class="para">
+ Allow users to create files within the directory, and set the setgid bit:
+ </div><pre class="screen"><code
class="command">chmod 2775
/opt/myproject</code></pre></li></ol></div><div
class="para">
+ At this point, all members of the <code
class="systemitem">myproject</code> group can create and edit files in
the <code class="filename">/opt/myproject/</code> directory without
the administrator having to change file permissions every time users write new files. To
verify that the permissions have been set correctly, run the following command:
+ </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><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-users-groups-standard-groups.html"><strong>Prev</strong>3.5. Standard
Groups</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-groups-shadow-utilities.html"><strong>Next</strong>3.7. Shadow
Passwords</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-shadow-utilities.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-shadow-utilities.html
new file mode 100644
index 0000000..9ccfc65
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-shadow-utilities.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>3.7. Shadow Passwords</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="Chapter 3. Managing Users
and Groups" /><link rel="prev"
href="s1-users-groups-private-groups.html" title="3.6. User Private
Groups" /><link rel="next"
href="s1-users-groups-additional-resources.html" title="3.8. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-users-groups-private-groups.html"><strong>
Prev</strong></a></li><li class="next"><a
accesskey="n"
href="s1-users-groups-additional-resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-users-groups-shadow-utilities"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-shadow-utilities">3.7. Shadow
Passwords</h2></div></div></div><a id="id419075"
class="indexterm"></a><a id="id419087"
class="indexterm"></a><div class="para">
+ In multiuser environments it is very important to use <em
class="firstterm">shadow passwords</em> (provided by the <code
class="filename">shadow-utils</code> package). Doing so enhances the
security of system authentication files. For this reason, the installation program enables
shadow passwords by default.
+ </div><div class="para">
+ The following list shows the advantages shadow passwords have over the traditional way
of storing passwords on UNIX-based systems:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Improves system security by moving encrypted password hashes from the world-readable
<code class="filename">/etc/passwd</code> file to <code
class="filename">/etc/shadow</code>, which is readable only by the
<code class="systemitem">root</code> user.
+ </div></li><li class="listitem"><div
class="para">
+ Stores information about password aging.
+ </div></li><li class="listitem"><div
class="para">
+ Allows the <code class="filename">/etc/login.defs</code> file
to enforce security policies.
+ </div></li></ul></div><div class="para">
+ Most utilities provided by the <code
class="filename">shadow-utils</code> package work properly whether or
not shadow passwords are enabled. However, since password aging information is stored
exclusively in the <code class="filename">/etc/shadow</code> file,
any commands which create or modify password aging information do not work.
+ </div><div class="para">
+ The following is a list of commands which do not work without first enabling shadow
passwords:
+ </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="command">usermod</code> <code
class="option">-e</code> or <code
class="option">-f</code> options
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">useradd</code> <code
class="option">-e</code> or <code
class="option">-f</code> options
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-users-groups-private-groups.html"><strong>Prev</strong>3.6. User
Private Groups</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-groups-additional-resources.html"><strong>Next</strong>3.8. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-standard-groups.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-standard-groups.html
new file mode 100644
index 0000000..ff7d4a8
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-standard-groups.html
@@ -0,0 +1,390 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Standard Groups</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="Chapter 3. Managing Users
and Groups" /><link rel="prev"
href="s1-users-groups-standard-users.html" title="3.4. Standard Users"
/><link rel="next" href="s1-users-groups-private-groups.html"
title="3.6. User Private Groups" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-users-groups-standard-users.html"><strong>Prev</strong
</a></li><li class="next"><a
accesskey="n"
href="s1-users-groups-private-groups.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-users-groups-standard-groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-standard-groups">3.5. Standard
Groups</h2></div></div></div><a id="id538220"
class="indexterm"></a><div class="para">
+ <a class="xref"
href="s1-users-groups-standard-groups.html#tb-users-groups-group-etc">Table 3.5,
“Standard Groups”</a> lists the standard groups configured by an <span
class="guilabel"><strong>Everything</strong></span>
installation. Groups are stored in the <code
class="filename">/etc/group</code> file.
+ </div><div class="table"
id="tb-users-groups-group-etc"><h6>Table 3.5. Standard
Groups</h6><div class="table-contents"><table
summary="Standard Groups" border="1"><colgroup><col
class="group" width="33%" /><col class="gid"
width="33%" /><col class="members" width="33%"
/></colgroup><thead><tr><th>
+ Group
+ </th><th>
+ GID
+ </th><th>
+ Members
+ </th></tr></thead><tbody><tr><td>
+ <code class="systemitem">root</code>
+ </td><td>
+ 0
+ </td><td>
+ <code class="systemitem">root</code>
+ </td></tr><tr><td>
+ <code class="systemitem">bin</code>
+ </td><td>
+ 1
+ </td><td>
+ <code class="systemitem">root</code>, <code
class="systemitem">bin</code>, <code
class="systemitem">daemon</code>
+ </td></tr><tr><td>
+ <code class="systemitem">daemon</code>
+ </td><td>
+ 2
+ </td><td>
+ <code class="systemitem">root</code>, <code
class="systemitem">bin</code>, <code
class="systemitem">daemon</code>
+ </td></tr><tr><td>
+ <code class="systemitem">sys</code>
+ </td><td>
+ 3
+ </td><td>
+ <code class="systemitem">root</code>, <code
class="systemitem">bin</code>, <code
class="systemitem">adm</code>
+ </td></tr><tr><td>
+ <code class="systemitem">adm</code>
+ </td><td>
+ 4
+ </td><td>
+ <code class="systemitem">root</code>, <code
class="systemitem">adm</code>, <code
class="systemitem">daemon</code>
+ </td></tr><tr><td>
+ <code class="systemitem">tty</code>
+ </td><td>
+ 5
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">disk</code>
+ </td><td>
+ 6
+ </td><td>
+ <code class="systemitem">root</code>
+ </td></tr><tr><td>
+ <code class="systemitem">lp</code>
+ </td><td>
+ 7
+ </td><td>
+ <code class="systemitem">daemon</code>, <code
class="systemitem">lp</code>
+ </td></tr><tr><td>
+ <code class="systemitem">mem</code>
+ </td><td>
+ 8
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">kmem</code>
+ </td><td>
+ 9
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">wheel</code>
+ </td><td>
+ 10
+ </td><td>
+ <code class="systemitem">root</code>
+ </td></tr><tr><td>
+ <code class="systemitem">mail</code>
+ </td><td>
+ 12
+ </td><td>
+ <code class="systemitem">mail</code>, <code
class="systemitem">postfix</code>
+ </td></tr><tr><td>
+ <code class="systemitem">uucp</code>
+ </td><td>
+ 14
+ </td><td>
+ <code class="systemitem">uucp</code>
+ </td></tr><tr><td>
+ <code class="systemitem">man</code>
+ </td><td>
+ 15
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">games</code>
+ </td><td>
+ 20
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">gopher</code>
+ </td><td>
+ 30
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">video</code>
+ </td><td>
+ 39
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dip</code>
+ </td><td>
+ 40
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">ftp</code>
+ </td><td>
+ 50
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">lock</code>
+ </td><td>
+ 54
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">audio</code>
+ </td><td>
+ 63
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">nobody</code>
+ </td><td>
+ 99
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">users</code>
+ </td><td>
+ 100
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dbus</code>
+ </td><td>
+ 81
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">usbmuxd</code>
+ </td><td>
+ 113
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">utmp</code>
+ </td><td>
+ 22
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">utempter</code>
+ </td><td>
+ 35
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">avahi-autoipd</code>
+ </td><td>
+ 170
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">floppy</code>
+ </td><td>
+ 19
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">vcsa</code>
+ </td><td>
+ 69
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">rpc</code>
+ </td><td>
+ 32
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">rtkit</code>
+ </td><td>
+ 499
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">abrt</code>
+ </td><td>
+ 498
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">nscd</code>
+ </td><td>
+ 28
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">desktop_admin_r</code>
+ </td><td>
+ 497
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">desktop_user_r</code>
+ </td><td>
+ 496
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">cdrom</code>
+ </td><td>
+ 11
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">tape</code>
+ </td><td>
+ 33
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dialout</code>
+ </td><td>
+ 18
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">haldaemon</code>
+ </td><td>
+ 68
+ </td><td>
+ <code class="systemitem">haldaemon</code>
+ </td></tr><tr><td>
+ <code class="systemitem">apache</code>
+ </td><td>
+ 48
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">ldap</code>
+ </td><td>
+ 55
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">saslauth</code>
+ </td><td>
+ 495
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">postdrop</code>
+ </td><td>
+ 90
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">postfix</code>
+ </td><td>
+ 89
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">avahi</code>
+ </td><td>
+ 70
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">ntp</code>
+ </td><td>
+ 38
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">rpcuser</code>
+ </td><td>
+ 29
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">nfsnobody</code>
+ </td><td>
+ 65534
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">pulse</code>
+ </td><td>
+ 494
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">pulse-access</code>
+ </td><td>
+ 493
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">fuse</code>
+ </td><td>
+ 492
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">gdm</code>
+ </td><td>
+ 42
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">stapdev</code>
+ </td><td>
+ 491
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">stapusr</code>
+ </td><td>
+ 490
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">sshd</code>
+ </td><td>
+ 74
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">tcpdump</code>
+ </td><td>
+ 72
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">slocate</code>
+ </td><td>
+ 21
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dovecot</code>
+ </td><td>
+ 97
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">dovenull</code>
+ </td><td>
+ 489
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">mailnull</code>
+ </td><td>
+ 47
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">smmsp</code>
+ </td><td>
+ 51
+ </td><td>
+ —
+ </td></tr></tbody></table></div></div><br
class="table-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-users-groups-standard-users.html"><strong>Prev</strong>3.4. Standard
Users</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-groups-private-groups.html"><strong>Next</strong>3.6. User
Private Groups</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-standard-users.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-standard-users.html
new file mode 100644
index 0000000..c45234b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-groups-standard-users.html
@@ -0,0 +1,1502 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Standard Users</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="Chapter 3. Managing Users
and Groups" /><link rel="prev"
href="s2-redhat-config-users-process.html" title="3.3.2. Explaining the
Process" /><link rel="next"
href="s1-users-groups-standard-groups.html" title="3.5. Standard
Groups" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-redhat-config-users-process.html"><strong>Prev<
/strong></a></li><li class="next"><a
accesskey="n"
href="s1-users-groups-standard-groups.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-users-groups-standard-users"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-groups-standard-users">3.4. Standard
Users</h2></div></div></div><a id="id615043"
class="indexterm"></a><a id="id615055"
class="indexterm"></a><div class="para">
+ <a class="xref"
href="s1-users-groups-standard-users.html#tb-users-groups-group-use">Table 3.4,
“Standard Users”</a> lists the standard users configured in the <code
class="filename">/etc/passwd</code> file by an <span
class="guilabel"><strong>Everything</strong></span>
installation. The group ID (GID) in this table is the <span
class="emphasis"><em>primary group</em></span> for the
user. See <a class="xref"
href="s1-users-groups-standard-groups.html">Section 3.5, “Standard
Groups”</a> for a listing of standard groups.
+ </div><div class="table"
id="tb-users-groups-group-use"><h6>Table 3.4. Standard
Users</h6><div class="table-contents"><table
summary="Standard Users" border="1"><colgroup><col
class="col1" width="17%" /><col class="col2"
width="17%" /><col class="col3" width="17%"
/><col class="col4" width="17%" /><col
class="col5" width="17%" /><col class="col6"
width="17%" /></colgroup><thead><tr><th>
+ User
+ </th><th>
+ UID
+ </th><th>
+ GID
+ </th><th>
+ Home Directory
+ </th><th>
+ Shell
+ </th><th>
+ Packages
+ </th></tr></thead><tbody><tr><td>
+ <code class="systemitem">root</code>
+ </td><td>
+ 0
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/root</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">bin</code>
+ </td><td>
+ 1
+ </td><td>
+ 1
+ </td><td>
+ <code class="filename">/bin</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">daemon</code>
+ </td><td>
+ 2
+ </td><td>
+ 2
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">sys</code>
+ </td><td>
+ —
+ </td><td>
+ 3
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">adm</code>
+ </td><td>
+ 3
+ </td><td>
+ 4
+ </td><td>
+ <code class="filename">/var/adm</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">tty</code>
+ </td><td>
+ —
+ </td><td>
+ 5
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">disk</code>
+ </td><td>
+ —
+ </td><td>
+ 6
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">lp</code>
+ </td><td>
+ 4
+ </td><td>
+ 7
+ </td><td>
+ <code class="filename">/var/spool/lpd</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mem</code>
+ </td><td>
+ —
+ </td><td>
+ 8
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">kmem</code>
+ </td><td>
+ —
+ </td><td>
+ 9
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">wheel</code>
+ </td><td>
+ —
+ </td><td>
+ 10
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">cdrom</code>
+ </td><td>
+ —
+ </td><td>
+ 11
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">udev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">sync</code>
+ </td><td>
+ 5
+ </td><td>
+ (0)
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/bin/sync</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">shutdown</code>
+ </td><td>
+ 6
+ </td><td>
+ (0)
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/shutdown</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">halt</code>
+ </td><td>
+ 7
+ </td><td>
+ (0)
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/halt</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mail</code>
+ </td><td>
+ 8
+ </td><td>
+ 12
+ </td><td>
+ <code class="filename">/var/spool/mail</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">news</code>
+ </td><td>
+ 9
+ </td><td>
+ 13
+ </td><td>
+ <code class="filename">/var/spool/news</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">uucp</code>
+ </td><td>
+ 10
+ </td><td>
+ 14
+ </td><td>
+ <code class="filename">/var/spool/uucp</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">operator</code>
+ </td><td>
+ 11
+ </td><td>
+ (0)
+ </td><td>
+ <code class="filename">/root</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">games</code>
+ </td><td>
+ 12
+ </td><td>
+ (100)
+ </td><td>
+ <code class="filename">/usr/games</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">gopher</code>
+ </td><td>
+ 13
+ </td><td>
+ 30
+ </td><td>
+ <code class="filename">/usr/lib/gopher-data</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ftp</code>
+ </td><td>
+ 14
+ </td><td>
+ 50
+ </td><td>
+ <code class="filename">/var/ftp</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">man</code>
+ </td><td>
+ —
+ </td><td>
+ 15
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">oprofile</code>
+ </td><td>
+ 16
+ </td><td>
+ 16
+ </td><td>
+ <code class="filename">/home/oprofile</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">oprofile</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pkiuser</code>
+ </td><td>
+ 17
+ </td><td>
+ 17
+ </td><td>
+ <code class="filename">/usr/share/pki</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">pki-ca</span>, <span
class="package">rhpki-ca</span>
+ </td></tr><tr><td>
+ <code class="systemitem">dialout</code>
+ </td><td>
+ —
+ </td><td>
+ 18
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">udev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">floppy</code>
+ </td><td>
+ —
+ </td><td>
+ 19
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">dev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">games</code>
+ </td><td>
+ —
+ </td><td>
+ 20
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">slocate</code>
+ </td><td>
+ —
+ </td><td>
+ 21
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">slocate</span>
+ </td></tr><tr><td>
+ <code class="systemitem">utmp</code>
+ </td><td>
+ —
+ </td><td>
+ 22
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">initscripts</span>, <span
class="package">libutempter</span>
+ </td></tr><tr><td>
+ <code class="systemitem">squid</code>
+ </td><td>
+ 23
+ </td><td>
+ 23
+ </td><td>
+ <code class="filename">/var/spool/squid</code>
+ </td><td>
+ <code class="filename">/dev/null</code>
+ </td><td>
+ <span class="package">squid</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pvm</code>
+ </td><td>
+ 24
+ </td><td>
+ 24
+ </td><td>
+ <code class="filename">/usr/share/pvm3</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">pvm</span>
+ </td></tr><tr><td>
+ <code class="systemitem">named</code>
+ </td><td>
+ 25
+ </td><td>
+ 25
+ </td><td>
+ <code class="filename">/var/named</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">bind</span>
+ </td></tr><tr><td>
+ <code class="systemitem">postgres</code>
+ </td><td>
+ 26
+ </td><td>
+ 26
+ </td><td>
+ <code class="filename">/var/lib/pgsql</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">postgresql-server</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mysql</code>
+ </td><td>
+ 27
+ </td><td>
+ 27
+ </td><td>
+ <code class="filename">/var/lib/mysql</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">mysql</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nscd</code>
+ </td><td>
+ 28
+ </td><td>
+ 28
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">nscd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">rpcuser</code>
+ </td><td>
+ 29
+ </td><td>
+ 29
+ </td><td>
+ <code class="filename">/var/lib/nfs</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">nfs-utils</span>
+ </td></tr><tr><td>
+ <code class="systemitem">console</code>
+ </td><td>
+ —
+ </td><td>
+ 31
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">dev</span>
+ </td></tr><tr><td>
+ <code class="systemitem">rpc</code>
+ </td><td>
+ 32
+ </td><td>
+ 32
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">portmap</span>
+ </td></tr><tr><td>
+ <code class="systemitem">amanda</code>
+ </td><td>
+ 33
+ </td><td>
+ (6)
+ </td><td>
+ <code class="filename">/var/lib/amanda</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">amanda</span>
+ </td></tr><tr><td>
+ <code class="systemitem">tape</code>
+ </td><td>
+ —
+ </td><td>
+ 33
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">udev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">netdump</code>
+ </td><td>
+ 34
+ </td><td>
+ 34
+ </td><td>
+ <code class="filename">/var/crash</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">netdump-client</span>, <span
class="package">netdump-server</span>
+ </td></tr><tr><td>
+ <code class="systemitem">utempter</code>
+ </td><td>
+ —
+ </td><td>
+ 35
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">libutempter</span>
+ </td></tr><tr><td>
+ <code class="systemitem">vdsm</code>
+ </td><td>
+ 36
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">kvm</span>, <span
class="package">vdsm</span>
+ </td></tr><tr><td>
+ <code class="systemitem">kvm</code>
+ </td><td>
+ —
+ </td><td>
+ 36
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">kvm</span>, <span
class="package">vdsm</span>, <span
class="package">libvirt</span>
+ </td></tr><tr><td>
+ <code class="systemitem">rpm</code>
+ </td><td>
+ 37
+ </td><td>
+ 37
+ </td><td>
+ <code class="filename">/var/lib/rpm</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">rpm</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ntp</code>
+ </td><td>
+ 38
+ </td><td>
+ 38
+ </td><td>
+ <code class="filename">/etc/ntp</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">ntp</span>
+ </td></tr><tr><td>
+ <code class="systemitem">video</code>
+ </td><td>
+ —
+ </td><td>
+ 39
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">dip</code>
+ </td><td>
+ —
+ </td><td>
+ 40
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mailman</code>
+ </td><td>
+ 41
+ </td><td>
+ 41
+ </td><td>
+ <code class="filename">/var/mailman</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">mailman</span>
+ </td></tr><tr><td>
+ <code class="systemitem">gdm</code>
+ </td><td>
+ 42
+ </td><td>
+ 42
+ </td><td>
+ <code class="filename">/var/gdm</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">gdm</span>
+ </td></tr><tr><td>
+ <code class="systemitem">xfs</code>
+ </td><td>
+ 43
+ </td><td>
+ 43
+ </td><td>
+ <code class="filename">/etc/X11/fs</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">XFree86-xfs</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pppusers</code>
+ </td><td>
+ —
+ </td><td>
+ 44
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">linuxconf</span>
+ </td></tr><tr><td>
+ <code class="systemitem">popusers</code>
+ </td><td>
+ —
+ </td><td>
+ 45
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">linuxconf</span>
+ </td></tr><tr><td>
+ <code class="systemitem">slipusers</code>
+ </td><td>
+ —
+ </td><td>
+ 46
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">linuxconf</span>
+ </td></tr><tr><td>
+ <code class="systemitem">mailnull</code>
+ </td><td>
+ 47
+ </td><td>
+ 47
+ </td><td>
+ <code class="filename">/var/spool/mqueue</code>
+ </td><td>
+ <code class="filename">/dev/null</code>
+ </td><td>
+ <span class="package">sendmail</span>
+ </td></tr><tr><td>
+ <code class="systemitem">apache</code>
+ </td><td>
+ 48
+ </td><td>
+ 48
+ </td><td>
+ <code class="filename">/var/www</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">apache</span>
+ </td></tr><tr><td>
+ <code class="systemitem">wnn</code>
+ </td><td>
+ 49
+ </td><td>
+ 49
+ </td><td>
+ <code class="filename">/home/wnn</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">FreeWnn</span>
+ </td></tr><tr><td>
+ <code class="systemitem">smmsp</code>
+ </td><td>
+ 51
+ </td><td>
+ 51
+ </td><td>
+ <code class="filename">/var/spool/mqueue</code>
+ </td><td>
+ <code class="filename">/dev/null</code>
+ </td><td>
+ <span class="package">sendmail</span>
+ </td></tr><tr><td>
+ <code class="systemitem">puppet</code>
+ </td><td>
+ 52
+ </td><td>
+ 52
+ </td><td>
+ <code class="filename">/var/lib/puppet</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">puppet</span>
+ </td></tr><tr><td>
+ <code class="systemitem">tomcat</code>
+ </td><td>
+ 53
+ </td><td>
+ 53
+ </td><td>
+ <code class="filename">/var/lib/tomcat</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">tomcat</span>
+ </td></tr><tr><td>
+ <code class="systemitem">lock</code>
+ </td><td>
+ —
+ </td><td>
+ 54
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">lockdev</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ldap</code>
+ </td><td>
+ 55
+ </td><td>
+ 55
+ </td><td>
+ <code class="filename">/var/lib/ldap</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">openldap-servers</span>
+ </td></tr><tr><td>
+ <code class="systemitem">frontpage</code>
+ </td><td>
+ 56
+ </td><td>
+ 56
+ </td><td>
+ <code class="filename">/var/www</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">mod_frontpage</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nut</code>
+ </td><td>
+ 57
+ </td><td>
+ 57
+ </td><td>
+ <code class="filename">/var/lib/ups</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">nut</span>
+ </td></tr><tr><td>
+ <code class="systemitem">beagleindex</code>
+ </td><td>
+ 58
+ </td><td>
+ 58
+ </td><td>
+ <code class="filename">/var/cache/beagle</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">beagle</span>
+ </td></tr><tr><td>
+ <code class="systemitem">tss</code>
+ </td><td>
+ 59
+ </td><td>
+ 59
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">trousers</span>
+ </td></tr><tr><td>
+ <code class="systemitem">piranha</code>
+ </td><td>
+ 60
+ </td><td>
+ 60
+ </td><td>
+ <code class="filename">/etc/sysconfig/ha</code>
+ </td><td>
+ <code class="filename">/dev/null</code>
+ </td><td>
+ <span class="package">piranha</span>
+ </td></tr><tr><td>
+ <code class="systemitem">prelude-manager</code>
+ </td><td>
+ 61
+ </td><td>
+ 61
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">prelude-manager</span>
+ </td></tr><tr><td>
+ <code class="systemitem">snortd</code>
+ </td><td>
+ 62
+ </td><td>
+ 62
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">snortd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">audio</code>
+ </td><td>
+ —
+ </td><td>
+ 63
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">condor</code>
+ </td><td>
+ 64
+ </td><td>
+ 64
+ </td><td>
+ <code class="filename">/var/lib/condor</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">condord</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nslcd</code>
+ </td><td>
+ 65
+ </td><td>
+ (55)
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">nslcd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">wine</code>
+ </td><td>
+ —
+ </td><td>
+ 66
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">wine</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pegasus</code>
+ </td><td>
+ 66
+ </td><td>
+ 65
+ </td><td>
+ <code class="filename">/var/lib/Pegasus</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">tog-pegasus</span>
+ </td></tr><tr><td>
+ <code class="systemitem">webalizer</code>
+ </td><td>
+ 67
+ </td><td>
+ 67
+ </td><td>
+ <code class="filename">/var/www/html/usage</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">webalizer</span>
+ </td></tr><tr><td>
+ <code class="systemitem">haldaemon</code>
+ </td><td>
+ 68
+ </td><td>
+ 68
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">hal</span>
+ </td></tr><tr><td>
+ <code class="systemitem">vcsa</code>
+ </td><td>
+ 69
+ </td><td>
+ 69
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">dev</span>, <span
class="package">MAKEDEV</span>
+ </td></tr><tr><td>
+ <code class="systemitem">avahi</code>
+ </td><td>
+ 70
+ </td><td>
+ 70
+ </td><td>
+ <code class="filename">/var/run/avahi-daemon</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">avahi</span>
+ </td></tr><tr><td>
+ <code class="systemitem">realtime</code>
+ </td><td>
+ —
+ </td><td>
+ 71
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ —
+ </td></tr><tr><td>
+ <code class="systemitem">tcpdump</code>
+ </td><td>
+ 72
+ </td><td>
+ 72
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">tcpdump</span>
+ </td></tr><tr><td>
+ <code class="systemitem">privoxy</code>
+ </td><td>
+ 73
+ </td><td>
+ 73
+ </td><td>
+ <code class="filename">/etc/privoxy</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">privoxy</span>
+ </td></tr><tr><td>
+ <code class="systemitem">sshd</code>
+ </td><td>
+ 74
+ </td><td>
+ 74
+ </td><td>
+ <code class="filename">/var/empty/sshd</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">openssh-server</span>
+ </td></tr><tr><td>
+ <code class="systemitem">radvd</code>
+ </td><td>
+ 75
+ </td><td>
+ 75
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">radvd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">cyrus</code>
+ </td><td>
+ 76
+ </td><td>
+ (12)
+ </td><td>
+ <code class="filename">/var/imap</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">cyrus-imapd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">saslauth</code>
+ </td><td>
+ —
+ </td><td>
+ 76
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">cyrus-imapd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">arpwatch</code>
+ </td><td>
+ 77
+ </td><td>
+ 77
+ </td><td>
+ <code class="filename">/var/lib/arpwatch</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">arpwatch</span>
+ </td></tr><tr><td>
+ <code class="systemitem">fax</code>
+ </td><td>
+ 78
+ </td><td>
+ 78
+ </td><td>
+ <code class="filename">/var/spool/fax</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">mgetty</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nocpulse</code>
+ </td><td>
+ 79
+ </td><td>
+ 79
+ </td><td>
+ <code class="filename">/etc/sysconfig/nocpulse</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">nocpulse</span>
+ </td></tr><tr><td>
+ <code class="systemitem">desktop</code>
+ </td><td>
+ 80
+ </td><td>
+ 80
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">desktop-file-utils</span>
+ </td></tr><tr><td>
+ <code class="systemitem">dbus</code>
+ </td><td>
+ 81
+ </td><td>
+ 81
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">dbus</span>
+ </td></tr><tr><td>
+ <code class="systemitem">jonas</code>
+ </td><td>
+ 82
+ </td><td>
+ 82
+ </td><td>
+ <code class="filename">/var/lib/jonas</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">jonas</span>
+ </td></tr><tr><td>
+ <code class="systemitem">clamav</code>
+ </td><td>
+ 83
+ </td><td>
+ 83
+ </td><td>
+ <code class="filename">/tmp</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">clamav</span>
+ </td></tr><tr><td>
+ <code class="systemitem">screen</code>
+ </td><td>
+ —
+ </td><td>
+ 84
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">screen</span>
+ </td></tr><tr><td>
+ <code class="systemitem">quaggavt</code>
+ </td><td>
+ —
+ </td><td>
+ 85
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">quagga</span>
+ </td></tr><tr><td>
+ <code class="systemitem">sabayon</code>
+ </td><td>
+ 86
+ </td><td>
+ 86
+ </td><td>
+ —
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">sabayon</span>
+ </td></tr><tr><td>
+ <code class="systemitem">polkituser</code>
+ </td><td>
+ 87
+ </td><td>
+ 87
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">PolicyKit</span>
+ </td></tr><tr><td>
+ <code class="systemitem">wbpriv</code>
+ </td><td>
+ —
+ </td><td>
+ 88
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">samba-common</span>
+ </td></tr><tr><td>
+ <code class="systemitem">postfix</code>
+ </td><td>
+ 89
+ </td><td>
+ 89
+ </td><td>
+ <code class="filename">/var/spool/postfix</code>
+ </td><td>
+ <code class="filename">/bin/true</code>
+ </td><td>
+ <span class="package">postfix</span>
+ </td></tr><tr><td>
+ <code class="systemitem">postdrop</code>
+ </td><td>
+ —
+ </td><td>
+ 90
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">postfix</span>
+ </td></tr><tr><td>
+ <code class="systemitem">majordomo</code>
+ </td><td>
+ 91
+ </td><td>
+ 91
+ </td><td>
+ <code class="filename">/usr/lib/majordomo</code>
+ </td><td>
+ <code class="filename">/bin/bash</code>
+ </td><td>
+ <span class="package">majordomo</span>
+ </td></tr><tr><td>
+ <code class="systemitem">quagga</code>
+ </td><td>
+ 92
+ </td><td>
+ 92
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">quagga</span>
+ </td></tr><tr><td>
+ <code class="systemitem">exim</code>
+ </td><td>
+ 93
+ </td><td>
+ 93
+ </td><td>
+ <code class="filename">/var/spool/exim</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">exim</span>
+ </td></tr><tr><td>
+ <code class="systemitem">distcache</code>
+ </td><td>
+ 94
+ </td><td>
+ 94
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">distcache</span>
+ </td></tr><tr><td>
+ <code class="systemitem">radiusd</code>
+ </td><td>
+ 95
+ </td><td>
+ 95
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/bin/false</code>
+ </td><td>
+ <span class="package">freeradius</span>
+ </td></tr><tr><td>
+ <code class="systemitem">hsqldb</code>
+ </td><td>
+ 96
+ </td><td>
+ 96
+ </td><td>
+ <code class="filename">/var/lib/hsqldb</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">hsqldb</span>
+ </td></tr><tr><td>
+ <code class="systemitem">dovecot</code>
+ </td><td>
+ 97
+ </td><td>
+ 97
+ </td><td>
+ <code class="filename">/usr/libexec/dovecot</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">dovecot</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ident</code>
+ </td><td>
+ 98
+ </td><td>
+ 98
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">ident</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nobody</code>
+ </td><td>
+ 99
+ </td><td>
+ 99
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">users</code>
+ </td><td>
+ —
+ </td><td>
+ 100
+ </td><td>
+ —
+ </td><td>
+ —
+ </td><td>
+ <span class="package">setup</span>
+ </td></tr><tr><td>
+ <code class="systemitem">qemu</code>
+ </td><td>
+ 107
+ </td><td>
+ 107
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">libvirt</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ovirt</code>
+ </td><td>
+ 108
+ </td><td>
+ 108
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">libvirt</span>
+ </td></tr><tr><td>
+ <code class="systemitem">saned</code>
+ </td><td>
+ 111
+ </td><td>
+ 111
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">sane-backends</span>
+ </td></tr><tr><td>
+ <code class="systemitem">vhostmd</code>
+ </td><td>
+ 112
+ </td><td>
+ 112
+ </td><td>
+ <code class="filename">/usr/share/vhostmd</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">vhostmd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">usbmuxd</code>
+ </td><td>
+ 113
+ </td><td>
+ 113
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">usbmuxd</span>
+ </td></tr><tr><td>
+ <code class="systemitem">bacula</code>
+ </td><td>
+ 133
+ </td><td>
+ 133
+ </td><td>
+ <code class="filename">/var/spool/bacula</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">bacula</span>
+ </td></tr><tr><td>
+ <code class="systemitem">ricci</code>
+ </td><td>
+ 140
+ </td><td>
+ 140
+ </td><td>
+ <code class="filename">/var/lib/ricci</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">ricci</span>
+ </td></tr><tr><td>
+ <code class="systemitem">luci</code>
+ </td><td>
+ 141
+ </td><td>
+ 141
+ </td><td>
+ <code class="filename">/var/lib/luci</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">luci</span>
+ </td></tr><tr><td>
+ <code class="systemitem">stap-server</code>
+ </td><td>
+ 155
+ </td><td>
+ 155
+ </td><td>
+ <code class="filename">/var/lib/stap-server</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">systemtap</span>
+ </td></tr><tr><td>
+ <code class="systemitem">avahi-autoipd</code>
+ </td><td>
+ 170
+ </td><td>
+ 170
+ </td><td>
+ <code class="filename">/var/lib/avahi-autoipd</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">avahi</span>
+ </td></tr><tr><td>
+ <code class="systemitem">pulse</code>
+ </td><td>
+ 171
+ </td><td>
+ 171
+ </td><td>
+ <code class="filename">/var/run/pulse</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">pulseaudio</span>
+ </td></tr><tr><td>
+ <code class="systemitem">rtkit</code>
+ </td><td>
+ 172
+ </td><td>
+ 172
+ </td><td>
+ <code class="filename">/proc</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">rtkit</span>
+ </td></tr><tr><td>
+ <code class="systemitem">nfsnobody</code>
+ </td><td>
+ 65534<sup>[<a id="id538165" href="#ftn.id538165"
class="footnote">a</a>]</sup>
+ </td><td>
+ 65534
+ </td><td>
+ <code class="filename">/var/lib/nfs</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td><td>
+ <span class="package">nfs-utils</span>
+ </td></tr></tbody><tbody
class="footnotes"><tr><td colspan="6"><div
class="footnote"><div class="para"><sup>[<a
id="ftn.id538165" href="#id538165"
class="para">a</a>] </sup>
+ nfsnobdy is 4294967294 on 64-bit platforms
+ </div></div></td></tr></tbody></table></div></div><br
class="table-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-redhat-config-users-process.html"><strong>Prev</strong>3.3.2. Explaining
the Process</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-groups-standard-groups.html"><strong>Next</strong>3.5. Standard
Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-tools.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-tools.html
new file mode 100644
index 0000000..1f18a27
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s1-users-tools.html
@@ -0,0 +1,181 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. User and Group Management Tools</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Managing_Users_and_Groups.html" title="Chapter 3. Managing Users
and Groups" /><link rel="prev"
href="s2-redhat-config-users-group-properties.html" title="3.2.3. Modifying
Group Properties" /><link rel="next"
href="s2-redhat-config-users-process.html" title="3.3.2. Explaining the
Process" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-
properties.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-redhat-config-users-process.html"><strong>Next</strong></a></li></ul><div
class="section" id="s1-users-tools"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="s1-users-tools">3.3. User and Group Management
Tools</h2></div></div></div><a id="id537078"
class="indexterm"></a><a id="id537095"
class="indexterm"></a><a id="id537113"
class="indexterm"></a><a id="id537130"
class="indexterm"></a><div class="para">
+ Managing users and groups can be tiresome; this is why Fedora provides tools and
conventions to make this task easier to manage.
+ </div><div class="para">
+ The easiest way to manage users and groups is through the graphical application,
<span class="application"><strong>User
Manager</strong></span> (<code
class="command">system-config-users</code>). For more information on
<span class="application"><strong>User
Manager</strong></span>, refer to <a class="xref"
href="s1-users-configui.html">Section 3.2, “User Manager Tool”</a>.
+ </div><div class="para">
+ The following command line tools can also be used to manage users and groups:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">useradd</code>, <code
class="command">usermod</code>, and <code
class="command">userdel</code> — Industry-standard methods of adding,
deleting and modifying user accounts
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">groupadd</code>, <code
class="command">groupmod</code>, and <code
class="command">groupdel</code> — Industry-standard methods of adding,
deleting, and modifying user groups
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">gpasswd</code> — Industry-standard
method of administering the <code class="filename">/etc/group</code>
file
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pwck</code>, <code
class="command">grpck</code> — Tools used for the verification of the
password, group, and associated shadow files
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pwconv</code>, <code
class="command">pwunconv</code> — Tools used for the conversion of
passwords to shadow passwords and back to standard passwords
+ </div></li></ul></div><div class="section"
id="s2-users-cmd-line"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-users-cmd-line">3.3.1. Command Line
Configuration</h3></div></div></div><a id="id537275"
class="indexterm"></a><a id="id537287"
class="indexterm"></a><a id="id537301"
class="indexterm"></a><div class="para">
+ If you prefer command line tools or do not have the X Window System installed, use
following to configure users and groups.
+ </div><h4 id="id537318">Adding a User</h4><div
class="para">
+ To add a user to the system:
+ </div><a id="id537326"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Issue the <code class="command">useradd</code> command to
create a locked user account:
+ </div><pre class="screen"><code
class="command">useradd</code> <em
class="replaceable"><code>username</code></em></pre></li><li
class="step"><div class="para">
+ <a id="id537372" class="indexterm"></a>
+ Unlock the account by issuing the <code
class="command">passwd</code> command to assign a password and set
password aging guidelines:
+ </div><pre class="screen"><code
class="command">passwd</code> <em
class="replaceable"><code>username</code></em></pre></li></ol></div><div
class="para">
+ Command line options for <code class="command">useradd</code>
are detailed in <a class="xref"
href="s1-users-tools.html#table-useradd-options">Table 3.1, “<code
class="command">useradd</code> Command Line Options”</a>.
+ </div><div class="table"
id="table-useradd-options"><h6>Table 3.1. <code
class="command">useradd</code> Command Line Options</h6><div
class="table-contents"><table summary="useradd Command Line
Options" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-c</code> '<em
class="replaceable"><code>comment</code></em>'
+ </td><td>
+ <em
class="replaceable"><code>comment</code></em> can be
replaced with any string. This option is generally used to specify the full name of a
user.
+ </td></tr><tr><td>
+ <code class="option">-d</code> <em
class="replaceable"><code>home_directory</code></em>
+ </td><td>
+ Home directory to be used instead of default <code
class="filename">/home/<em
class="replaceable"><code>username</code></em>/</code>.
+ </td></tr><tr><td>
+ <code class="option">-e</code> <em
class="replaceable"><code>date</code></em>
+ </td><td>
+ Date for the account to be disabled in the format YYYY-MM-DD.
+ </td></tr><tr><td>
+ <code class="option">-f</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Number of days after the password expires until the account is disabled. If
<code class="literal">0</code> is specified, the account is disabled
immediately after the password expires. If <code
class="literal">-1</code> is specified, the account is not be disabled
after the password expires.
+ </td></tr><tr><td>
+ <code class="option">-g</code> <em
class="replaceable"><code>group_name</code></em>
+ </td><td>
+ Group name or group number for the user's default group. The group must exist
prior to being specified here.
+ </td></tr><tr><td>
+ <code class="option">-G</code> <em
class="replaceable"><code>group_list</code></em>
+ </td><td>
+ List of additional (other than default) group names or group numbers, separated
by commas, of which the user is a member. The groups must exist prior to being specified
here.
+ </td></tr><tr><td>
+ <code class="option">-m</code>
+ </td><td>
+ Create the home directory if it does not exist.
+ </td></tr><tr><td>
+ <code class="option">-M</code>
+ </td><td>
+ Do not create the home directory.
+ </td></tr><tr><td>
+ <code class="option">-N</code>
+ </td><td>
+ Do not create a user private group for the user.
+ </td></tr><tr><td>
+ <code class="option">-p</code> <em
class="replaceable"><code>password</code></em>
+ </td><td>
+ The password encrypted with <code
class="command">crypt</code>.
+ </td></tr><tr><td>
+ <code class="option">-r</code>
+ </td><td>
+ Create a system account with a UID less than 500 and without a home directory.
+ </td></tr><tr><td>
+ <code class="option">-s</code>
+ </td><td>
+ User's login shell, which defaults to <code
class="command">/bin/bash</code>.
+ </td></tr><tr><td>
+ <code class="option">-u</code> <em
class="replaceable"><code>uid</code></em>
+ </td><td>
+ User ID for the user, which must be unique and greater than 499.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><h4 id="id619968">Adding a
Group</h4><a id="id619972"
class="indexterm"></a><a id="id619985"
class="indexterm"></a><div class="para">
+ To add a group to the system, use the command <code
class="command">groupadd</code>:
+ </div><pre class="screen"><code
class="command">groupadd</code> <em
class="replaceable"><code>group_name</code></em></pre><div
class="para">
+ Command line options for <code class="command">groupadd</code>
are detailed in <a class="xref"
href="s1-users-tools.html#table-groupadd-options">Table 3.2, “<code
class="command">groupadd</code> Command Line Options”</a>.
+ </div><div class="table"
id="table-groupadd-options"><h6>Table 3.2. <code
class="command">groupadd</code> Command Line Options</h6><div
class="table-contents"><table summary="groupadd Command Line
Options" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-f</code>, <code
class="option">--force</code>
+ </td><td>
+ When used with <code class="option">-g</code> <em
class="replaceable"><code>gid</code></em> and <em
class="replaceable"><code>gid</code></em> already exists,
<code class="command">groupadd</code> will choose another unique
<em class="replaceable"><code>gid</code></em> for the
group.
+ </td></tr><tr><td>
+ <code class="option">-g</code> <em
class="replaceable"><code>gid</code></em>
+ </td><td>
+ Group ID for the group, which must be unique and greater than 499.
+ </td></tr><tr><td>
+ <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>
+ Override <code class="filename">/etc/login.defs</code>
defaults.
+ </td></tr><tr><td>
+ <code class="option">-o</code>, <code
class="option">--non-unique</code>
+ </td><td>
+ Allow to create groups with duplicate.
+ </td></tr><tr><td>
+ <code class="option">-p</code>, <code
class="option">--password</code> <em
class="replaceable"><code>password</code></em>
+ </td><td>
+ Use this encrypted password for the new group.
+ </td></tr><tr><td>
+ <code class="option">-r</code>
+ </td><td>
+ Create a system group with a GID less than 500.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><h4 id="id620239">Password
Aging</h4><a id="id620243"
class="indexterm"></a><a id="id620255"
class="indexterm"></a><a id="id620267"
class="indexterm"></a><a id="id620275"
class="indexterm"></a><a id="id620290"
class="indexterm"></a><div class="para">
+ For security reasons, it is advisable to require users to change their passwords
periodically. This can be done when adding or editing a user on the <span
class="guilabel"><strong>Password Info</strong></span> tab
of the <span class="application"><strong>User
Manager</strong></span>.
+ </div><div class="para">
+ To configure password expiration for a user from a shell prompt, use the <code
class="command">chage</code> command with an option from <a
class="xref"
href="s1-users-tools.html#table-chage-options">Table 3.3, “<code
class="command">chage</code> Command Line Options”</a>, followed
by the username.
+ </div><div class="important"><div
class="admonition_header"><h2>Shadow passwords must be enabled to use
chage</h2></div><div class="admonition"><div
class="para">
+ Shadow passwords must be enabled to use the <code
class="command">chage</code> command. For more information, see <a
class="xref"
href="s1-users-groups-shadow-utilities.html">Section 3.7, “Shadow
Passwords”</a>.
+ </div></div></div><div class="table"
id="table-chage-options"><h6>Table 3.3. <code
class="command">chage</code> Command Line Options</h6><div
class="table-contents"><table summary="chage Command Line
Options" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-d</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specifies the number of days since January 1, 1970 the password was changed.
+ </td></tr><tr><td>
+ <code class="option">-E</code> <em
class="replaceable"><code>date</code></em>
+ </td><td>
+ Specifies the date on which the account is locked, in the format YYYY-MM-DD.
Instead of the date, the number of days since January 1, 1970 can also be used.
+ </td></tr><tr><td>
+ <code class="option">-I</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specifies the number of inactive days after the password expiration before
locking the account. If the value is <code class="literal">0</code>,
the account is not locked after the password expires.
+ </td></tr><tr><td>
+ <code class="option">-l</code>
+ </td><td>
+ Lists current account aging settings.
+ </td></tr><tr><td>
+ <code class="option">-m</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specify the minimum number of days after which the user must change passwords. If
the value is <code class="literal">0</code>, the password does not
expire.
+ </td></tr><tr><td>
+ <code class="option">-M</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specify the maximum number of days for which the password is valid. When the
number of days specified by this option plus the number of days specified with the
<code class="option">-d</code> option is less than the current day,
the user must change passwords before using the account.
+ </td></tr><tr><td>
+ <code class="option">-W</code> <em
class="replaceable"><code>days</code></em>
+ </td><td>
+ Specifies the number of days before the password expiration date to warn the
user.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="note"><div
class="admonition_header"><h2>chage
interactivity</h2></div><div class="admonition"><div
class="para">
+ If the <code class="command">chage</code> command is followed
directly by a username (with no options), it displays the current password aging values
and allows them to be changed interactively.
+ </div></div></div><div class="para">
+ You can configure a password to expire the first time a user logs in. This forces
users to change passwords immediately.
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ <span class="emphasis"><em>Set up an initial
password</em></span> — There are two common approaches to this step: the
administrator can assign a default password, or he can use a null password.
+ </div><div class="para">
+ To assign a default password, type the following at a shell prompt:
+ </div><pre class="screen"><code
class="command">passwd</code> <em
class="replaceable"><code>username</code></em></pre><div
class="para">
+ To assign a null password instead, use the following command:
+ </div><pre class="screen"><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>Avoid using null passwords whenever
possible</h2></div><div class="admonition"><div
class="para">
+ Using a null password, while convenient, is a highly insecure practice, as any
third party can log in first and access the system using the insecure username. Always
make sure that the user is ready to log in before unlocking an account with a null
password.
+ </div></div></div></li><li
class="step"><div class="para">
+ <span class="emphasis"><em>Force immediate password
expiration</em></span> — Type the following command:
+ </div><pre class="screen"><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">
+ This command sets the value for the date the password was last changed to the epoch
(January 1, 1970). This value forces immediate password expiration no matter what password
aging policy, if any, is in place.
+ </div></li></ol></div><div class="para">
+ Upon the initial log in, the user is now prompted for a new password.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-redhat-config-users-group-properties.html"><strong>Prev</strong>3.2.3. Modifying
Group Properties</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-redhat-config-users-process.html"><strong>Next</strong>3.3.2. Explaining
the Process</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.html
new file mode 100644
index 0000000..a4c1145
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.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>18.2.5. Controlling Access to At and 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-autotasks-at-batch.html" title="18.2. At and Batch"
/><link rel="prev" href="s2-autotasks-commandline-options.html"
title="18.2.4. Additional Command Line Options" /><link
rel="next" href="s2-autotasks-at-batch-service.html"
title="18.2.6. Starting and Stopping the 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="s2-autotasks-commandline-options.html"><stron
g>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="s2-autotasks-at-batch-service.html"><strong>Next</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"
id="s2-autotasks-at-batch-controlling-access">18.2.5. Controlling Access to
At and 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>Prev</strong>18.2.4. Additional
Command Line Options</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-at-batch-service.html"><strong>Next</strong>18.2.6. Starting
and Stopping the Service</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-service.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-service.html
new file mode 100644
index 0000000..d7aa396
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-service.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>18.2.6. Starting and Stopping the 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-autotasks-at-batch.html" title="18.2. At and Batch"
/><link rel="prev"
href="s2-autotasks-at-batch-controlling-access.html"
title="18.2.5. Controlling Access to At and Batch" /><link
rel="next" href="s1-autotasks-additional-resources.html"
title="18.3. Additional Resources" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-at-batch-controlling-access.html
"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-autotasks-additional-resources.html"><strong>Next</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"
id="s2-autotasks-at-batch-service">18.2.6. Starting and Stopping the
Service</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">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-at-batch-controlling-access.html"><strong>Prev</strong>18.2.5. Controlling
Access to At and Batch</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-autotasks-additional-resources.html"><strong>Next</strong>18.3. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-viewing.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-viewing.html
new file mode 100644
index 0000000..fa20a41
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-at-batch-viewing.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>18.2.3. Viewing Pending Jobs</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-autotasks-at-batch.html" title="18.2. At and Batch"
/><link rel="prev" href="s2-autotasks-batch-configuring.html"
title="18.2.2. Configuring Batch Jobs" /><link rel="next"
href="s2-autotasks-commandline-options.html" title="18.2.4. Additional
Command Line Options" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-autotasks-batch-configuring.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n"
href="s2-autotasks-commandline-options.html"><strong>Next</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"
id="s2-autotasks-at-batch-viewing">18.2.3. Viewing Pending
Jobs</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>Prev</strong>18.2.2. Configuring
Batch Jobs</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-commandline-options.html"><strong>Next</strong>18.2.4. Additional
Command Line Options</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-batch-configuring.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-batch-configuring.html
new file mode 100644
index 0000000..eb45501
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-batch-configuring.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>18.2.2. Configuring Batch Jobs</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-autotasks-at-batch.html" title="18.2. At and Batch"
/><link rel="prev" href="s1-autotasks-at-batch.html"
title="18.2. At and Batch" /><link rel="next"
href="s2-autotasks-at-batch-viewing.html" title="18.2.3. Viewing Pending
Jobs" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-autotasks-at-batch.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n
"
href="s2-autotasks-at-batch-viewing.html"><strong>Next</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"
id="s2-autotasks-batch-configuring">18.2.2. Configuring Batch
Jobs</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">
+ If the set of commands or script tries to display information to standard out, 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">Section 18.2.3, “Viewing Pending
Jobs”</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">Section 18.2.5,
“Controlling Access to At and Batch”</a> for details.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-autotasks-at-batch.html"><strong>Prev</strong>18.2. At
and Batch</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-at-batch-viewing.html"><strong>Next</strong>18.2.3. Viewing
Pending Jobs</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-commandline-options.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-commandline-options.html
new file mode 100644
index 0000000..6a37d10
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-autotasks-commandline-options.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>18.2.4. Additional Command Line Options</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-autotasks-at-batch.html" title="18.2. At and Batch"
/><link rel="prev" href="s2-autotasks-at-batch-viewing.html"
title="18.2.3. Viewing Pending Jobs" /><link rel="next"
href="s2-autotasks-at-batch-controlling-access.html"
title="18.2.5. Controlling Access to At and 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-autotasks-at-batch-viewing.html"><strong>Pre
v</strong></a></li><li class="next"><a
accesskey="n"
href="s2-autotasks-at-batch-controlling-access.html"><strong>Next</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"
id="s2-autotasks-commandline-options">18.2.4. Additional Command Line
Options</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>Table 18.1. <code
class="command">at</code> and <code
class="command">batch</code> Command Line Options</h6><div
class="table-contents"><table summary=" at and batch Command Line
Options" border="1"><colgroup><col width="29%"
class="option" /><col width="71%" class="description"
/></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-f</code>
+ </td><td>
+ Read the commands or shell script from a file instead of specifying them at the
prompt.
+ </td></tr><tr><td>
+ <code class="option">-m</code>
+ </td><td>
+ Send email to the user when the job has been completed.
+ </td></tr><tr><td>
+ <code class="option">-v</code>
+ </td><td>
+ Display the time that the job is executed.
+ </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>Prev</strong>18.2.3. Viewing
Pending Jobs</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-autotasks-at-batch-controlling-access.html"><strong>Next</strong>18.2.5. Controlling
Access to At and Batch</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-additional-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-additional-resources.html
new file mode 100644
index 0000000..bde3d49
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-additional-resources.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>11.2.7. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-BIND.html" title="11.2. BIND" /><link
rel="prev" href="s2-bind-mistakes.html" title="11.2.6. Common
Mistakes to Avoid" /><link rel="next"
href="ch-Web_Servers.html" title="Chapter 12. Web Servers"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-bind-mistakes.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Web_Servers.html"><strong>
Next</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"
id="s2-bind-additional-resources">11.2.7. Additional
Resources</h3></div></div></div><div
class="para">
+ The following sources of information provide additional resources regarding BIND.
+ </div><div class="section"
id="s3-bind-installed-docs"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-installed-docs">11.2.7.1. Installed
Documentation</h4></div></div></div><a id="id588287"
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><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">
+ The main directory containing the most recent documentation.
+ </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">
+ The directory providing every RFC document related to BIND.
+ </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><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"
id="s3-bind-useful-websites">11.2.7.2. Useful
Websites</h4></div></div></div><a id="id534498"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://www.isc.org/software/bind">http://www.isc.org/s...
class="para">
+ The home page of the BIND project containing information about current releases as
well as a PDF version of the <em class="citetitle">BIND 9 Administrator
Reference Manual</em>.
+ </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"
id="s3-bind-related-books">11.2.7.3. Related
Books</h4></div></div></div><a id="id583386"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><em
class="citetitle">DNS and BIND</em> by Paul Albitz and Cricket Liu;
O'Reilly & Associates</span></dt><dd><div
class="para">
+ A popular reference that explains both common and esoteric BIND configuration
options, and provides strategies for securing a DNS server.
+ </div></dd><dt class="varlistentry"><span
class="term"><em class="citetitle">The Concise Guide to DNS
and BIND</em> by 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>Prev</strong>11.2.6. Common
Mistakes to Avoid</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Web_Servers.html"><strong>Next</strong>Chapter 12. Web
Servers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-dig.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-dig.html
new file mode 100644
index 0000000..163e138
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-dig.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>11.2.4. Using the dig 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-BIND.html" title="11.2. BIND" /><link
rel="prev" href="s2-bind-rndc.html" title="11.2.3. Using the rndc
Utility" /><link rel="next" href="s2-bind-features.html"
title="11.2.5. Advanced Features of 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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-features.html"><stro
ng>Next</strong></a></li></ul><div
class="section" id="s2-bind-dig"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-dig">11.2.4. Using the dig
Utility</h3></div></div></div><a id="id590809"
class="indexterm"></a><div class="para">
+ The <code class="command">dig</code> utility is a command line
tool that allows you to perform DNS lookups and debug a nameserver configuration. Its
typical usage is as follows:
+ </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">
+ Refer to <a class="xref"
href="s2-bind-zone.html#s4-bind-zone-rr">Section 11.2.2.2, “Common Resource
Records”</a> for a list of common <em
class="replaceable"><code>type</code></em>s.
+ </div><div class="section" id="s3-bind-dig-ns"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-dig-ns">11.2.4.1. Looking Up a
Nameserver</h4></div></div></div><div
class="para">
+ To look up a nameserver for a particular domain, use the command in the following
form:
+ </div><pre class="screen"><code
class="command">dig</code> <em
class="replaceable"><code>name</code></em>
NS</pre><div class="para">
+ In <a class="xref"
href="s2-bind-dig.html#example-bind-dig-ns">Example 11.16, “A sample
nameserver lookup”</a>, the <code class="command">dig</code>
utility is used to display nameservers for <code
class="systemitem">example.com</code>.
+ </div><div class="example"
id="example-bind-dig-ns"><h6>Example 11.16. A sample nameserver
lookup</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"
id="s3-bind-dig-a">11.2.4.2. Looking Up an IP
Address</h4></div></div></div><div class="para">
+ To look up an IP address assigned to a particular domain, use the command in the
following form:
+ </div><pre class="screen"><code
class="command">dig</code> <em
class="replaceable"><code>name</code></em>
A</pre><div class="para">
+ In <a class="xref"
href="s2-bind-dig.html#example-bind-dig-a">Example 11.17, “A sample IP
address lookup”</a>, the <code class="command">dig</code>
utility is used to display the IP address of <code
class="systemitem">example.com</code>.
+ </div><div class="example"
id="example-bind-dig-a"><h6>Example 11.17. A sample IP address
lookup</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"
id="s3-bind-dig-x">11.2.4.3. Looking Up a
Hostname</h4></div></div></div><div class="para">
+ To look up a hostname for a particular IP address, use the command in the following
form:
+ </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">
+ In <a class="xref"
href="s2-bind-dig.html#example-bind-dig-x">Example 11.18, “A sample hostname
lookup”</a>, the <code class="command">dig</code> utility is
used to display the hostname assigned to <code
class="systemitem">192.0.32.10</code>.
+ </div><div class="example"
id="example-bind-dig-x"><h6>Example 11.18. A sample hostname
lookup</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>Prev</strong>11.2.3. Using the
rndc Utility</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-features.html"><strong>Next</strong>11.2.5. Advanced
Features of BIND</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-features.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-features.html
new file mode 100644
index 0000000..52b2ebc
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-features.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>11.2.5. Advanced Features of 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-BIND.html" title="11.2. BIND" /><link
rel="prev" href="s2-bind-dig.html" title="11.2.4. Using the dig
Utility" /><link rel="next" href="s2-bind-mistakes.html"
title="11.2.6. Common Mistakes to Avoid" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-mistakes.html"><strong>N
ext</strong></a></li></ul><div class="section"
id="s2-bind-features"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-features">11.2.5. Advanced Features of
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>Make sure the feature is
supported</h2></div><div class="admonition"><div
class="para">
+ Before attempting to use advanced features like DNSSEC, TSIG, or IXFR, make sure that
the particular feature is supported by all nameservers in the network environment,
especially when you use older versions of BIND or non-BIND servers.
+ </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">Section 11.2.7.1,
“Installed Documentation”</a>.
+ </div><div class="section"
id="s3-bind-features-views"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-features-views">11.2.5.1. Multiple
Views</h4></div></div></div><a id="id575530"
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"
id="s3-bind-features-ixfr">11.2.5.2. Incremental Zone Transfers
(IXFR)</h4></div></div></div><a id="id584597"
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="id583871"
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"
id="s3-bind-features-tsig">11.2.5.3. Transaction SIGnatures
(TSIG)</h4></div></div></div><a id="id553710"
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"
id="s3-bind-features-dnssec">11.2.5.4. DNS Security Extensions
(DNSSEC)</h4></div></div></div><a id="id542005"
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="id636840"
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">Section 11.2.4, “Using the dig
Utility”</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"
id="s3-bind-features-ipv6">11.2.5.5. Internet Protocol version 6
(IPv6)</h4></div></div></div><a id="id588968"
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">Table 11.3, “Commonly
used options”</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-bind-dig.html"><strong>Prev</strong>11.2.4. Using the
dig Utility</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-mistakes.html"><strong>Next</strong>11.2.6. Common
Mistakes to Avoid</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-mistakes.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-mistakes.html
new file mode 100644
index 0000000..09e6db3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-mistakes.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>11.2.6. Common Mistakes to Avoid</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-BIND.html" title="11.2. BIND" /><link
rel="prev" href="s2-bind-features.html" title="11.2.5. Advanced
Features of BIND" /><link rel="next"
href="s2-bind-additional-resources.html" title="11.2.7. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-bind-features.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-bind-ad
ditional-resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-bind-mistakes"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-mistakes">11.2.6. Common Mistakes to
Avoid</h3></div></div></div><a id="id566847"
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><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">Configure the firewall</span></dt><dd><div
class="para">
+ If a firewall is blocking connections from the <code
class="systemitem">named</code> service to other nameservers, the
recommended best practice is to change the firewall settings whenever possible.
+ </div><div class="warning"
id="warning-Warning-Avoid_Using_Fixed_UDP_Source_Ports"><div
class="admonition_header"><h2>Avoid using fixed UDP source
ports</h2></div><div class="admonition"><div
class="para">
+ According to the recent research in DNS security, using a fixed UDP source port
for DNS queries is a potential security vulnerability that could allow an attacker to
conduct cache-poisoning attacks more easily. To prevent this, configure your firewall to
allow queries from a random UDP source port.
+ </div></div></div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-bind-features.html"><strong>Prev</strong>11.2.5. Advanced
Features of BIND</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-additional-resources.html"><strong>Next</strong>11.2.7. Additional
Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-rndc.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-rndc.html
new file mode 100644
index 0000000..2344b56
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-rndc.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>11.2.3. Using the rndc 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-BIND.html" title="11.2. BIND" /><link
rel="prev" href="s2-bind-zone.html" title="11.2.2. Editing Zone
Files" /><link rel="next" href="s2-bind-dig.html"
title="11.2.4. Using the dig 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-bind-zone.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-dig.html"><strong>Next</strong></
a></li></ul><div class="section"
id="s2-bind-rndc"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-rndc">11.2.3. Using the rndc
Utility</h3></div></div></div><a id="id608382"
class="indexterm"></a><div class="para">
+ The <code class="command">rndc</code> utility is a command line
tool that allows you to administer the <code
class="systemitem">named</code> service, both locally and from a remote
machine. Its usage is as follows:
+ </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"
id="s3-bind-rndc-configuration">11.2.3.1. Configuring the
Utility</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>Table 11.7. Relevant
files</h6><div class="table-contents"><table
summary="Relevant files" border="1"><colgroup><col
width="38%" class="path" /><col width="63%"
class="description" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id561396" class="indexterm"></a>
+ <code class="filename">/etc/named.conf</code>
+ </td><td>
+ The default configuration file for the <code
class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <a id="id593924" class="indexterm"></a>
+ <code class="filename">/etc/rndc.conf</code>
+ </td><td>
+ The default configuration file for the <code
class="command">rndc</code> utility.
+ </td></tr><tr><td>
+ <a id="id637344" class="indexterm"></a>
+ <code class="filename">/etc/rndc.key</code>
+ </td><td>
+ The default key location.
+ </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">Section 11.2.1.2, “Other
Statement Types”</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">Section 11.2.7, “Additional
Resources”</a>.
+ </div><div class="important"><div
class="admonition_header"><h2>Set the correct
permissions</h2></div><div class="admonition"><div
class="para">
+ To prevent unprivileged users from sending control commands to the service, make
sure only root is allowed to read the <code
class="filename">/etc/rndc.key</code> file:
+ </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"
id="s3-bind-rndc-status">11.2.3.2. Checking the Service
Status</h4></div></div></div><div class="para">
+ To check the current status of the <code
class="systemitem">named</code> service, use the following command:
+ </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"
id="s3-bind-rndc-reload">11.2.3.3. Reloading the Configuration and
Zones</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">
+ Finally, to reload the configuration file and newly added zones only, type:
+ </div><pre class="screen">~]# <code
class="command">rndc reconfig</code></pre><div
class="note"><div
class="admonition_header"><h2>Modifying zones with dynamic
DNS</h2></div><div class="admonition"><div
class="para">
+ If you intend to manually modify a zone that uses Dynamic DNS (DDNS), make sure you
run the <code class="command">freeze</code> command first:
+ </div><pre class="screen">~]# <code
class="command">rndc freeze localhost</code></pre><div
class="para">
+ Once you are finished, run the <code
class="command">thaw</code> command to allow the DDNS again and reload
the zone:
+ </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"
id="s3-bind-rndc-sign">11.2.3.4. Updating Zone
Keys</h4></div></div></div><div class="para">
+ To update the DNSSEC keys and sign the zone, use the <code
class="command">sign</code> command. For example:
+ </div><pre class="screen">~]# <code
class="command">rndc sign localhost</code></pre><div
class="para">
+ Note that to sign a zone with the above command, the <code
class="option">auto-dnssec</code> option has to be set to <code
class="literal">maintain</code> in the zone statement. For instance:
+ </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"
id="s3-bind-rndc-validation">11.2.3.5. Enabling the DNSSEC
Validation</h4></div></div></div><div
class="para">
+ To enable the DNSSEC validation, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code
class="command">rndc validation on</code></pre><div
class="para">
+ Similarly, to disable this option, type:
+ </div><pre class="screen">~]# <code
class="command">rndc validation off</code></pre><div
class="para">
+ Refer to the <code class="option">options</code> statement
described in <a class="xref"
href="s1-BIND.html#s3-bind-namedconf-state">Section 11.2.1.1, “Common
Statement Types”</a> for information on how configure this option in <code
class="filename">/etc/named.conf</code>.
+ </div></div><div class="section"
id="s3-bind-rndc-querylog"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-rndc-querylog">11.2.3.6. Enabling the Query
Logging</h4></div></div></div><div class="para">
+ To enable (or disable in case it is currently enabled) the query logging, run the
following command:
+ </div><pre class="screen">~]# <code
class="command">rndc querylog</code></pre><div
class="para">
+ To check the current setting, use the <code
class="command">status</code> command as described in <a
class="xref"
href="s2-bind-rndc.html#s3-bind-rndc-status">Section 11.2.3.2, “Checking the
Service Status”</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-bind-zone.html"><strong>Prev</strong>11.2.2. Editing
Zone Files</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-dig.html"><strong>Next</strong>11.2.4. Using the
dig Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-zone.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-zone.html
new file mode 100644
index 0000000..9bb2704
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-bind-zone.html
@@ -0,0 +1,256 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Editing Zone 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-BIND.html" title="11.2. BIND" /><link
rel="prev" href="s1-BIND.html" title="11.2. BIND"
/><link rel="next" href="s2-bind-rndc.html"
title="11.2.3. Using the rndc 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="s1-BIND.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-rndc.html"><strong>Next</strong></a></li></ul><div
class=
"section" id="s2-bind-zone"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-bind-zone">11.2.2. Editing Zone
Files</h3></div></div></div><a id="id645070"
class="indexterm"></a><a id="id645055"
class="indexterm"></a><a id="id645043"
class="indexterm"></a><a id="id645022"
class="indexterm"></a><div class="para">
+ As outlined in <a class="xref"
href="ch-DNS_Servers.html#s2-dns-introduction-zones">Section 11.1.1,
“Nameserver 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>Table 11.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>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/var/named/</code>
+ </td><td>
+ The working directory for the <code
class="systemitem">named</code> service. The nameserver is <span
class="emphasis"><em>not</em></span> allowed to write to
this directory.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/slaves/</code>
+ </td><td>
+ The directory for secondary zones. This directory is writable by the <code
class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/dynamic/</code>
+ </td><td>
+ 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>
+ <code class="filename">/var/named/data/</code>
+ </td><td>
+ 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">
+ All directives and resource records should be entered on individual lines.
+ </div><div class="section"
id="s3-bind-zone-directives"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-zone-directives">11.2.2.1. Common
Directives</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><dt
class="varlistentry"><span class="term"> <a
id="id644838" 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>Example 11.6. Using the
$INCLUDE directive</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="id644781" 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">Example 11.7,
“Using the $ORIGIN directive”</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>Example 11.7. Using the
$ORIGIN directive</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="id644712"
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">
+ Increasing this value allows remote nameservers to cache the zone information for
a longer period of time, reducing the number of queries for the zone and lengthening the
amount of time required to proliferate resource record changes.
+ </div><div class="example"
id="example-bind-zone-directive-ttl"><h6>Example 11.8. Using the $TTL
directive</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"
id="s4-bind-zone-rr">11.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><dt
class="varlistentry"><span class="term"> <a
id="id644650" 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">Example 11.9, “Using the A
resource record”</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>Example 11.9. Using the A resource
record</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="id644563" 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">Example 11.10, “Using the
CNAME resource record”</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>Example 11.10. Using the CNAME
resource record</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="id644450" 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">Example 11.11, “Using the MX
resource record”</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>Example 11.11. Using the MX resource
record</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="id644354" class="indexterm"></a>
+ <code class="command">NS</code>
</span></dt><dd><div class="para">
+ The <em class="firstterm">Nameserver</em> record announces
authoritative nameservers for a particular zone. It takes the following form:
+ </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>Example 11.12. Using the NS resource
record</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="id644262" class="indexterm"></a>
+ <code class="command">PTR</code>
</span></dt><dd><div class="para">
+ The <em class="firstterm">Pointer</em> record points to
another part of the namespace. It takes the following form:
+ </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">Section 11.2.2.4.2,
“A Reverse Name Resolution Zone File”</a> for more examples of <code
class="command">PTR</code> records in use.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id644228"
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">
+ The directives are as follows:
+ </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">Table 11.6, “Seconds compared to
other time units”</a> shows an amount of time in seconds and the equivalent time in
another format.
+ </div><div class="table"
id="tb-bind-seconds"><h6>Table 11.6. Seconds compared to other time
units</h6><div class="table-contents"><table
summary="Seconds compared to other time units"
border="1"><colgroup><col width="50%"
class="seconds" /><col width="50%" class="other"
/></colgroup><thead><tr><th>
+ Seconds
+ </th><th>
+ Other Time Units
+ </th></tr></thead><tbody><tr><td>
+ 60
+ </td><td>
+ <code class="literal">1M</code>
+ </td></tr><tr><td>
+ 1800
+ </td><td>
+ <code class="literal">30M</code>
+ </td></tr><tr><td>
+ 3600
+ </td><td>
+ <code class="literal">1H</code>
+ </td></tr><tr><td>
+ 10800
+ </td><td>
+ <code class="literal">3H</code>
+ </td></tr><tr><td>
+ 21600
+ </td><td>
+ <code class="literal">6H</code>
+ </td></tr><tr><td>
+ 43200
+ </td><td>
+ <code class="literal">12H</code>
+ </td></tr><tr><td>
+ 86400
+ </td><td>
+ <code class="literal">1D</code>
+ </td></tr><tr><td>
+ 259200
+ </td><td>
+ <code class="literal">3D</code>
+ </td></tr><tr><td>
+ 604800
+ </td><td>
+ <code class="literal">1W</code>
+ </td></tr><tr><td>
+ 31536000
+ </td><td>
+ <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>Example 11.13. Using the SOA resource
record</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"
id="s3-bind-zone-comm">11.2.2.3. Comment
Tags</h4></div></div></div><a id="id643842"
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 ; expire after 1
week</pre></div><div class="section"
id="s3-bind-zone-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-bind-zone-examples">11.2.2.4. Example
Usage</h4></div></div></div><div class="para">
+ The following examples show the basic usage of zone files.
+ </div><div class="section"
id="s4-bind-zone-examples-basic"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="s4-bind-zone-examples-basic">11.2.2.4.1. A Simple Zone
File</h5></div></div></div><a id="id643790"
class="indexterm"></a><div class="para">
+ <a class="xref"
href="s2-bind-zone.html#example-bind-zone-examples-basic">Example 11.14, “A
simple zone file”</a> demonstrates the use of standard directives and <code
class="command">SOA</code> values.
+ </div><div class="example"
id="example-bind-zone-examples-basic"><h6>Example 11.14. A simple zone
file</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">
+ This zone file would be called into service with a <code
class="command">zone</code> statement in the <code
class="filename">/etc/named.conf</code> similar to the following:
+ </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"
id="s3-bind-configuration-zone-reverse">11.2.2.4.2. A Reverse Name Resolution
Zone File</h5></div></div></div><a id="id636236"
class="indexterm"></a><div class="para">
+ A reverse name resolution zone file is used to translate an IP address in a
particular namespace into an fully qualified domain name (FQDN). It looks very similar to
a standard zone file, except that the <code
class="command">PTR</code> resource records are used to link the IP
addresses to a fully qualified domain name as shown in <a class="xref"
href="s2-bind-zone.html#example-bind-zone-examples-reverse">Example 11.15, “A
reverse name resolution zone file”</a>.
+ </div><div class="example"
id="example-bind-zone-examples-reverse"><h6>Example 11.15. A reverse
name resolution zone file</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">
+ In this example, IP addresses <code
class="systemitem">10.0.1.1</code> through <code
class="systemitem">10.0.1.6</code> are pointed to the corresponding
fully qualified domain name.
+ </div><div class="para">
+ This zone file would be called into service with a <code
class="option">zone</code> statement in the <code
class="filename">/etc/named.conf</code> file similar to the following:
+ </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>Prev</strong>11.2. BIND</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-bind-rndc.html"><strong>Next</strong>11.2.3. Using the
rndc Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-mta-fetchmail.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-mta-fetchmail.html
new file mode 100644
index 0000000..a52051f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-mta-fetchmail.html
@@ -0,0 +1,116 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.3.3. 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-email-mta.html" title="13.3. Mail Transport Agents"
/><link rel="prev" href="s2-email-mta-sendmail.html"
title="13.3.2. Sendmail" /><link rel="next"
href="s2-email-switchmail.html" title="13.3.4. Mail Transport Agent (MTA)
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-email-mta-sendmail.html"><strong>Prev</strong></a></li><li
class="next"><a acce
sskey="n"
href="s2-email-switchmail.html"><strong>Next</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"
id="s2-email-mta-fetchmail">13.3.3. Fetchmail</h3></div></div></div><a
id="id597992" class="indexterm"></a><a
id="id598007" 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>Installing the fetchmail
package</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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ Fetchmail is configured for each user through the use of a <code
class="filename">.fetchmailrc</code> file in the user's home
directory. If it does not already exist, create the <code
class="filename">.fetchmailrc</code> file in your home directory
+ </div><div class="para">
+ Using preferences in the <code
class="filename">.fetchmailrc</code> file, Fetchmail checks for email
on a remote server and downloads it. It then delivers it to port <code
class="constant">25</code> on the local machine, using the local MTA to
place the email in the correct user's spool file. If Procmail is available, it is
launched to filter the email and place it in a mailbox so that it can be read by an MUA.
+ </div><div class="section"
id="s3-email-mda-fetchmail-configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-mda-fetchmail-configuration">13.3.3.1. Fetchmail Configuration
Options</h4></div></div></div><a id="id422766"
class="indexterm"></a><a id="id422781"
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">
+ A user's <code class="filename">.fetchmailrc</code> file
contains three classes of configuration options:
+ </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">
+ The following is a sample example of a <code
class="filename">.fetchmailrc</code> file:
+ </div><pre class="programlisting">set postmaster
"user1"
+set bouncemail
+
+poll
pop.domain.com proto pop3
+ user 'user1' there with password 'secret' is user1 here
+
+poll
mail.domain2.com
+ user 'user5' there with password 'secret2' is user1 here
+ user 'user7' there with password 'secret3' is user1
here</pre><div class="para">
+ In this example, the global options specify that the user is sent email as a last
resort (<code class="command">postmaster</code> option) and all
email errors are sent to the postmaster instead of the sender (<code
class="command">bouncemail</code> option). The <code
class="command">set</code> action tells Fetchmail that this line
contains a global option. Then, two email servers are specified, one set to check using
<code class="systemitem">POP3</code>, the other for trying various
protocols to find one that works. Two users are checked using the second server option,
but all email found for any user is sent to <code
class="command">user1</code>'s mail spool. This allows multiple
mailboxes to be checked on multiple servers, while appearing in a single MUA inbox. Each
user's specific information begins with the <code
class="command">user</code> action.
+ </div><div class="note"><div
class="admonition_header"><h2>Omitting the password from the
configuration</h2></div><div class="admonition"><div
class="para">
+ Users are not required to place their password in the <code
class="filename">.fetchmailrc</code> file. Omitting the <code
class="command">with password '<em
class="replaceable"><code>password</code></em>'</code>
section causes Fetchmail to ask for a password when it is launched.
+ </div></div></div><div class="para">
+ Fetchmail has numerous global, server, and local options. Many of these options are
rarely used or only apply to very specific situations. The <code
class="filename">fetchmail</code> man page explains each option in
detail, but the most common ones are listed in the following three sections.
+ </div></div><div class="section"
id="s3-email-mda-fetchmail-configuration-global"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-mda-fetchmail-configuration-global">13.3.3.2. Global
Options</h4></div></div></div><a id="id448132"
class="indexterm"></a><a id="id598469"
class="indexterm"></a><div class="para">
+ Each global option should be placed on a single line after a <code
class="command">set</code> action.
+ </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> — Specifies a local
user to send mail to in case of delivery problems.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">syslog</code> — Specifies the log file
for errors and status messages. By default, this is <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"
id="s3-email-mda-fetchmail-configuration-server">13.3.3.3. Server
Options</h4></div></div></div><a id="id422758"
class="indexterm"></a><a id="id572921"
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"
id="s3-email-fetchmail-configuration-user">13.3.3.4. User
Options</h4></div></div></div><a id="id448280"
class="indexterm"></a><a id="id608186"
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> — Activates SSL
encryption.
+ </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"
id="s3-email-mda-fetchmail-commands">13.3.3.5. Fetchmail Command
Options</h4></div></div></div><a id="id479399"
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"
id="s3-email-mda-fetchmail-commands-info">13.3.3.6. Informational or
Debugging Options</h4></div></div></div><a
id="id425280" class="indexterm"></a><div
class="para">
+ Certain options used after the <code
class="command">fetchmail</code> command can supply important
information.
+ </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"
id="s3-email-mda-fetchmail-commands-special">13.3.3.7. Special
Options</h4></div></div></div><a id="id584640"
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> — Quits the Fetchmail
daemon process.
+ </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>Prev</strong>13.3.2. Sendmail</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-switchmail.html"><strong>Next</strong>13.3.4. Mail
Transport Agent (MTA)
Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-mta-sendmail.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-mta-sendmail.html
new file mode 100644
index 0000000..216aec3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-mta-sendmail.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>13.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-email-mta.html" title="13.3. Mail Transport Agents"
/><link rel="prev" href="s1-email-mta.html"
title="13.3. Mail Transport Agents" /><link rel="next"
href="s2-email-mta-fetchmail.html" title="13.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-email-mta-fetchm
ail.html"><strong>Next</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"
id="s2-email-mta-sendmail">13.3.2. Sendmail</h3></div></div></div><a
id="id569261" class="indexterm"></a><a
id="id569274" 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"
id="s3-email-mta-sendmail-purpose">13.3.2.1. Purpose and
Limitations</h4></div></div></div><a id="id570098"
class="indexterm"></a><a id="id426596"
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">Section 13.6, “Additional
Resources”</a> for a list of Sendmail resources.
+ </div><div class="para">
+ This section reviews the files installed with Sendmail by default and reviews basic
configuration changes, including how to stop unwanted email (spam) and how to extend
Sendmail with the <em class="firstterm">Lightweight Directory Access
Protocol (LDAP)</em>.
+ </div></div><div class="section"
id="s3-email-mta-sendmail-default"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-mta-sendmail-default">13.3.2.2. The Default Sendmail
Installation</h4></div></div></div><a id="id623528"
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">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div><div class="para">
+ Before using Sendmail, the default MTA has to be switched from Postfix. For more
information how to switch the default MTA refer to <a class="xref"
href="s1-email-mta.html">Section 13.3, “Mail Transport Agents”</a>.
+ </div><div class="para">
+ The Sendmail executable is <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">Section 13.3.2.3,
“Common Sendmail Configuration Changes”</a>.
+ </div><div class="para">
+ Various Sendmail configuration files are installed in the <code
class="filename">/etc/mail/</code> directory including:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="filename">access</code> — Specifies which
systems can use Sendmail for outbound email.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">domaintable</code> — Specifies domain
name mapping.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="filename">local-host-names</code> — Specifies
aliases for the host.
+ </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@other-example.com">bob@other-example.com</a></code>
+ , add the following line to the <code
class="filename">virtusertable</code> file:
+ </div><pre class="programlisting"><code
class="command">(a)example.com
bob(a)other-example.com</code></pre><div class="para">
+ To finalize the change, the <code
class="filename">virtusertable.db</code> file must be updated:
+ </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"
id="s3-email-mta-sendmail-changes">13.3.2.3. Common Sendmail Configuration
Changes</h4></div></div></div><a id="id532943"
class="indexterm"></a><a id="id631113"
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>Backup the sendmail.cf file before
changing its content</h2></div><div class="admonition"><div
class="para">
+ Before changing the <code class="filename">sendmail.cf</code>
file, it is a good idea to create a backup copy.
+ </div></div></div><div class="para">
+ To add the desired functionality to Sendmail, edit the <code
class="filename">/etc/mail/sendmail.mc</code> file as <code
class="systemitem">root</code>. Once you are finished, restart the
<code class="systemitem">sendmail</code> service and, if the
<span class="package">m4</span> package is installed, the <code
class="command">m4</code> macro processor will automatically generate a
new <code class="filename">sendmail.cf</code> configuration file:
+ </div><pre class="screen"><code
class="command">systemctl restart
sendmail.service</code></pre><div class="important"><div
class="admonition_header"><h2>Configuring Sendmail as a server for
other clients</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"
id="s3-email-sendmail-changes-masquerading">13.3.2.4. Masquerading</h4></div></div></div><a
id="id424742" class="indexterm"></a><a
id="id465751" 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(a)example.com</code> instead of <code
class="computeroutput">user(a)host.example.com</code>.
+ </div><div class="para">
+ To do this, add the following lines to <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"
id="s3-email-sendmail-stopping-spam">13.3.2.5. Stopping
Spam</h4></div></div></div><a id="id423737"
class="indexterm"></a><div class="para">
+ Email spam can be defined as unnecessary and unwanted email received by a user who
never requested the communication. It is a disruptive, costly, and widespread abuse of
Internet communication standards.
+ </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">Section 13.4.2.6,
“Spam Filters”</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"
id="s3-email-mta-sendmail-ldap">13.3.2.6. Using Sendmail with
LDAP</h4></div></div></div><a id="id600668"
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>Advanced
configuration</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">Section 13.3.2.3,
“Common Sendmail Configuration Changes”</a> for instructions.
+ </div><div class="para">
+ For more information on <code class="systemitem">LDAP</code>,
refer to <a class="xref"
href="ch-Directory_Servers.html#s1-OpenLDAP">Section 14.1,
“OpenLDAP”</a>.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-mta.html"><strong>Prev</strong>13.3. Mail
Transport Agents</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-mta-fetchmail.html"><strong>Next</strong>13.3.3. Fetchmail</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-procmail-recipes.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-procmail-recipes.html
new file mode 100644
index 0000000..127ee54
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-procmail-recipes.html
@@ -0,0 +1,141 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.4.2. Procmail Recipes</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-email-mda.html" title="13.4. Mail Delivery Agents"
/><link rel="prev" href="s1-email-mda.html"
title="13.4. Mail Delivery Agents" /><link rel="next"
href="s1-email-mua.html" title="13.5. Mail User Agents"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-mua.html"><strong
Next</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"
id="s2-email-procmail-recipes">13.4.2. Procmail
Recipes</h3></div></div></div><a id="id509411"
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">Section 13.4.2.5,
“Recipe Examples”</a>.
+ </div><div class="para">
+ Procmail recipes take the following form:
+ </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">Section 13.4.2.4,
“Special Conditions and Actions”</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"
id="s2-email-procmail-recipes-delivering">13.4.2.1. Delivering vs.
Non-Delivering Recipes</h4></div></div></div><a
id="id631598" class="indexterm"></a><a
id="id631617" 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">
+ When messages match a delivering recipe, Procmail performs the specified action and
stops comparing the message against any other recipes. Messages that match non-delivering
recipes continue to be compared against other recipes.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-flags"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-procmail-recipes-flags">13.4.2.2. Flags</h4></div></div></div><a
id="id629228" class="indexterm"></a><div
class="para">
+ Flags are essential to determine how or if a recipe's conditions are compared to
a message. The following flags are commonly used:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">A</code> — Specifies that this recipe
is only used if the previous recipe without an <code
class="command">A</code> or <code
class="command">a</code> flag also matched this message.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">a</code> — Specifies that this recipe
is only used if the previous recipe with an <code
class="command">A</code> or <code
class="command">a</code> flag also matched this message <span
class="emphasis"><em>and</em></span> was successfully
completed.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">B</code> — Parses the body of the
message and looks for matching conditions.
+ </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> — Uses the pipe as a filter.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">H</code> — Parses the header of the
message and looks for matching conditions. This is the default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">h</code> — Uses the header in a
resulting action. This is the default behavior.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">w</code> — Tells Procmail to wait for
the specified filter or program to finish, and reports whether or not it was successful
before considering the message filtered.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">W</code> — Is identical to <code
class="command">w</code> except that "Program failure"
messages are suppressed.
+ </div></li></ul></div><div class="para">
+ For a detailed list of additional flags, refer to the <code
class="filename">procmailrc</code> man page.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-lockfile"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-procmail-recipes-lockfile">13.4.2.3. Specifying a Local
Lockfile</h4></div></div></div><a id="id533495"
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">
+ Alternatively, specify the name of the local lockfile to be used with this recipe
after the colon.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-special"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-procmail-recipes-special">13.4.2.4. Special Conditions and
Actions</h4></div></div></div><a id="id625080"
class="indexterm"></a><a id="id445636"
class="indexterm"></a><div class="para">
+ Special characters used before Procmail recipe conditions and actions change the way
they are interpreted.
+ </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> — In the condition line, this
character inverts the condition, causing a match to occur only if the condition does not
match the message.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command"><</code> — Checks if the
message is under a specified number of bytes.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">></code> — Checks if the
message is over a specified number of bytes.
+ </div></li></ul></div><div class="para">
+ The following characters are used to perform special actions:
+ </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> — Starts a specified program
to process the message.
+ </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">
+ If no special character is used at the beginning of the action line, Procmail
assumes that the action line is specifying the mailbox in which to write the message.
+ </div></div><div class="section"
id="s3-email-procmail-recipes-examples"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-email-procmail-recipes-examples">13.4.2.5. Recipe
Examples</h4></div></div></div><a id="id603316"
class="indexterm"></a><div class="para">
+ Procmail is an extremely flexible program, but as a result of this flexibility,
composing Procmail recipes from scratch can be difficult for new users.
+ </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">
+ The following simple examples demonstrate the basic structure of Procmail recipes
and can provide the foundation for more intricate constructions.
+ </div><div class="para">
+ A basic recipe may not even contain conditions, as is illustrated in the following
example:
+ </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">
+ The following example matched messages from a specific email address and throws them
away.
+ </div><pre class="programlisting">:0 * ^From:
spammer(a)domain.com /dev/null</pre><div class="para">
+ With this example, any messages sent by <code
class="computeroutput">spammer(a)domain.com</code> are sent to the
<code class="filename">/dev/null</code> device, deleting them.
+ </div><div class="warning"><div
class="admonition_header"><h2>Sending messages to
/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">
+ The following recipe grabs email sent from a particular mailing list and places it
in a specified folder.
+ </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(a)domain.com</code> mailing list are
placed in the <code class="filename">tuxlug</code> mailbox
automatically for the MUA. Note that the condition in this example matches the message if
it has the mailing list's email address on the <code
class="computeroutput">From</code>, <code
class="computeroutput">Cc</code>, or <code
class="computeroutput">To</code> lines.
+ </div><div class="para">
+ Consult the many Procmail online resources available in <a class="xref"
href="s1-email-additional-resources.html">Section 13.6, “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"
id="s3-email-mda-spam">13.4.2.6. Spam
Filters</h4></div></div></div><a id="id591045"
class="indexterm"></a><a id="id591547"
class="indexterm"></a><a id="id591562"
class="indexterm"></a><div class="para">
+ Because it is called by Sendmail, Postfix, and Fetchmail upon receiving new emails,
Procmail can be used as a powerful tool for combating spam.
+ </div><div class="para">
+ This is particularly true when Procmail is used in conjunction with SpamAssassin.
When used together, these two applications can quickly identify spam emails, and sort or
destroy them.
+ </div><div class="para">
+ SpamAssassin uses header analysis, text analysis, blacklists, a spam-tracking
database, and self-learning Bayesian spam analysis to quickly and accurately identify and
tag spam.
+ </div><div class="note"><div
class="admonition_header"><h2>Installing the spamassassin
package</h2></div><div class="admonition"><div
class="para">
+ In order to use <span
class="application"><strong>SpamAssassin</strong></span>,
first ensure the <span class="package">spamassassin</span> package
is installed on your system by running, as <code
class="systemitem">root</code>:
+ </div><pre class="screen"><code
class="command">yum install spamassassin</code></pre><div
class="para">
+ For more information on installing packages with Yum, refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a>.
+ </div></div></div><div class="para">
+ The easiest way for a local user to use SpamAssassin is to place the following line
near the top of the <code class="filename">~/.procmailrc</code>
file:
+ </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">
+ The message body of the email is also prepended with a running tally of what
elements caused it to be diagnosed as spam.
+ </div><div class="para">
+ To file email tagged as spam, a rule similar to the following can be used:
+ </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">
+ To start the <code class="systemitem">spamd</code> daemon,
type the following command:
+ </div><pre class="screen"><code
class="command">systemctl start
spamassassin.service</code></pre><div class="para">
+ To start the SpamAssassin daemon when the system is booted, run:
+ </div><pre class="screen"><code
class="command">systemctl enable
spamassassin.service</code></pre><div class="para">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div><div class="para">
+ To configure Procmail to use the SpamAssassin client application instead of the Perl
script, place the following line near the top of the <code
class="filename">~/.procmailrc</code> file. For a system-wide
configuration, place it in <code
class="filename">/etc/procmailrc</code>:
+ </div><pre
class="programlisting">INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc</pre></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-email-mda.html"><strong>Prev</strong>13.4. Mail Delivery
Agents</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-mua.html"><strong>Next</strong>13.5. Mail User
Agents</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-related-books.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-related-books.html
new file mode 100644
index 0000000..52ecbee
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-related-books.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>13.6.3. Related Books</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-email-additional-resources.html" title="13.6. Additional
Resources" /><link rel="prev"
href="s2-email-useful-websites.html" title="13.6.2. Useful Websites"
/><link rel="next" href="ch-Directory_Servers.html"
title="Chapter 14. Directory Servers" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-useful-websites.html"><strong>Prev</strong></a></li><li
class="n
ext"><a accesskey="n"
href="ch-Directory_Servers.html"><strong>Next</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"
id="s2-email-related-books">13.6.3. Related
Books</h3></div></div></div><a id="id448103"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <em class="citetitle">Sendmail Milters: A Guide for Fighting
Spam</em> by Bryan Costales and Marcia Flynt; Addison-Wesley — A good Sendmail guide
that can help you customize your mail filters.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Sendmail</em> by Bryan Costales with
Eric Allman et al.; O'Reilly & Associates — A good Sendmail reference written
with the assistance of the original creator of Delivermail and Sendmail.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Removing the Spam: Email Processing and
Filtering</em> by Geoff Mulligan; Addison-Wesley Publishing Company — A volume that
looks at various methods used by email administrators using established tools, such as
Sendmail and Procmail, to manage spam problems.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Internet Email Protocols: A Developer's
Guide</em> by Kevin Johnson; Addison-Wesley Publishing Company — Provides a very
thorough review of major email protocols and the security they provide.
+ </div></li><li class="listitem"><div
class="para">
+ <em class="citetitle">Managing IMAP</em> by Dianna Mullet and
Kevin Mullet; O'Reilly & Associates — Details the steps required to configure
an IMAP server.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-email-useful-websites.html"><strong>Prev</strong>13.6.2. Useful
Websites</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Directory_Servers.html"><strong>Next</strong>Chapter 14. Directory
Servers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-switchmail.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-switchmail.html
new file mode 100644
index 0000000..f317f13
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-switchmail.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>13.3.4. Mail Transport Agent (MTA) 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-email-mta.html" title="13.3. Mail Transport Agents"
/><link rel="prev" href="s2-email-mta-fetchmail.html"
title="13.3.3. Fetchmail" /><link rel="next"
href="s1-email-mda.html" title="13.4. Mail Delivery Agents"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s1-email-m
da.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-email-switchmail"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-email-switchmail">13.3.4. Mail Transport Agent (MTA)
Configuration</h3></div></div></div><a id="id570190"
class="indexterm"></a><a id="id570203"
class="indexterm"></a><a id="id599606"
class="indexterm"></a><a id="id478278"
class="indexterm"></a><a id="id442047"
class="indexterm"></a><a id="id442058"
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="id437930"
class="indexterm"></a><a id="id437940"
class="indexterm"></a><div class="para">
+ Fedora 15 provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is
the default MTA.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-email-mta-fetchmail.html"><strong>Prev</strong>13.3.3. Fetchmail</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-mda.html"><strong>Next</strong>13.4. Mail Delivery
Agents</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-types-mda.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-types-mda.html
new file mode 100644
index 0000000..fb445f3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-types-mda.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.2.2. 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-email-types.html" title="13.2. Email Program Classifications"
/><link rel="prev" href="s1-email-types.html"
title="13.2. Email Program Classifications" /><link rel="next"
href="s2-email-types-mua.html" title="13.2.3. Mail User 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="s1-email-types.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" h
ref="s2-email-types-mua.html"><strong>Next</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"
id="s2-email-types-mda">13.2.2. Mail Delivery
Agent</h3></div></div></div><a id="id465063"
class="indexterm"></a><a id="id465082"
class="indexterm"></a><a id="id509152"
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">
+ Any program that actually handles a message for delivery to the point where it can be
read by an email client application can be considered an MDA. For this reason, some MTAs
(such as Sendmail and Postfix) can fill the role of an MDA when they append new email
messages to a local user's mail spool file. In general, MDAs do not transport messages
between systems nor do they provide a user interface; MDAs distribute and sort messages on
the local machine for an email client application to access.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-email-types.html"><strong>Prev</strong>13.2. Email
Program Classifications</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-types-mua.html"><strong>Next</strong>13.2.3. Mail
User Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-types-mua.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-types-mua.html
new file mode 100644
index 0000000..4ffb306
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-types-mua.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>13.2.3. Mail User 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-email-types.html" title="13.2. Email Program Classifications"
/><link rel="prev" href="s2-email-types-mda.html"
title="13.2.2. Mail Delivery Agent" /><link rel="next"
href="s1-email-mta.html" title="13.3. Mail Transport Agents"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" hre
f="s1-email-mta.html"><strong>Next</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"
id="s2-email-types-mua">13.2.3. Mail User
Agent</h3></div></div></div><a id="id552382"
class="indexterm"></a><a id="id460511"
class="indexterm"></a><a id="id423173"
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>Prev</strong>13.2.2. Mail
Delivery Agent</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-email-mta.html"><strong>Next</strong>13.3. Mail
Transport Agents</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-useful-websites.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-useful-websites.html
new file mode 100644
index 0000000..487000f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-email-useful-websites.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>13.6.2. Useful Websites</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-email-additional-resources.html" title="13.6. Additional
Resources" /><link rel="prev"
href="s1-email-additional-resources.html" title="13.6. Additional
Resources" /><link rel="next"
href="s2-email-related-books.html" title="13.6.3. Related Books"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
cl
ass="next"><a accesskey="n"
href="s2-email-related-books.html"><strong>Next</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"
id="s2-email-useful-websites">13.6.2. Useful
Websites</h3></div></div></div><a id="id535947"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.sendmail.org/">http://www.sendmail.org/<... — Offers a
thorough technical breakdown of Sendmail features, documentation and configuration
examples.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.sendmail.com/">http://www.sendmail.com/<... — Contains
news, interviews and articles concerning Sendmail, including an expanded view of the many
options available.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.postfix.org/">http://www.postfix.org/</a...
— The Postfix project home page contains a wealth of information about Postfix. The
mailing list is a particularly good place to look for information.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://fetchmail.berlios.de/">http://fetchmail.berlios.de/</a> —
The home page for Fetchmail, featuring an online manual, and a thorough FAQ.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.procmail.org/">http://www.procmail.org/<... — The home
page for Procmail with links to assorted mailing lists dedicated to Procmail as well as
various FAQ documents.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://partmaps.org/era/procmail/mini-faq.html">http:/...
— 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.... —
The official site of the SpamAssassin project.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-email-additional-resources.html"><strong>Prev</strong>13.6. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-email-related-books.html"><strong>Next</strong>13.6.3. Related
Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-resources.html
new file mode 100644
index 0000000..bbc106b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-resources.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>15.2.6. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-FTP.html" title="15.2. FTP" /><link
rel="prev" href="s2-ftp-vsftpd-conf.html" title="15.2.5. vsftpd
Configuration Options" /><link rel="next"
href="part-Monitoring_and_Automation.html" title="Part VI. Monitoring and
Automation" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" h
ref="part-Monitoring_and_Automation.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-ftp-resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ftp-resources">15.2.6. Additional
Resources</h3></div></div></div><a id="id472372"
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"
id="s3-ftp-installed-documentation">15.2.6.1. Installed
Documentation</h4></div></div></div><a id="id546958"
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><dt
class="varlistentry"><span class="term">Server
Applications</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">Configuration
Files</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"
id="s3-ftp-useful-websites">15.2.6.2. Useful
Websites</h4></div></div></div><a id="id668644"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/&l... — The
<code class="command">vsftpd</code> project page is a great place to
locate the latest documentation and to contact the author of the software.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://slacksite.com/other/ftp.html">http://slacksite....
— This website provides a concise explanation of the differences between active and
passive mode <code class="systemitem">FTP</code>.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://www.ietf.org/rfc/rfc0959.txt">http://www.ietf.o...
— The original <em class="firstterm">Request for Comments</em>
(<em class="firstterm">RFC</em>) of the <code
class="systemitem">FTP</code> protocol from the IETF.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s2-ftp-vsftpd-conf.html"><strong>Prev</strong>15.2.5.
vsftpd Configuration Options</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="part-Monitoring_and_Automation.html"><strong>Next</strong>Part VI. Monitoring
and Automation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-servers.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-servers.html
new file mode 100644
index 0000000..f952a1d
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-servers.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>15.2.2. FTP Servers</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-FTP.html" title="15.2. FTP" /><link
rel="prev" href="s1-FTP.html" title="15.2. FTP"
/><link rel="next" href="s3-ftp-vsftpd-conf.html"
title="15.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s3-ftp-vsftpd-conf.html"><strong>Next</strong></a></li></ul
<div class="section"
id="s2-ftp-servers"><div class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-ftp-servers">15.2.2. FTP
Servers</h3></div></div></div><a id="id505941"
class="indexterm"></a><a id="id624739"
class="indexterm"></a><a id="id571671"
class="indexterm"></a><a id="id480044"
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.re...;.
+ </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"
id="s3-ftp-servers-vsftpd">15.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>Prev</strong>15.2. FTP</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s3-ftp-vsftpd-conf.html"><strong>Next</strong>15.2.3. Files
Installed with vsftpd </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-vsftpd-conf.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-vsftpd-conf.html
new file mode 100644
index 0000000..003a938
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-vsftpd-conf.html
@@ -0,0 +1,338 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>15.2.5. vsftpd Configuration Options</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-FTP.html" title="15.2. FTP" /><link
rel="prev" href="s2-ftp-vsftpd-start.html"
title="15.2.4. Starting and Stopping vsftpd" /><link rel="next"
href="s2-ftp-resources.html" title="15.2.6. Additional Resources"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ftp-vsftpd-start.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-ftp-resource
s.html"><strong>Next</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"
id="s2-ftp-vsftpd-conf">15.2.5. <code
class="command">vsftpd</code> Configuration
Options</h3></div></div></div><a id="id425371"
class="indexterm"></a><a id="id431224"
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 <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"
id="s3-ftp-vsftpd-conf-opt-daemon">15.2.5.1. Daemon
Options</h4></div></div></div><a id="id422868"
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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-login">15.2.5.2. Log In Options and Access
Controls</h4></div></div></div><a id="id466853"
class="indexterm"></a><a id="id535386"
class="indexterm"></a><div class="para">
+ The following is a list of directives which control the login behavior and access
control mechanisms.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">anonymous_enable</code> — When enabled,
anonymous users are allowed to log in. The usernames <code
class="computeroutput">anonymous</code> and <code
class="computeroutput">ftp</code> are accepted.
+ </div><div class="para">
+ The default value is <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">Section 15.2.5.3,
“Anonymous User Options”</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">
+ There is no default value for this directive.
+ </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">
+ There is no default value for this directive.
+ </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">
+ The default value is <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">
+ By default <code class="command">vsftpd</code> displays its
standard banner.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">local_enable</code> — When enabled,
local users are allowed to log into the system.
+ </div><div class="para">
+ The default value is <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">Section 15.2.5.4,
“Local User Options”</a> for a list of directives affecting local users.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">pam_service_name</code> — Specifies the
PAM service name for <code class="command">vsftpd</code>.
+ </div><div class="para">
+ The default value is <code class="command">ftp</code>. Note,
in Fedora, the value is set to <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div
class="para">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-anon">15.2.5.3. Anonymous User
Options</h4></div></div></div><a id="id566916"
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">
+ The default value is <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">
+ There is no default value for this directive.
+ </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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-usr">15.2.5.4. Local User
Options</h4></div></div></div><a id="id576463"
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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ There is no default value for this directive.
+ </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">
+ The default value is <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">
+ The default value is <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">
+ There is no default value for this directive.
+ </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"
id="s3-ftp-vsftpd-conf-opt-dir">15.2.5.5. Directory
Options</h4></div></div></div><a id="id637501"
class="indexterm"></a><div class="para">
+ The following lists directives which affect directories.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">dirlist_enable</code> — When enabled,
users are allowed to view directory lists.
+ </div><div class="para">
+ The default value is <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">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-file">15.2.5.6. File Transfer
Options</h4></div></div></div><a id="id566138"
class="indexterm"></a><div class="para">
+ The following lists directives which affect directories.
+ </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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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"
id="s3-ftp-vsftpd-conf-opt-log">15.2.5.7. Logging
Options</h4></div></div></div><a id="id432065"
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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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">
+ The default value is <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">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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"
id="s3-ftp-vsftpd-conf-opt-net">15.2.5.8. Network
Options</h4></div></div></div><a id="id623178"
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">
+ The default value is <code class="command">NO</code>. Note,
in Fedora, the value is set to <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">
+ There is no default value for this directive.
+ </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">Section 15.2.4.1,
“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">
+ There is no default value for this directive.
+ </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">Section 15.2.4.1,
“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">
+ There is no default value for this directive.
+ </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">
+ The default value is <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">
+ The default value is <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">
+ The default value is <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>Prev</strong>15.2.4. Starting
and Stopping vsftpd </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-resources.html"><strong>Next</strong>15.2.6. Additional
Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-vsftpd-start.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-vsftpd-start.html
new file mode 100644
index 0000000..1c4d59b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ftp-vsftpd-start.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>15.2.4. Starting and Stopping 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-FTP.html" title="15.2. FTP" /><link
rel="prev" href="s3-ftp-vsftpd-conf.html" title="15.2.3. Files
Installed with vsftpd" /><link rel="next"
href="s2-ftp-vsftpd-conf.html" title="15.2.5. vsftpd Configuration
Options" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-ftp-vsftpd-conf.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-ftp-
vsftpd-conf.html"><strong>Next</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"
id="s2-ftp-vsftpd-start">15.2.4. Starting and Stopping <code
class="command">vsftpd</code>
</h3></div></div></div><a id="id676840"
class="indexterm"></a><a id="id676485"
class="indexterm"></a><a id="id596532"
class="indexterm"></a><a id="id471727"
class="indexterm"></a><a id="id428149"
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">Chapter 7, <em>Services and
Daemons</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"
id="s3-ftp-vsftpd-start-multi">15.2.4.1. Starting Multiple Copies of <code
class="command">vsftpd</code>
</h4></div></div></div><a id="id547060"
class="indexterm"></a><a id="id669074"
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">Chapter 6, <em>Network
Interfaces</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">Section 11.2,
“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>Prev</strong>15.2.3. Files
Installed with vsftpd </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-vsftpd-conf.html"><strong>Next</strong>15.2.5.
vsftpd Configuration Options</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-backtrace.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-backtrace.html
new file mode 100644
index 0000000..4b54841
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-backtrace.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>22.2.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kdump-crash.html" title="22.2. Analyzing the Core Dump"
/><link rel="prev" href="s2-kdump-crash-log.html"
title="22.2.2. Displaying the Message Buffer" /><link rel="next"
href="s2-kdump-crash-processes.html" title="22.2.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>Prev</strong></a></li><li
class="ne
xt"><a accesskey="n"
href="s2-kdump-crash-processes.html"><strong>Next</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"
id="s2-kdump-crash-backtrace">22.2.3. Displaying a
Backtrace</h3></div></div></div><a id="id564771"
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>Example 22.5. 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>Prev</strong>22.2.2. Displaying
the Message Buffer</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kdump-crash-processes.html"><strong>Next</strong>22.2.4. Displaying
a Process Status</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-exit.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-exit.html
new file mode 100644
index 0000000..9e51727
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-exit.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>22.2.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kdump-crash.html" title="22.2. Analyzing the Core Dump"
/><link rel="prev" href="s2-kdump-crash-files.html"
title="22.2.6. Displaying Open Files" /><link rel="next"
href="s1-kdump-resources.html" title="22.3. Additional Resources"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-kdump-crash-files.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n
"
href="s1-kdump-resources.html"><strong>Next</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"
id="s2-kdump-crash-exit">22.2.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>Example 22.9. 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>Prev</strong>22.2.6. Displaying
Open Files</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kdump-resources.html"><strong>Next</strong>22.3. Additional
Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-files.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-files.html
new file mode 100644
index 0000000..d08418e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-files.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>22.2.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kdump-crash.html" title="22.2. Analyzing the Core Dump"
/><link rel="prev" href="s2-kdump-crash-memory.html"
title="22.2.5. Displaying Virtual Memory Information" /><link
rel="next" href="s2-kdump-crash-exit.html" title="22.2.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>Prev</strong></a></li><li
class="n
ext"><a accesskey="n"
href="s2-kdump-crash-exit.html"><strong>Next</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"
id="s2-kdump-crash-files">22.2.6. Displaying Open
Files</h3></div></div></div><a id="id601670"
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>Example 22.8. 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>Prev</strong>22.2.5. Displaying
Virtual Memory Information</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kdump-crash-exit.html"><strong>Next</strong>22.2.7. Exiting
the Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-log.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-log.html
new file mode 100644
index 0000000..f54d0c8
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-log.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>22.2.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kdump-crash.html" title="22.2. Analyzing the Core Dump"
/><link rel="prev" href="s1-kdump-crash.html"
title="22.2. Analyzing the Core Dump" /><link rel="next"
href="s2-kdump-crash-backtrace.html" title="22.2.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kdump-crash-backtrace.html"><strong>Next</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"
id="s2-kdump-crash-log">22.2.2. Displaying the Message
Buffer</h3></div></div></div><a id="id643567"
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>Example 22.4. 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>Prev</strong>22.2. Analyzing
the Core Dump</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kdump-crash-backtrace.html"><strong>Next</strong>22.2.3. Displaying
a Backtrace</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-memory.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-memory.html
new file mode 100644
index 0000000..debb448
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-memory.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.2.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kdump-crash.html" title="22.2. Analyzing the Core Dump"
/><link rel="prev" href="s2-kdump-crash-processes.html"
title="22.2.4. Displaying a Process Status" /><link rel="next"
href="s2-kdump-crash-files.html" title="22.2.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>Prev</strong></a></li><li
class="ne
xt"><a accesskey="n"
href="s2-kdump-crash-files.html"><strong>Next</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"
id="s2-kdump-crash-memory">22.2.5. Displaying Virtual Memory
Information</h3></div></div></div><a id="id562963"
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>Example 22.7. 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>Prev</strong>22.2.4. Displaying
a Process Status</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kdump-crash-files.html"><strong>Next</strong>22.2.6. Displaying
Open Files</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-processes.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-processes.html
new file mode 100644
index 0000000..ce7146c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-crash-processes.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>22.2.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kdump-crash.html" title="22.2. Analyzing the Core Dump"
/><link rel="prev" href="s2-kdump-crash-backtrace.html"
title="22.2.3. Displaying a Backtrace" /><link rel="next"
href="s2-kdump-crash-memory.html" title="22.2.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>Prev</strong></a></li><
li class="next"><a accesskey="n"
href="s2-kdump-crash-memory.html"><strong>Next</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"
id="s2-kdump-crash-processes">22.2.4. Displaying a Process
Status</h3></div></div></div><a id="id587916"
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>Example 22.6. 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>Prev</strong>22.2.3. Displaying
a Backtrace</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kdump-crash-memory.html"><strong>Next</strong>22.2.5. Displaying
Virtual Memory Information</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-resources-online.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-resources-online.html
new file mode 100644
index 0000000..6928d3b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kdump-resources-online.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>22.3.2. Useful Websites</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kdump-resources.html" title="22.3. Additional Resources"
/><link rel="prev" href="s1-kdump-resources.html"
title="22.3. Additional Resources" /><link rel="next"
href="ch-RPM.html" title="Appendix A. RPM" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kdump-resources.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch-RPM.html"><strong
Next</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"
id="s2-kdump-resources-online">22.3.2. Useful
Websites</h3></div></div></div><a id="id424548"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://people.redhat.com/anderson/">http://people.redh...
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>Prev</strong>22.3. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-RPM.html"><strong>Next</strong>Appendix A. RPM</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-boot-loader-iseries.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-boot-loader-iseries.html
new file mode 100644
index 0000000..94afb3f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-boot-loader-iseries.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>20.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kernel-boot-loader.html" title="20.6. Verifying the Boot
Loader" /><link rel="prev"
href="s1-kernel-boot-loader.html" title="20.6. Verifying the Boot
Loader" /><link rel="next"
href="s2-kernel-boot-loader-pseries.html" title="20.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>Prev</strong><
/a></li><li class="next"><a accesskey="n"
href="s2-kernel-boot-loader-pseries.html"><strong>Next</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"
id="s2-kernel-boot-loader-iseries">20.6.2. Configuring the OS/400 Boot
Loader</h3></div></div></div><a id="id623923"
class="indexterm"></a><a id="id546032"
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">
+ Begin testing the new kernel by rebooting the computer and watching the messages to
ensure that the hardware is detected properly.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-kernel-boot-loader.html"><strong>Prev</strong>20.6. Verifying
the Boot Loader</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-kernel-boot-loader-pseries.html"><strong>Next</strong>20.6.3. Configuring
the YABOOT Boot Loader</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-boot-loader-pseries.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-boot-loader-pseries.html
new file mode 100644
index 0000000..501f493
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-boot-loader-pseries.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>20.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kernel-boot-loader.html" title="20.6. Verifying the Boot
Loader" /><link rel="prev"
href="s2-kernel-boot-loader-iseries.html" title="20.6.2. Configuring the
OS/400 Boot Loader" /><link rel="next"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. 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-iseries.ht
ml"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Working_with_Kernel_Modules.html"><strong>Next</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"
id="s2-kernel-boot-loader-pseries">20.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">
+ Begin testing the new kernel by rebooting the computer and watching the messages to
ensure that the hardware is detected properly.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-kernel-boot-loader-iseries.html"><strong>Prev</strong>20.6.2. Configuring
the OS/400 Boot Loader</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Working_with_Kernel_Modules.html"><strong>Next</strong>Chapter 21. Working
with Kernel Modules</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-modules-additional-resources-websites.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-modules-additional-resources-websites.html
new file mode 100644
index 0000000..d431680
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-kernel-modules-additional-resources-websites.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>21.8.2. Useful Websites</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-kernel-modules-additional-resources.html" title="21.8. Additional
Resources" /><link rel="prev"
href="s1-kernel-modules-additional-resources.html" title="21.8. Additional
Resources" /><link rel="next" href="ch-kdump.html"
title="Chapter 22. 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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch-kdump.html"><strong>Next</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"
id="s2-kernel-modules-additional-resources-websites">21.8.2. Useful
Websites</h3></div></div></div><div
class="variablelist"><dl><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>Prev</strong>21.8. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-kdump.html"><strong>Next</strong>Chapter 22. The kdump
Crash Recovery Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-keys-checking.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-keys-checking.html
new file mode 100644
index 0000000..3a30660
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-keys-checking.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>A.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-check-rpm-sig.html" title="A.3. Checking a Package's
Signature" /><link rel="prev" href="s1-check-rpm-sig.html"
title="A.3. Checking a Package's Signature" /><link
rel="next" href="s1-rpm-impressing.html" title="A.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>Prev</strong></a></li><li
cl
ass="next"><a accesskey="n"
href="s1-rpm-impressing.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-keys-checking"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-keys-checking">A.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...;.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-check-rpm-sig.html"><strong>Prev</strong>A.3. Checking a
Package's Signature</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-rpm-impressing.html"><strong>Next</strong>A.4. Practical
and Common Examples of RPM
Usage</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-log-files-useful-websites.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-log-files-useful-websites.html
new file mode 100644
index 0000000..cb856bf
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-log-files-useful-websites.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Useful Websites</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-log-files-additional-resources.html" title="17.6. Additional
Resources" /><link rel="prev"
href="s1-log-files-additional-resources.html" title="17.6. Additional
Resources" /><link rel="next"
href="ch-Automating_System_Tasks.html" title="Chapter 18. Automating System
Tasks" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-additional-resources.html"><stro
ng>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="ch-Automating_System_Tasks.html"><strong>Next</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"
id="s2-log-files-useful-websites">17.6.2. Useful
Websites</h3></div></div></div><a id="id587322"
class="indexterm"></a><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <a
href="http://www.rsyslog.com/">http://www.rsyslog.com/</a...
— Offers a thorough technical breakdown of <span
class="package">rsyslog</span> features, documentation, configuration
examples, and video tutorials.
+ </div></li><li class="listitem"><div
class="para">
+ <a
href="http://wiki.rsyslog.com/index.php/Main_Page">http://wi...
— Contains useful <code class="filename">/etc/rsyslog.conf</code>
configuration examples.
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-log-files-additional-resources.html"><strong>Prev</strong>17.6. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Automating_System_Tasks.html"><strong>Next</strong>Chapter 18. Automating
System Tasks</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-alias.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-alias.html
new file mode 100644
index 0000000..1c41382
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-alias.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.2.3. Alias and Clone 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-networkscripts-interfaces.html" title="6.2. Interface
Configuration Files" /><link rel="prev"
href="s2-networkscripts-interfaces-chan.html" title="6.2.2. Channel Bonding
Interfaces" /><link rel="next"
href="s2-networkscripts-interfaces-ppp0.html" title="6.2.4. Dialup
Interfaces" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-chan.html">
<strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-networkscripts-interfaces-ppp0.html"><strong>Next</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"
id="s2-networkscripts-interfaces-alias">6.2.3. Alias and Clone
Files</h3></div></div></div><a id="id559185"
class="indexterm"></a><a id="id559203"
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.
+ </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="computeroutput">DEVICE=eth0:0</code> and a static IP address of
10.0.0.2, 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="filename">eth0</code> is
bound to a dynamic IP address, but the same physical network card can receive requests via
the fixed, 10.0.0.2 IP address.
+ </div><div class="warning"><div
class="admonition_header"><h2>Caution</h2></div><div
class="admonition"><div class="para">
+ Alias interfaces do not support 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="filename">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="command">USERCTL</code> directive is <code
class="command">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="filename">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">
+ The easiest way to create alias and clone interface configuration files is to use the
graphical <span class="application"><strong>Network Administration
Tool</strong></span>.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-networkscripts-interfaces-chan.html"><strong>Prev</strong>6.2.2. Channel
Bonding Interfaces</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-networkscripts-interfaces-ppp0.html"><strong>Next</strong>6.2.4. Dialup
Interfaces</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html
new file mode 100644
index 0000000..412c196
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-chan.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>6.2.2. Channel Bonding Interfaces</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-networkscripts-interfaces.html" title="6.2. Interface
Configuration Files" /><link rel="prev"
href="s1-networkscripts-interfaces.html" title="6.2. Interface
Configuration Files" /><link rel="next"
href="s2-networkscripts-interfaces-alias.html" title="6.2.3. Alias and
Clone 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="s1-networkscripts-interfaces.html"><str
ong>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="s2-networkscripts-interfaces-alias.html"><strong>Next</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"
id="s2-networkscripts-interfaces-chan">6.2.2. Channel Bonding
Interfaces</h3></div></div></div><a id="id558920"
class="indexterm"></a><a id="id558937"
class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind multiple network interfaces 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><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="command">DEVICE=</code> directive must be <code
class="command">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">
+ The following is a sample channel bonding configuration file:
+ </div><div class="example"
id="ex-Sample_ifcfg-bond0_interface_configuration_file"><h6>Example 6.1. Sample
ifcfg-bond0 interface configuration file</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>bonding parameters
separated by
spaces</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="command">MASTER=</code> and <code
class="command">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="filename">eth0</code> and <code
class="filename">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">
+ In this example, replace <em
class="replaceable"><code>N</code></em> with the numerical
value for the interface.
+ </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 <code class="systemitem">root</code> 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="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><div class="important"><div
class="admonition_header"><h2>Put all bonding module parameters in
ifcfg-bondN files</h2></div><div class="admonition"><div
class="para">
+ Parameters for the bonding kernel module must be specified as a space-separated list
in the <em class="parameter"><code>BONDING_OPTS="<em
class="replaceable"><code>bonding
parameters</code></em>"</code></em> directive in the
ifcfg-bond<em class="replaceable"><code>N</code></em>
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">Section 21.7.2, “Using Channel
Bonding”</a>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-networkscripts-interfaces.html"><strong>Prev</strong>6.2. Interface
Configuration Files</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-networkscripts-interfaces-alias.html"><strong>Next</strong>6.2.3. Alias
and Clone Files</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-other.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-other.html
new file mode 100644
index 0000000..6efff13
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-other.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.2.5. Other Interfaces</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-networkscripts-interfaces.html" title="6.2. Interface
Configuration Files" /><link rel="prev"
href="s2-networkscripts-interfaces-ppp0.html" title="6.2.4. Dialup
Interfaces" /><link rel="next"
href="s1-networkscripts-control.html" title="6.3. Interface Control
Scripts" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Pre
v</strong></a></li><li class="next"><a
accesskey="n"
href="s1-networkscripts-control.html"><strong>Next</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"
id="s2-networkscripts-interfaces-other">6.2.5. Other
Interfaces</h3></div></div></div><div
class="para">
+ Other common interface configuration files include the following:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="filename">ifcfg-lo</code>
</span></dt><dd><div class="para">
+ A local <em class="firstterm">loopback interface</em> is
often used in testing, as well as being used in a variety of applications that require an
IP address pointing back to the same system. Any data sent to the loopback device is
immediately returned to the host's network layer.
+ </div><div class="warning"><div
class="admonition_header"><h2>Do not manually edit the ifcfg-lo
script</h2></div><div class="admonition"><div
class="para">
+ The loopback interface script, <code
class="filename">/etc/sysconfig/network-scripts/ifcfg-lo</code>, should
never be edited manually. Doing so can prevent the system from operating correctly.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term"> <code
class="filename">ifcfg-irlan0</code>
</span></dt><dd><div class="para">
+ An <em class="firstterm">infrared interface</em> allows
information between devices, such as a laptop and a printer, to flow over an infrared
link. This works in a similar way to an Ethernet device except that it commonly occurs
over a peer-to-peer connection.
+ </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
(PLIP)</em> 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>Prev</strong>6.2.4. Dialup
Interfaces</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-networkscripts-control.html"><strong>Next</strong>6.3. Interface
Control Scripts</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-ppp0.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-networkscripts-interfaces-ppp0.html
new file mode 100644
index 0000000..257b0b4
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_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>6.2.4. Dialup Interfaces</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-networkscripts-interfaces.html" title="6.2. Interface
Configuration Files" /><link rel="prev"
href="s2-networkscripts-interfaces-alias.html" title="6.2.3. Alias and
Clone Files" /><link rel="next"
href="s2-networkscripts-interfaces-other.html" title="6.2.5. Other
Interfaces" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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-alias.html"><st
rong>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="s2-networkscripts-interfaces-other.html"><strong>Next</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"
id="s2-networkscripts-interfaces-ppp0">6.2.4. Dialup
Interfaces</h3></div></div></div><a id="id559377"
class="indexterm"></a><div class="para">
+ If you are connecting to the Internet via a dialup connection, a configuration file
is necessary for the interface.
+ </div><div class="para">
+ PPP interface files are named using the following format:
+ <div class="variablelist"><dl><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">
+ where <em
class="replaceable"><code>X</code></em> is a unique number
corresponding to a specific interface.
+ </div></dd></dl></div>
+
+ </div><div class="para">
+ The PPP interface configuration file is created automatically when <code
class="command">wvdial</code>, the <span
class="application"><strong>Network Administration
Tool</strong></span> or <span
class="application"><strong>Kppp</strong></span> is used to
create a dialup account. It is also possible to create and edit this file manually.
+ </div><div class="para">
+ The following is a typical <code
class="filename">ifcfg-ppp0</code> file:
+ </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 (SLIP)</em>
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">
+ Other options that may be used in these files include:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="command">DEFROUTE=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — Set this interface as
the default route.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — Do not set this
interface as the default route.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">DEMAND=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">yes</code> — This interface allows
<code class="command">pppd</code> to initiate a connection when
someone attempts to use it.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="command">no</code> — A connection must be
manually established for this interface.
+ </div></li></ul></div></dd><dt
class="varlistentry"><span class="term"> <code
class="command">IDLETIMEOUT=<em
class="replaceable"><code>value</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>value</code></em> </code>
is the number of seconds of idle activity before the interface disconnects itself.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">INITSTRING=<em
class="replaceable"><code>string</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>string</code></em> </code>
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="command">LINESPEED=<em
class="replaceable"><code>value</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>value</code></em> </code>
is the baud rate of the device. Possible standard values include <code
class="command">57600</code>, <code
class="command">38400</code>, <code
class="command">19200</code>, and <code
class="command">9600</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">MODEMPORT=<em
class="replaceable"><code>device</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>device</code></em> </code>
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="command">MTU=<em
class="replaceable"><code>value</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>value</code></em> </code>
is the <em class="firstterm">Maximum Transfer Unit (MTU)</em>
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="command">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="command">NAME=<em
class="replaceable"><code>name</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>name</code></em> </code> is
the reference to the title given to a collection of dialup connection configurations.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">PAPNAME=<em
class="replaceable"><code>name</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>name</code></em> </code> is
the username given during the <em class="firstterm">Password
Authentication Protocol (PAP)</em> exchange that occurs to allow connections to a
remote system.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">PERSIST=<em
class="replaceable"><code>answer</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>answer</code></em> </code>
is one of the following:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ <code class="command">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="command">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="command">REMIP=<em
class="replaceable"><code>address</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>address</code></em> </code>
is the IP address of the remote system. This is usually left unspecified.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="command">WVDIALSECT=<em
class="replaceable"><code>name</code></em> </code>
</span></dt><dd><div class="para">
+ where <code class="command"><em
class="replaceable"><code>name</code></em> </code>
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>Prev</strong>6.2.3. Alias
and Clone Files</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-networkscripts-interfaces-other.html"><strong>Next</strong>6.2.5. Other
Interfaces</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-openssh-useful-websites.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-openssh-useful-websites.html
new file mode 100644
index 0000000..f9a5d8f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-openssh-useful-websites.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>9.5.2. Useful Websites</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-openssh-additional-resources.html" title="9.5. Additional
Resources" /><link rel="prev"
href="s1-openssh-additional-resources.html" title="9.5. Additional
Resources" /><link rel="next" href="part-Servers.html"
title="Part V. Servers" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-openssh-additional-resources.html"><strong>Prev</strong></a></li><li
class="next">
<a accesskey="n"
href="part-Servers.html"><strong>Next</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"
id="s2-openssh-useful-websites">9.5.2. Useful
Websites</h3></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
href="http://www.openssh.com/">http://www.openssh.com/</a...
class="para">
+ The OpenSSH home page containing further documentation, frequently asked
questions, links to the mailing lists, bug reports, and other useful resources.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.openssl.org/">http://www.openssl.org/</a...
class="para">
+ The OpenSSL home page containing further documentation, frequently asked
questions, links to the mailing lists, and other useful resources.
+ </div></dd><dt class="varlistentry"><span
class="term"><a
href="http://www.freesshd.com/">http://www.freesshd.com/<...
class="para">
+ Another implementation of an SSH server.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-openssh-additional-resources.html"><strong>Prev</strong>9.5. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="part-Servers.html"><strong>Next</strong>Part V. Servers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-cmdline.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-cmdline.html
new file mode 100644
index 0000000..bef3ec6
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-cmdline.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="next" href="s2-proc-cpuinfo.html"
title="C.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>Prev</strong></a></li><li
clas
s="next"><a accesskey="n"
href="s2-proc-cpuinfo.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-cmdline"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-cmdline">C.2.2. /proc/cmdline
</h3></div></div></div><a id="id483645"
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:/...;.
+ </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>Prev</strong>C.2. Top-level
Files within the proc File System</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-cpuinfo.html"><strong>Next</strong>C.2.3.
/proc/cpuinfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-cpuinfo.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-cpuinfo.html
new file mode 100644
index 0000000..7598b99
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-cpuinfo.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-cmdline.html"
title="C.2.2. /proc/cmdline" /><link rel="next"
href="s2-proc-crypto.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href=
"s2-proc-crypto.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-cpuinfo"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-cpuinfo">C.2.3. /proc/cpuinfo
</h3></div></div></div><a id="id470602"
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>Prev</strong>C.2.2.
/proc/cmdline </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-crypto.html"><strong>Next</strong>C.2.4.
/proc/crypto </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-crypto.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-crypto.html
new file mode 100644
index 0000000..28743bf
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-crypto.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.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-cpuinfo.html"
title="C.2.3. /proc/cpuinfo" /><link rel="next"
href="s2-proc-devices.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" hre
f="s2-proc-devices.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-crypto"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-crypto">C.2.4. /proc/crypto
</h3></div></div></div><a id="id554101"
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>Prev</strong>C.2.3.
/proc/cpuinfo </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-devices.html"><strong>Next</strong>C.2.5.
/proc/devices </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-devices.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-devices.html
new file mode 100644
index 0000000..db1f65c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-devices.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-crypto.html"
title="C.2.4. /proc/crypto" /><link rel="next"
href="s2-proc-dma.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-proc-
dma.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-devices"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-devices">C.2.5. /proc/devices
</h3></div></div></div><a id="id467865"
class="indexterm"></a><a id="id467891"
class="indexterm"></a><a id="id543596"
class="indexterm"></a><a id="id543610"
class="indexterm"></a><a id="id543627"
class="indexterm"></a><a id="id543645"
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>Prev</strong>C.2.4.
/proc/crypto </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dma.html"><strong>Next</strong>C.2.6. /proc/dma
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-bus.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-bus.html
new file mode 100644
index 0000000..080021e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-bus.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s1-proc-directories.html"
title="C.3. Directories within /proc/" /><link rel="next"
href="s2-proc-pci.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href=
"s2-proc-pci.html"><strong>Next</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"
id="s2-proc-dir-bus">C.3.2. /proc/bus/
</h3></div></div></div><a id="id543731"
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>Prev</strong>C.3. Directories
within /proc/</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-pci.html"><strong>Next</strong>C.3.3.
/proc/bus/pci </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-driver.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-driver.html
new file mode 100644
index 0000000..5446a17
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-driver.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-pci.html" title="C.3.3.
/proc/bus/pci" /><link rel="next"
href="s2-proc-dir-fs.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-fs.html"><stro
ng>Next</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"
id="s2-proc-dir-driver">C.3.4. /proc/driver/
</h3></div></div></div><a id="id623027"
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>Prev</strong>C.3.3.
/proc/bus/pci </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-fs.html"><strong>Next</strong>C.3.5. /proc/fs
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-fs.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-fs.html
new file mode 100644
index 0000000..10fa36e
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-fs.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-dir-driver.html"
title="C.3.4. /proc/driver/" /><link rel="next"
href="s2-proc-dir-irq.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-proc-d
ir-irq.html"><strong>Next</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"
id="s2-proc-dir-fs">C.3.5. /proc/fs
</h3></div></div></div><a id="id469767"
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>Prev</strong>C.3.4.
/proc/driver/ </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-irq.html"><strong>Next</strong>C.3.6.
/proc/irq/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-irq.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-irq.html
new file mode 100644
index 0000000..5325344
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-irq.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-dir-fs.html"
title="C.3.5. /proc/fs" /><link rel="next"
href="s2-proc-dir-net.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-net.html">
<strong>Next</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"
id="s2-proc-dir-irq">C.3.6. /proc/irq/
</h3></div></div></div><a id="id469820"
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>Prev</strong>C.3.5. /proc/fs
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-net.html"><strong>Next</strong>C.3.7.
/proc/net/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-net.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-net.html
new file mode 100644
index 0000000..3a269f0
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-net.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-dir-irq.html"
title="C.3.6. /proc/irq/" /><link rel="next"
href="s2-proc-dir-scsi.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-proc-dir-scsi
.html"><strong>Next</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"
id="s2-proc-dir-net">C.3.7. /proc/net/
</h3></div></div></div><a id="id639553"
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>Prev</strong>C.3.6.
/proc/irq/ </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-scsi.html"><strong>Next</strong>C.3.8.
/proc/scsi/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-scsi.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-scsi.html
new file mode 100644
index 0000000..16d0ccd
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-scsi.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-dir-net.html"
title="C.3.7. /proc/net/" /><link rel="next"
href="s2-proc-dir-sys.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-proc-dir-sys.ht
ml"><strong>Next</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"
id="s2-proc-dir-scsi">C.3.8. /proc/scsi/
</h3></div></div></div><a id="id612467"
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>Prev</strong>C.3.7.
/proc/net/ </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-sys.html"><strong>Next</strong>C.3.9.
/proc/sys/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-sys.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-sys.html
new file mode 100644
index 0000000..296eed5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-sys.html
@@ -0,0 +1,333 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-dir-scsi.html"
title="C.3.8. /proc/scsi/" /><link rel="next"
href="s2-proc-dir-sysvipc.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-pro
c-dir-sysvipc.html"><strong>Next</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"
id="s2-proc-dir-sys">C.3.9. /proc/sys/
</h3></div></div></div><a id="id551832"
class="indexterm"></a><a id="id551854"
class="indexterm"></a><a id="id468766"
class="indexterm"></a><a id="id468796"
class="indexterm"></a><a id="id468815"
class="indexterm"></a><a id="id468829"
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">Section C.4,
“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"
id="s3-proc-sys-dev">C.3.9.1. /proc/sys/dev/
</h4></div></div></div><a id="id627924"
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"
id="s3-proc-sys-fs">C.3.9.2. /proc/sys/fs/
</h4></div></div></div><a id="id630285"
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"
id="s3-proc-sys-kernel">C.3.9.3. /proc/sys/kernel/
</h4></div></div></div><a id="id479568"
class="indexterm"></a><a id="id479599"
class="indexterm"></a><a id="id479613"
class="indexterm"></a><a id="id479632"
class="indexterm"></a><a id="id479650"
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, in bytes. 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, in bytes. 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"
id="s3-proc-sys-net">C.3.9.4. /proc/sys/net/
</h4></div></div></div><a id="id669978"
class="indexterm"></a><a id="id670008"
class="indexterm"></a><a id="id469573"
class="indexterm"></a><a id="id469587"
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"
id="s3-proc-sys-vm">C.3.9.5. /proc/sys/vm/
</h4></div></div></div><a id="id468502"
class="indexterm"></a><a id="id468533"
class="indexterm"></a><a id="id468548"
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>Prev</strong>C.3.8.
/proc/scsi/ </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-sysvipc.html"><strong>Next</strong>C.3.10.
/proc/sysvipc/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-sysvipc.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-sysvipc.html
new file mode 100644
index 0000000..7737bd6
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dir-sysvipc.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-dir-sys.html"
title="C.3.9. /proc/sys/" /><link rel="next"
href="s2-proc-tty.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-tty.html"><st
rong>Next</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"
id="s2-proc-dir-sysvipc">C.3.10. /proc/sysvipc/
</h3></div></div></div><a id="id468720"
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>Prev</strong>C.3.9.
/proc/sys/ </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-tty.html"><strong>Next</strong>C.3.11. /proc/tty/
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dma.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dma.html
new file mode 100644
index 0000000..8b234e8
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-dma.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-devices.html"
title="C.2.5. /proc/devices" /><link rel="next"
href="s2-proc-execdomains.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey
="n"
href="s2-proc-execdomains.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-dma"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-dma">C.2.6. /proc/dma
</h3></div></div></div><a id="id591248"
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>Prev</strong>C.2.5.
/proc/devices </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-execdomains.html"><strong>Next</strong>C.2.7.
/proc/execdomains </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-execdomains.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-execdomains.html
new file mode 100644
index 0000000..6f6f462
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-execdomains.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>C.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-dma.html"
title="C.2.6. /proc/dma" /><link rel="next"
href="s2-proc-fb.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-fb.html"><s
trong>Next</strong></a></li></ul><div
class="section" id="s2-proc-execdomains"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-execdomains">C.2.7. /proc/execdomains
</h3></div></div></div><a id="id591291"
class="indexterm"></a><a id="id676178"
class="indexterm"></a><a id="id676195"
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>Prev</strong>C.2.6. /proc/dma
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-fb.html"><strong>Next</strong>C.2.8. /proc/fb
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-fb.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-fb.html
new file mode 100644
index 0000000..38a3297
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-fb.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev"
href="s2-proc-execdomains.html" title="C.2.7. /proc/execdomains"
/><link rel="next" href="s2-proc-filesystems.html"
title="C.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>Prev</strong></a></li><li
class="next">
<a accesskey="n"
href="s2-proc-filesystems.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-fb"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-fb">C.2.8. /proc/fb
</h3></div></div></div><a id="id639037"
class="indexterm"></a><a id="id639059"
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>Prev</strong>C.2.7.
/proc/execdomains </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-filesystems.html"><strong>Next</strong>C.2.9.
/proc/filesystems </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-filesystems.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-filesystems.html
new file mode 100644
index 0000000..3d5ebc5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-filesystems.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>C.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-fb.html"
title="C.2.8. /proc/fb" /><link rel="next"
href="s2-proc-interrupts.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-pr
oc-interrupts.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-filesystems"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-filesystems">C.2.9. /proc/filesystems
</h3></div></div></div><a id="id649109"
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>Prev</strong>C.2.8. /proc/fb
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-interrupts.html"><strong>Next</strong>C.2.10.
/proc/interrupts </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-interrupts.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-interrupts.html
new file mode 100644
index 0000000..0d39c76
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-interrupts.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>C.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev"
href="s2-proc-filesystems.html" title="C.2.9. /proc/filesystems"
/><link rel="next" href="s2-proc-iomem.html"
title="C.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>Prev</strong></a></li><li
class="next"><a accesske
y="n"
href="s2-proc-iomem.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-interrupts"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-interrupts">C.2.10. /proc/interrupts
</h3></div></div></div><a id="id649172"
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>Prev</strong>C.2.9.
/proc/filesystems </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-iomem.html"><strong>Next</strong>C.2.11.
/proc/iomem </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-iomem.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-iomem.html
new file mode 100644
index 0000000..068a6a5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-iomem.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev"
href="s2-proc-interrupts.html" title="C.2.10. /proc/interrupts"
/><link rel="next" href="s2-proc-ioports.html"
title="C.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>Prev</strong></a></li><li
class="next"><a access
key="n"
href="s2-proc-ioports.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-iomem"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-iomem">C.2.11. /proc/iomem
</h3></div></div></div><a id="id641339"
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>Prev</strong>C.2.10.
/proc/interrupts </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-ioports.html"><strong>Next</strong>C.2.12.
/proc/ioports </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-ioports.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-ioports.html
new file mode 100644
index 0000000..92adb84
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-ioports.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-iomem.html"
title="C.2.11. /proc/iomem" /><link rel="next"
href="s2-proc-kcore.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-pr
oc-kcore.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-ioports"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-ioports">C.2.12. /proc/ioports
</h3></div></div></div><a id="id569935"
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>Prev</strong>C.2.11.
/proc/iomem </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-kcore.html"><strong>Next</strong>C.2.13.
/proc/kcore </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-kcore.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-kcore.html
new file mode 100644
index 0000000..d620606
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-kcore.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-ioports.html"
title="C.2.12. /proc/ioports" /><link rel="next"
href="s2-proc-kmsg.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s
2-proc-kmsg.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-kcore"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-kcore">C.2.13. /proc/kcore
</h3></div></div></div><a id="id642423"
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>Prev</strong>C.2.12.
/proc/ioports </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-kmsg.html"><strong>Next</strong>C.2.14. /proc/kmsg
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-kmsg.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-kmsg.html
new file mode 100644
index 0000000..b50645c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-kmsg.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-kcore.html"
title="C.2.13. /proc/kcore" /><link rel="next"
href="s2-proc-loadavg.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s
2-proc-loadavg.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-kmsg"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-kmsg">C.2.14. /proc/kmsg
</h3></div></div></div><a id="id676438"
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>Prev</strong>C.2.13.
/proc/kcore </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-loadavg.html"><strong>Next</strong>C.2.15.
/proc/loadavg </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-loadavg.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-loadavg.html
new file mode 100644
index 0000000..0aede5c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-loadavg.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-kmsg.html"
title="C.2.14. /proc/kmsg" /><link rel="next"
href="s2-proc-locks.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-proc-
locks.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-loadavg"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-loadavg">C.2.15. /proc/loadavg
</h3></div></div></div><a id="id676084"
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>Prev</strong>C.2.14. /proc/kmsg
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-locks.html"><strong>Next</strong>C.2.16.
/proc/locks </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-locks.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-locks.html
new file mode 100644
index 0000000..bf78c11
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-locks.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-loadavg.html"
title="C.2.15. /proc/loadavg" /><link rel="next"
href="s2-proc-mdstat.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" hre
f="s2-proc-mdstat.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-locks"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-locks">C.2.16. /proc/locks
</h3></div></div></div><a id="id668443"
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>Prev</strong>C.2.15.
/proc/loadavg </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-mdstat.html"><strong>Next</strong>C.2.17.
/proc/mdstat </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mdstat.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mdstat.html
new file mode 100644
index 0000000..e890eaf
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mdstat.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-locks.html"
title="C.2.16. /proc/locks" /><link rel="next"
href="s2-proc-meminfo.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s
2-proc-meminfo.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-mdstat"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-mdstat">C.2.17. /proc/mdstat
</h3></div></div></div><a id="id675626"
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>Prev</strong>C.2.16.
/proc/locks </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-meminfo.html"><strong>Next</strong>C.2.18.
/proc/meminfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-meminfo.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-meminfo.html
new file mode 100644
index 0000000..33dedc7
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-meminfo.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-mdstat.html"
title="C.2.17. /proc/mdstat" /><link rel="next"
href="s2-proc-misc.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-p
roc-misc.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-meminfo"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-meminfo">C.2.18. /proc/meminfo
</h3></div></div></div><a id="id669861"
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>Prev</strong>C.2.17.
/proc/mdstat </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-misc.html"><strong>Next</strong>C.2.19. /proc/misc
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-misc.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-misc.html
new file mode 100644
index 0000000..2412467
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-misc.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-meminfo.html"
title="C.2.18. /proc/meminfo" /><link rel="next"
href="s2-proc-modules.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" h
ref="s2-proc-modules.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-misc"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-misc">C.2.19. /proc/misc
</h3></div></div></div><a id="id675683"
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>Prev</strong>C.2.18.
/proc/meminfo </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-modules.html"><strong>Next</strong>C.2.20.
/proc/modules </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-modules.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-modules.html
new file mode 100644
index 0000000..0079cc2
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-modules.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-misc.html"
title="C.2.19. /proc/misc" /><link rel="next"
href="s2-proc-mounts.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-pro
c-mounts.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-modules"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-modules">C.2.20. /proc/modules
</h3></div></div></div><a id="id675730"
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>Prev</strong>C.2.19. /proc/misc
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-mounts.html"><strong>Next</strong>C.2.21.
/proc/mounts </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mounts.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mounts.html
new file mode 100644
index 0000000..01c7bc6
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mounts.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-modules.html"
title="C.2.20. /proc/modules" /><link rel="next"
href="s2-proc-mtrr.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s
2-proc-mtrr.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-mounts"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-mounts">C.2.21. /proc/mounts
</h3></div></div></div><a id="id546312"
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>Prev</strong>C.2.20.
/proc/modules </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-mtrr.html"><strong>Next</strong>C.2.22. /proc/mtrr
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mtrr.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mtrr.html
new file mode 100644
index 0000000..7e9d88c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-mtrr.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.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-mounts.html"
title="C.2.21. /proc/mounts" /><link rel="next"
href="s2-proc-partitions.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n
"
href="s2-proc-partitions.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-mtrr"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-mtrr">C.2.22. /proc/mtrr
</h3></div></div></div><a id="id472508"
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>Prev</strong>C.2.21.
/proc/mounts </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-partitions.html"><strong>Next</strong>C.2.23.
/proc/partitions </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-partitions.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-partitions.html
new file mode 100644
index 0000000..544cfa2
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-partitions.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.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-mtrr.html"
title="C.2.22. /proc/mtrr" /><link rel="next"
href="s2-proc-slabinfo.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2
-proc-slabinfo.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-partitions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-partitions">C.2.23. /proc/partitions
</h3></div></div></div><a id="id621875"
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>Prev</strong>C.2.22. /proc/mtrr
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-slabinfo.html"><strong>Next</strong>C.2.24.
/proc/slabinfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-pci.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-pci.html
new file mode 100644
index 0000000..0171497
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-pci.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-dir-bus.html"
title="C.3.2. /proc/bus/" /><link rel="next"
href="s2-proc-dir-driver.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-proc-dir-
driver.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-pci"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-pci">C.3.3. /proc/bus/pci
</h3></div></div></div><a id="id470847"
class="indexterm"></a><a id="id470878"
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">[output truncated]</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>Prev</strong>C.3.2.
/proc/bus/ </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-dir-driver.html"><strong>Next</strong>C.3.4.
/proc/driver/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-pid.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-pid.html
new file mode 100644
index 0000000..8314cef
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-pid.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-tty.html" title="C.3.11.
/proc/tty/" /><link rel="next" href="s1-proc-sysctl.html"
title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s1-proc-sysctl.
html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-pid"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-pid">C.3.12. /proc/<em
class="replaceable"><code>PID</code></em>/
</h3></div></div></div><a id="id470108"
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>Prev</strong>C.3.11. /proc/tty/
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-proc-sysctl.html"><strong>Next</strong>C.4. Using the
sysctl Command</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-slabinfo.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-slabinfo.html
new file mode 100644
index 0000000..5fd3ea2
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-slabinfo.html
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev"
href="s2-proc-partitions.html" title="C.2.23. /proc/partitions"
/><link rel="next" href="s2-proc-stat.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n
"
href="s2-proc-stat.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-slabinfo"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-slabinfo">C.2.24. /proc/slabinfo
</h3></div></div></div><a id="id618802"
class="indexterm"></a><a id="id618825"
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>Prev</strong>C.2.23.
/proc/partitions </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-stat.html"><strong>Next</strong>C.2.25. /proc/stat
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-stat.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-stat.html
new file mode 100644
index 0000000..ef02765
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-stat.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev"
href="s2-proc-slabinfo.html" title="C.2.24. /proc/slabinfo"
/><link rel="next" href="s2-proc-swaps.html"
title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" hr
ef="s2-proc-swaps.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-stat"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-stat">C.2.25. /proc/stat
</h3></div></div></div><a id="id677115"
class="indexterm"></a><a id="id677138"
class="indexterm"></a><a id="id677152"
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>Prev</strong>C.2.24.
/proc/slabinfo </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-swaps.html"><strong>Next</strong>C.2.26.
/proc/swaps </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-swaps.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-swaps.html
new file mode 100644
index 0000000..46dfdbb
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-swaps.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.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-stat.html"
title="C.2.25. /proc/stat" /><link rel="next"
href="s2-proc-sysrq-trigger.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n
"
href="s2-proc-sysrq-trigger.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-swaps"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-swaps">C.2.26. /proc/swaps
</h3></div></div></div><a id="id676989"
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>Prev</strong>C.2.25. /proc/stat
</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-sysrq-trigger.html"><strong>Next</strong>C.2.27.
/proc/sysrq-trigger </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-sysrq-trigger.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-sysrq-trigger.html
new file mode 100644
index 0000000..937673b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-sysrq-trigger.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-swaps.html"
title="C.2.26. /proc/swaps" /><link rel="next"
href="s2-proc-uptime.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-
proc-uptime.html"><strong>Next</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"
id="s2-proc-sysrq-trigger">C.2.27. /proc/sysrq-trigger
</h3></div></div></div><a id="id677050"
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">Section C.3.9.3, “
/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>Prev</strong>C.2.26.
/proc/swaps </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-uptime.html"><strong>Next</strong>C.2.28.
/proc/uptime </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-tty.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-tty.html
new file mode 100644
index 0000000..b77b8a3
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-tty.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-directories.html" title="C.3. Directories within /proc/"
/><link rel="prev" href="s2-proc-dir-sysvipc.html"
title="C.3.10. /proc/sysvipc/" /><link rel="next"
href="s2-proc-pid.html" title="C.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-proc-
pid.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-tty"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-tty">C.3.11. /proc/tty/
</h3></div></div></div><a id="id640568"
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>Prev</strong>C.3.10.
/proc/sysvipc/ </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-pid.html"><strong>Next</strong>C.3.12. /proc/PID/
</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-uptime.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-uptime.html
new file mode 100644
index 0000000..5818043
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-uptime.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev"
href="s2-proc-sysrq-trigger.html" title="C.2.27. /proc/sysrq-trigger"
/><link rel="next" href="s2-proc-version.html"
title="C.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>Prev</strong></a></li><li
class="next">
<a accesskey="n"
href="s2-proc-version.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-uptime"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-uptime">C.2.28. /proc/uptime
</h3></div></div></div><a id="id676026"
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>Prev</strong>C.2.27.
/proc/sysrq-trigger </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-proc-version.html"><strong>Next</strong>C.2.29.
/proc/version </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-version.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-version.html
new file mode 100644
index 0000000..e33aa97
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-proc-version.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>C.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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-proc-topfiles.html" title="C.2. Top-level Files within the proc
File System" /><link rel="prev" href="s2-proc-uptime.html"
title="C.2.28. /proc/uptime" /><link rel="next"
href="s1-proc-directories.html" title="C.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>Prev</strong></a></li><li
class="next"><a access
key="n"
href="s1-proc-directories.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-proc-version"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-proc-version">C.2.29. /proc/version
</h3></div></div></div><a id="id469147"
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(a)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>Prev</strong>C.2.28.
/proc/uptime </a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-proc-directories.html"><strong>Next</strong>C.3. Directories
within /proc/</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-group-new.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-group-new.html
new file mode 100644
index 0000000..a0740a0
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-group-new.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>3.2.2. Adding a New Group</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-users-configui.html" title="3.2. User Manager Tool"
/><link rel="prev" href="s1-users-configui.html"
title="3.2. User Manager Tool" /><link rel="next"
href="s2-redhat-config-users-group-properties.html" title="3.2.3. Modifying
Group Properties" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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.html"><strong>Prev</strong></a></li><li
class="next"><a a
ccesskey="n"
href="s2-redhat-config-users-group-properties.html"><strong>Next</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"
id="s2-redhat-config-users-group-new">3.2.2. Adding a New
Group</h3></div></div></div><a id="id536901"
class="indexterm"></a><div class="para">
+ To add a new user group, select <span
class="guibutton"><strong>Add Group</strong></span> from
the toolbar. A window similar to <a class="xref"
href="s2-redhat-config-users-group-new.html#group-new-fig">Figure 3.8, “New
Group”</a> appears. Type the name of the new group. To specify a group ID for the
new group, select <span class="guilabel"><strong>Specify group ID
manually</strong></span> and select the GID. Note that Fedora also reserves
group IDs lower than 500 for system groups.
+ </div><div class="figure" id="group-new-fig"><div
class="figure-contents"><div class="mediaobject"><img
src="images/user-manager-add-group.png" alt="New Group" /><div
class="longdesc"><div class="para">
+ Creating a new group
+ </div></div></div></div><h6>Figure 3.8. New
Group</h6></div><br class="figure-break" /><div
class="para">
+ Click <span
class="guibutton"><strong>OK</strong></span> to create the
group. The new group appears in the group list.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-users-configui.html"><strong>Prev</strong>3.2. User
Manager Tool</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-redhat-config-users-group-properties.html"><strong>Next</strong>3.2.3. Modifying
Group Properties</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-group-properties.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-group-properties.html
new file mode 100644
index 0000000..27a808b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-group-properties.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>3.2.3. Modifying Group Properties</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-users-configui.html" title="3.2. User Manager Tool"
/><link rel="prev" href="s2-redhat-config-users-group-new.html"
title="3.2.2. Adding a New Group" /><link rel="next"
href="s1-users-tools.html" title="3.3. User and Group Management
Tools" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class=
"next"><a accesskey="n"
href="s1-users-tools.html"><strong>Next</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"
id="s2-redhat-config-users-group-properties">3.2.3. Modifying Group
Properties</h3></div></div></div><a id="id536978"
class="indexterm"></a><div class="para">
+ To view the properties of an existing group, select the group from the group list and
click <span
class="guimenuitem"><strong>Properties</strong></span> from
the menu (or choose <span
class="guimenu"><strong>File</strong></span> → <span
class="guimenuitem"><strong>Properties</strong></span> from
the pulldown menu). A window similar to <a class="xref"
href="s2-redhat-config-users-group-properties.html#group-properties-fig">Figure 3.9,
“Group Properties”</a> appears.
+ </div><div class="figure"
id="group-properties-fig"><div
class="figure-contents"><div class="mediaobject"><img
src="images/user-manager-edit-group.png" alt="Group Properties"
/><div class="longdesc"><div class="para">
+ Modifying group properties
+ </div></div></div></div><h6>Figure 3.9. Group
Properties</h6></div><br class="figure-break" /><a
id="id537042" class="indexterm"></a><div
class="para">
+ The <span class="guilabel"><strong>Group
Users</strong></span> tab displays which users are members of the group. Use
this tab to add or remove users from the group. Click <span
class="guibutton"><strong>OK</strong></span> to save your
changes.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-redhat-config-users-group-new.html"><strong>Prev</strong>3.2.2. Adding
a New Group</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-tools.html"><strong>Next</strong>3.3. User and
Group Management Tools</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-process.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-process.html
new file mode 100644
index 0000000..15865e7
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-redhat-config-users-process.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>3.3.2. Explaining the Process</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-users-tools.html" title="3.3. User and Group Management
Tools" /><link rel="prev" href="s1-users-tools.html"
title="3.3. User and Group Management Tools" /><link rel="next"
href="s1-users-groups-standard-users.html" title="3.4. Standard Users"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a acces
skey="n"
href="s1-users-groups-standard-users.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-redhat-config-users-process"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-redhat-config-users-process">3.3.2. Explaining the
Process</h3></div></div></div><div class="para">
+ The following steps illustrate what happens if the command <code
class="command">useradd juan</code> is issued on a system that has
shadow passwords enabled:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ A new line for <code class="systemitem">juan</code> is
created in <code class="filename">/etc/passwd</code>:
+ </div><pre
class="screen">juan:x:501:501::/home/juan:/bin/bash</pre><div
class="para">
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the username <code
class="literal">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ There is an <code class="literal">x</code> for the password
field indicating that the system is using shadow passwords.
+ </div></li><li class="listitem"><div
class="para">
+ A UID greater than 499 is created. Under Fedora, UIDs and GIDs below 500 are
reserved for system use. These should not be assigned to users.
+ </div></li><li class="listitem"><div
class="para">
+ A GID greater than 499 is created.
+ </div></li><li class="listitem"><div
class="para">
+ The optional GECOS information is left blank.
+ </div></li><li class="listitem"><div
class="para">
+ The home directory for <code class="systemitem">juan</code>
is set to <code class="filename">/home/juan/</code>.
+ </div></li><li class="listitem"><div
class="para">
+ The default shell is set to <code
class="command">/bin/bash</code>.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ A new line for <code class="systemitem">juan</code> is
created in <code class="filename">/etc/shadow</code>:
+ </div><pre
class="screen">juan:!!:14798:0:99999:7:::</pre><div
class="para">
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the username <code
class="systemitem">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ Two exclamation marks (<code class="literal">!!</code>)
appear in the password field of the <code
class="filename">/etc/shadow</code> file, which locks the account.
+ </div><div class="note"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ If an encrypted password is passed using the <code
class="option">-p</code> flag, it is placed in the <code
class="filename">/etc/shadow</code> file on the new line for the user.
+ </div></div></div></li><li
class="listitem"><div class="para">
+ The password is set to never expire.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ A new line for a group named <code
class="systemitem">juan</code> is created in <code
class="filename">/etc/group</code>:
+ </div><pre class="screen">juan:x:501:</pre><div
class="para">
+ A group with the same name as a user is called a <em
class="firstterm">user private group</em>. For more information on user
private groups, refer to <a class="xref"
href="s1-users-configui.html#s2-redhat-config-users-user-new">Section 3.2.1,
“Adding a New User”</a>.
+ </div><div class="para">
+ The line created in <code class="filename">/etc/group</code>
has the following characteristics:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the group name <code
class="systemitem">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ An <code class="literal">x</code> appears in the password
field indicating that the system is using shadow group passwords.
+ </div></li><li class="listitem"><div
class="para">
+ The GID matches the one listed for user <code
class="systemitem">juan</code> in <code
class="filename">/etc/passwd</code>.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ A new line for a group named <code
class="systemitem">juan</code> is created in <code
class="filename">/etc/gshadow</code>:
+ </div><pre class="screen">juan:!::</pre><div
class="para">
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ It begins with the group name <code
class="systemitem">juan</code>.
+ </div></li><li class="listitem"><div
class="para">
+ An exclamation mark (<code class="literal">!</code>)
appears in the password field of the <code
class="filename">/etc/gshadow</code> file, which locks the group.
+ </div></li><li class="listitem"><div
class="para">
+ All other fields are blank.
+ </div></li></ul></div></li><li
class="step"><div class="para">
+ A directory for user <code class="systemitem">juan</code> is
created in the <code class="filename">/home/</code> directory:
+ </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">
+ This directory is owned by user <code
class="systemitem">juan</code> and group <code
class="systemitem">juan</code>. It has <em
class="firstterm">read</em>, <em
class="firstterm">write</em>, and <em
class="firstterm">execute</em> privileges <span
class="emphasis"><em>only</em></span> for the user <code
class="systemitem">juan</code>. All other permissions are denied.
+ </div></li><li class="step"><div
class="para">
+ The files within the <code class="filename">/etc/skel/</code>
directory (which contain default user settings) are copied into the new <code
class="filename">/home/juan/</code> directory:
+ </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">
+ At this point, a locked account called <code
class="systemitem">juan</code> exists on the system. To activate it,
the administrator must next assign a password to the account using the <code
class="command">passwd</code> command and, optionally, set password
aging guidelines.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-users-tools.html"><strong>Prev</strong>3.3. User and
Group Management Tools</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-users-groups-standard-users.html"><strong>Next</strong>3.4. Standard
Users</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-freshening.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-freshening.html
new file mode 100644
index 0000000..59c987f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-freshening.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>A.2.5. Freshening</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-rpm-using.html" title="A.2. Using RPM" /><link
rel="prev" href="s2-rpm-uninstalling.html"
title="A.2.4. Uninstalling" /><link rel="next"
href="s2-rpm-querying.html" title="A.2.6. Querying"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-querying.html"><strong>Next<
/strong></a></li></ul><div class="section"
id="s2-rpm-freshening"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-rpm-freshening">A.2.5. Freshening</h3></div></div></div><a
id="id600903" class="indexterm"></a><a
id="id573379" 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.fc15.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>Prev</strong>A.2.4. Uninstalling</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-querying.html"><strong>Next</strong>A.2.6. Querying</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-querying.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-querying.html
new file mode 100644
index 0000000..6c5efe7
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-querying.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>A.2.6. Querying</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-rpm-using.html" title="A.2. Using RPM" /><link
rel="prev" href="s2-rpm-freshening.html"
title="A.2.5. Freshening" /><link rel="next"
href="s2-rpm-verifying.html" title="A.2.7. Verifying"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-verifying.html"><strong>Next</st
rong></a></li></ul><div class="section"
id="s2-rpm-querying"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-rpm-querying">A.2.6. Querying</h3></div></div></div><a
id="id608435" class="indexterm"></a><a
id="id608447" 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.fc15.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> — queries all currently
installed packages.
+ </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>Prev</strong>A.2.5. Freshening</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-verifying.html"><strong>Next</strong>A.2.7. Verifying</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-related-books.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-related-books.html
new file mode 100644
index 0000000..3e435a5
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-related-books.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>A.5.3. Related Books</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-rpm-additional-resources.html" title="A.5. Additional
Resources" /><link rel="prev"
href="s2-rpm-useful-websites.html" title="A.5.2. Useful Websites"
/><link rel="next" href="ch-The_sysconfig_Directory.html"
title="Appendix B. The 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-rpm-useful-websites.html"><strong>Prev</strong></a></li><li
clas
s="next"><a accesskey="n"
href="ch-The_sysconfig_Directory.html"><strong>Next</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"
id="s2-rpm-related-books">A.5.3. Related
Books</h3></div></div></div><a id="id566305"
class="indexterm"></a><div
class="variablelist"><dl><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-rp...
</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>Prev</strong>A.5.2. Useful
Websites</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-The_sysconfig_Directory.html"><strong>Next</strong>Appendix B. The
sysconfig Directory</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-uninstalling.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-uninstalling.html
new file mode 100644
index 0000000..4cac959
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-uninstalling.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.2.4. Uninstalling</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-rpm-using.html" title="A.2. Using RPM" /><link
rel="prev" href="sec-Configuration_File_Changes.html"
title="A.2.3. Configuration File Changes" /><link rel="next"
href="s2-rpm-freshening.html" title="A.2.5. Freshening"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" h
ref="s2-rpm-freshening.html"><strong>Next</strong></a></li></ul><div
class="section" id="s2-rpm-uninstalling"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-rpm-uninstalling">A.2.4. Uninstalling</h3></div></div></div><a
id="id433395" class="indexterm"></a><a
id="id433407" class="indexterm"></a><a
id="id433419" class="indexterm"></a><a
id="id543324" class="indexterm"></a><div
class="para">
+ Uninstalling a package is just as simple as installing one. Type the following
command at a shell prompt:
+ </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.fc15.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.fc15.x86_64
+ libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc15.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc15.x86_64
+ ghostscript is needed by (installed)
printer-filters-1.1-4.fc15.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">Section A.2.2.3,
“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.fc15.x86_64</pre><div class="warning"
id="warning-uninstall-Warning-Forcing_Package_Installation"><div
class="admonition_header"><h2>Warning: Forcing Package
Installation</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>Prev</strong>A.2.3. Configuration
File Changes</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-freshening.html"><strong>Next</strong>A.2.5. Freshening</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-useful-websites.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-useful-websites.html
new file mode 100644
index 0000000..3038643
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-useful-websites.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>A.5.2. Useful Websites</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-rpm-additional-resources.html" title="A.5. Additional
Resources" /><link rel="prev"
href="s1-rpm-additional-resources.html" title="A.5. Additional
Resources" /><link rel="next"
href="s2-rpm-related-books.html" title="A.5.3. Related Books"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next">
<a accesskey="n"
href="s2-rpm-related-books.html"><strong>Next</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"
id="s2-rpm-useful-websites">A.5.2. Useful
Websites</h3></div></div></div><div
class="itemizedlist"><a id="id445475"
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/">http...
+ </div></li></ul></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-rpm-additional-resources.html"><strong>Prev</strong>A.5. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-related-books.html"><strong>Next</strong>A.5.3. Related
Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-verifying.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-verifying.html
new file mode 100644
index 0000000..ffa96a1
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-rpm-verifying.html
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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.7. Verifying</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-rpm-using.html" title="A.2. Using RPM" /><link
rel="prev" href="s2-rpm-querying.html"
title="A.2.6. Querying" /><link rel="next"
href="s1-check-rpm-sig.html" title="A.3. Checking a Package's
Signature" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-check-rpm-sig.html"><st
rong>Next</strong></a></li></ul><div
class="section" id="s2-rpm-verifying"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="s2-rpm-verifying">A.2.7. Verifying</h3></div></div></div><a
id="id625000" class="indexterm"></a><a
id="id573662" 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">
+ To verify a package containing a particular file:
+ </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">
+ To verify an installed package against an RPM package file:
+ </div><pre class="screen">
+<code class="command">rpm -Vp
tree-1.5.2.2-4.fc15.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 checksum
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">S</code> — file size
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">L</code> — symbolic link
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">T</code> — file modification
time
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">D</code> — device
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">U</code> — user
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">G</code> — group
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">M</code> — mode (includes
permissions and file type)
+ </div></li><li class="listitem"><div
class="para">
+ <code class="computeroutput">?</code> — unreadable file (file
permission errors, for example)
+ </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>Prev</strong>A.2.6. Querying</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-check-rpm-sig.html"><strong>Next</strong>A.3. Checking a
Package's Signature</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-services-additional-resources-books.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-services-additional-resources-books.html
new file mode 100644
index 0000000..fa4e620
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-services-additional-resources-books.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>7.3.2. Related Books</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-services-additional-resources.html" title="7.3. Additional
Resources" /><link rel="prev"
href="s1-services-additional-resources.html" title="7.3. Additional
Resources" /><link rel="next"
href="ch-Configuring_Authentication.html" title="Chapter 8. Configuring
Authentication" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-services-additional-resources.html"><stro
ng>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="ch-Configuring_Authentication.html"><strong>Next</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"
id="s2-services-additional-resources-books">7.3.2. Related
Books</h3></div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <em
class="citetitle">Security Guide</em>
</span></dt><dd><div class="para">
+ A guide to securing Fedora. It contains valuable information on how to set up the
firewall, as well as the configuration of <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>Prev</strong>7.3. Additional
Resources</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Configuring_Authentication.html"><strong>Next</strong>Chapter 8. Configuring
Authentication</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.html
new file mode 100644
index 0000000..9132a68
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.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>9.4.2. Port Forwarding</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-ssh-beyondshell.html" title="9.4. More Than a Secure Shell"
/><link rel="prev" href="s1-ssh-beyondshell.html"
title="9.4. More Than a Secure Shell" /><link rel="next"
href="s1-openssh-additional-resources.html" title="9.5. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ssh-beyondshell.html"><strong>Prev</strong></a></li><li
class="next"><a
accesskey="n"
href="s1-openssh-additional-resources.html"><strong>Next</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"
id="s2-ssh-beyondshell-tcpip">9.4.2. Port
Forwarding</h3></div></div></div><a id="id616848"
class="indexterm"></a><div class="para">
+ SSH can secure otherwise insecure <code
class="systemitem">TCP/IP</code> protocols via port forwarding. When
using this technique, the SSH server becomes an encrypted conduit to the SSH client.
+ </div><div class="para">
+ Port forwarding works by mapping a local port on the client to a remote port on the
server. SSH can map any port from the server to any port on the client. Port numbers do
not need to match for this technique to work.
+ </div><div class="note"><div
class="admonition_header"><h2>Using reserved port
numbers</h2></div><div class="admonition"><div
class="para">
+ Setting up port forwarding to listen on ports below 1024 requires root level
access.
+ </div></div></div><div class="para">
+ To create a TCP/IP port forwarding channel which listens for connections on the
<code class="systemitem">localhost</code>, use a command in the
following form:
+ </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">
+ For example, to check email on a server called <code
class="systemitem">mail.example.com</code> using <code
class="systemitem">POP3</code> through an encrypted connection, use the
following command:
+ </div><pre class="screen">~]$ <code
class="command">ssh -L 1100:mail.example.com:110
mail.example.com</code></pre><div class="para">
+ Once the port forwarding channel is in place between the client machine and the mail
server, direct a POP3 mail client to use port <code
class="literal">1100</code> on the <code
class="systemitem">localhost</code> to check for new email. Any
requests sent to port <code class="literal">1100</code> on the
client system will be directed securely to the <code
class="systemitem">mail.example.com</code> server.
+ </div><div class="para">
+ If <code class="systemitem">mail.example.com</code> is not
running an SSH server, but another machine on the same network is, SSH can still be used
to secure part of the connection. However, a slightly different command is necessary:
+ </div><pre class="screen">~]$ <code
class="command">ssh -L 1100:mail.example.com:110
other.example.com</code></pre><div class="para">
+ In this example, POP3 requests from port <code
class="literal">1100</code> on the client machine are forwarded through
the SSH connection on port <code class="literal">22</code> to the
SSH server, <code class="systemitem">other.example.com</code>. Then,
<code class="systemitem">other.example.com</code> connects to port
<code class="literal">110</code> on <code
class="systemitem">mail.example.com</code> to check for new email. Note
that when using this technique, only the connection between the client system and <code
class="systemitem">other.example.com</code> SSH server is secure.
+ </div><div class="para">
+ Port forwarding can also be used to get information securely through network
firewalls. If the firewall is configured to allow SSH traffic via its standard port (that
is, port 22) but blocks access to other ports, a connection between two hosts using the
blocked ports is still possible by redirecting their communication over an established SSH
connection.
+ </div><div class="important"><div
class="admonition_header"><h2>A connection is only as secure as a
client system</h2></div><div class="admonition"><div
class="para">
+ Using port forwarding to forward connections in this manner allows any user on the
client system to connect to that service. If the client system becomes compromised, the
attacker also has access to forwarded services.
+ </div><div class="para">
+ System administrators concerned about port forwarding can disable this functionality
on the server by specifying a <code class="option">No</code>
parameter for the <code class="option">AllowTcpForwarding</code>
line in <code class="filename">/etc/ssh/sshd_config</code> and
restarting the <code class="command">sshd</code> service.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-ssh-beyondshell.html"><strong>Prev</strong>9.4. More
Than a Secure Shell</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-openssh-additional-resources.html"><strong>Next</strong>9.5. Additional
Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-clients-scp.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-clients-scp.html
new file mode 100644
index 0000000..b305b39
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-clients-scp.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>9.3.2. Using the scp 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-ssh-clients.html" title="9.3. OpenSSH Clients" /><link
rel="prev" href="s1-ssh-clients.html" title="9.3. OpenSSH
Clients" /><link rel="next" href="s2-ssh-clients-sftp.html"
title="9.3.3. Using the sftp 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="s1-ssh-clients.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-ssh-clients-sft
p.html"><strong>Next</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"
id="s2-ssh-clients-scp">9.3.2. Using the <code
class="command">scp</code>
Utility</h3></div></div></div><a id="id540677"
class="indexterm"></a><a id="id568667"
class="indexterm"></a><a id="id568687"
class="indexterm"></a><div class="para">
+ <code class="command">scp</code> can be used to transfer files
between machines over a secure, encrypted connection. In its design, it is very similar to
<code class="command">rcp</code>.
+ </div><div class="para">
+ To transfer a local file to a remote system, use a command in the following form:
+ </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">
+ For example, if you want to transfer <code
class="filename">taglist.vim</code> to a remote machine named <code
class="systemitem">penguin.example.com</code>, type the following at a
shell prompt:
+ </div><pre class="screen">~]$ <code
class="command">scp taglist.vim
john@penguin.example.com:.vim/plugin/taglist.vim</code>
+john(a)penguin.example.com's password:
+taglist.vim 100% 144KB 144.5KB/s
00:00</pre><div class="para">
+ Multiple files can be specified at once. To transfer the contents of <code
class="filename">.vim/plugin/</code> to the same directory on the
remote machine <code class="systemitem">penguin.example.com</code>,
type the following command:
+ </div><pre class="screen">~]$ <code
class="command">scp .vim/plugin/*
john@penguin.example.com:.vim/plugin/</code>
+john(a)penguin.example.com's password:
+closetag.vim 100% 13KB 12.6KB/s 00:00
+snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
+taglist.vim 100% 144KB 144.5KB/s
00:00</pre><div class="para">
+ To transfer a remote file to the local system, use the following syntax:
+ </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">
+ For instance, to download the <code
class="filename">.vimrc</code> configuration file from the remote
machine, type:
+ </div><pre class="screen">~]$ <code
class="command">scp john@penguin.example.com:.vimrc .vimrc</code>
+john(a)penguin.example.com's password:
+.vimrc 100% 2233 2.2KB/s
00:00</pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ssh-clients.html"><strong>Prev</strong>9.3. OpenSSH
Clients</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-clients-sftp.html"><strong>Next</strong>9.3.3. Using
the sftp Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-clients-sftp.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-clients-sftp.html
new file mode 100644
index 0000000..a896647
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-clients-sftp.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>9.3.3. Using the sftp 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-ssh-clients.html" title="9.3. OpenSSH Clients" /><link
rel="prev" href="s2-ssh-clients-scp.html" title="9.3.2. Using the
scp Utility" /><link rel="next"
href="s1-ssh-beyondshell.html" title="9.4. More Than a Secure Shell"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s1-
ssh-beyondshell.html"><strong>Next</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"
id="s2-ssh-clients-sftp">9.3.3. Using the <code
class="command">sftp</code>
Utility</h3></div></div></div><a id="id431826"
class="indexterm"></a><a id="id431842"
class="indexterm"></a><div class="para">
+ The <code class="command">sftp</code> utility can be used to
open a secure, interactive FTP session. In its design, it is similar to <code
class="command">ftp</code> except that it uses a secure, encrypted
connection.
+ </div><div class="para">
+ To connect to a remote system, use a command in the following form:
+ </div><pre class="screen"><code
class="command">sftp <em
class="replaceable"><code>username</code></em>@<em
class="replaceable"><code>hostname</code></em></code></pre><div
class="para">
+ For example, to log in to a remote machine named <code
class="systemitem">penguin.example.com</code> with <code
class="systemitem">john</code> as a username, type:
+ </div><pre class="screen">~]$ <code
class="command">sftp john(a)penguin.example.com</code>
+john(a)penguin.example.com's password:
+Connected to
penguin.example.com.
+sftp></pre><div class="para">
+ After you enter the correct password, you will be presented with a prompt. The
<code class="command">sftp</code> utility accepts a set of commands
similar to those used by <code class="command">ftp</code> (see <a
class="xref"
href="s2-ssh-clients-sftp.html#table-ssh-clients-sftp">Table 9.3, “A
selection of available sftp commands”</a>).
+ </div><div class="table"
id="table-ssh-clients-sftp"><h6>Table 9.3. A selection of available
sftp commands</h6><div class="table-contents"><table
summary="A selection of available sftp commands"
border="1"><colgroup><col width="38%"
class="command" /><col width="63%" class="description"
/></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">ls</code> [<em
class="replaceable"><code>directory</code></em>]
+ </td><td>
+ List the content of a remote <em
class="replaceable"><code>directory</code></em>. If none is
supplied, a current working directory is used by default.
+ </td></tr><tr><td>
+ <code class="command">cd</code> <em
class="replaceable"><code>directory</code></em>
+ </td><td>
+ Change the remote working directory to <em
class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">mkdir</code> <em
class="replaceable"><code>directory</code></em>
+ </td><td>
+ Create a remote <em
class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">rmdir</code> <em
class="replaceable"><code>path</code></em>
+ </td><td>
+ Remove a remote <em
class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">put</code> <em
class="replaceable"><code>localfile</code></em> [<em
class="replaceable"><code>remotefile</code></em>]
+ </td><td>
+ Transfer <em
class="replaceable"><code>localfile</code></em> to a remote
machine.
+ </td></tr><tr><td>
+ <code class="command">get</code> <em
class="replaceable"><code>remotefile</code></em> [<em
class="replaceable"><code>localfile</code></em>]
+ </td><td>
+ Transfer <em
class="replaceable"><code>remotefile</code></em> from a
remote machine.
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ For a complete list of available commands, refer to the <code
class="command">sftp</code> man page.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-clients-scp.html"><strong>Prev</strong>9.3.2. Using
the scp Utility</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-beyondshell.html"><strong>Next</strong>9.4. More
Than a Secure Shell</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-keypairs.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-keypairs.html
new file mode 100644
index 0000000..f873e0f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-keypairs.html
@@ -0,0 +1,128 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Using a Key-Based Authentication</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-ssh-configuration.html" title="9.2. An OpenSSH Configuration"
/><link rel="prev" href="s2-ssh-configuration-requiring.html"
title="9.2.3. Requiring SSH for Remote Connections" /><link
rel="next" href="s1-ssh-clients.html" title="9.3. OpenSSH
Clients" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-requiring.html"><strong>Prev</strong></a></li><l
i class="next"><a accesskey="n"
href="s1-ssh-clients.html"><strong>Next</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"
id="s2-ssh-configuration-keypairs">9.2.4. Using a Key-Based
Authentication</h3></div></div></div><a id="id556221"
class="indexterm"></a><div class="para">
+ To improve the system security even further, you can enforce the key-based
authentication by disabling the standard password authentication. To do so, open the
<code class="filename">/etc/ssh/sshd_config</code> configuration
file in a text editor, and change the <code
class="option">PasswordAuthentication</code> option as follows:
+ </div><pre class="programlisting">PasswordAuthentication
no</pre><div class="para">
+ To be able to use <code class="command">ssh</code>, <code
class="command">scp</code>, or <code
class="command">sftp</code> to connect to the server from a client
machine, generate an authorization key pair by following the steps below. Note that keys
must be generated for each user separately.
+ </div><div class="para">
+ Fedora 15 uses SSH Protocol 2 and RSA keys by default (see <a
class="xref" href="ch-OpenSSH.html#s2-ssh-versions">Section 9.1.3,
“Protocol Versions”</a> for more information).
+ </div><div class="important"><div
class="admonition_header"><h2>Do not generate key pairs as
root</h2></div><div class="admonition"><div
class="para">
+ If you complete the steps as <code
class="systemitem">root</code>, only <code
class="systemitem">root</code> will be able to use the keys.
+ </div></div></div><div class="note"><div
class="admonition_header"><h2>Backup your ~/.ssh/
directory</h2></div><div class="admonition"><div
class="para">
+ If you reinstall your system and want to keep previously generated key pair, backup
the <code class="filename">~/.ssh/</code> directory. After
reinstalling, copy it back to your home directory. This process can be done for all users
on your system, including <code class="systemitem">root</code>.
+ </div></div></div><div class="section"
id="s3-ssh-configuration-keypairs-generating"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-ssh-configuration-keypairs-generating">9.2.4.1. Generating Key
Pairs</h4></div></div></div><a id="id441584"
class="indexterm"></a><a id="id567911"
class="indexterm"></a><div class="para">
+ To generate an RSA key pair for version 2 of the SSH protocol, follow these steps:
+ </div><a id="id567931"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Generate an RSA key pair by typing the following at a shell prompt:
+ </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">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location (that is, <code
class="filename">~/.ssh/id_rsa</code>) for the newly created key.
+ </div></li><li class="step"><div
class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so.
For security reasons, avoid using the same password as you use to log in to your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </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(a)penguin.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| E. |
+| . . |
+| o . |
+| . .|
+| S . . |
+| + o o ..|
+| * * +oo|
+| O +..=|
+| o* o.|
++-----------------+</pre></li><li class="step"><div
class="para">
+ Change the permissions of the <code
class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code
class="command">chmod 755 ~/.ssh</code></pre></li><li
class="step"><div class="para">
+ Copy the content of <code
class="filename">~/.ssh/id_rsa.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> on the machine to which
you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step"><div
class="para">
+ Change the permissions of the <code
class="filename">~/.ssh/authorized_keys</code> file using the following
command:
+ </div><pre class="screen">~]$ <code
class="command">chmod 644
~/.ssh/authorized_keys</code></pre></li></ol></div><a
id="id507765" class="indexterm"></a><a
id="id507777" class="indexterm"></a><div
class="para">
+ To generate a DSA key pair for version 2 of the SSH protocol, follow these steps:
+ </div><a id="id619842"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Generate a DSA key pair by typing the following at a shell prompt:
+ </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">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location (that is, <code
class="filename">~/.ssh/id_dsa</code>) for the newly created key.
+ </div></li><li class="step"><div
class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so.
For security reasons, avoid using the same password as you use to log in to your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </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(a)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">
+ Change the permissions of the <code
class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code
class="command">chmod 775 ~/.ssh</code></pre></li><li
class="step"><div class="para">
+ Copy the content of <code
class="filename">~/.ssh/id_dsa.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> on the machine to which
you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step"><div
class="para">
+ Change the permissions of the <code
class="filename">~/.ssh/authorized_keys</code> file using the following
command:
+ </div><pre class="screen">~]$ <code
class="command">chmod 644
~/.ssh/authorized_keys</code></pre></li></ol></div><a
id="id558208" class="indexterm"></a><a
id="id558220" class="indexterm"></a><div
class="para">
+ To generate an RSA key pair for version 1 of the SSH protocol, follow these steps:
+ </div><a id="id558240"
class="indexterm"></a><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Generate an RSA key pair by typing the following at a shell prompt:
+ </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">
+ Press <span
class="keycap"><strong>Enter</strong></span> to confirm the
default location (that is, <code
class="filename">~/.ssh/identity</code>) for the newly created key.
+ </div></li><li class="step"><div
class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so.
For security reasons, avoid using the same password as you use to log into your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </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(a)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">
+ Change the permissions of the <code
class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code
class="command">chmod 755 ~/.ssh</code></pre></li><li
class="step"><div class="para">
+ Copy the content of <code
class="filename">~/.ssh/identity.pub</code> into the <code
class="filename">~/.ssh/authorized_keys</code> on the machine to which
you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step"><div
class="para">
+ Change the permissions of the <code
class="filename">~/.ssh/authorized_keys</code> file using the following
command:
+ </div><pre class="screen">~]$ <code
class="command">chmod 644
~/.ssh/authorized_keys</code></pre></li></ol></div><div
class="para">
+ Refer to <a class="xref"
href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Section 9.2.4.2,
“Configuring ssh-agent”</a> for information on how to set up your system to remember
the passphrase.
+ </div><div class="important"><div
class="admonition_header"><h2>Never share your private
key</h2></div><div class="admonition"><div
class="para">
+ The private key is for your personal use only, and it is important that you never
give it to anyone.
+ </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"
id="s3-ssh-configuration-keypairs-agent">9.2.4.2. Configuring
ssh-agent</h4></div></div></div><a id="id619438"
class="indexterm"></a><a id="id619454"
class="indexterm"></a><a id="id619466"
class="indexterm"></a><a id="id571876"
class="indexterm"></a><div class="para">
+ To store your passphrase so that you do not have to enter it each time you initiate
a connection with a remote machine, you can use the <code
class="command">ssh-agent</code> authentication agent. To save your
passphrase for a certain shell prompt, use the following command:
+ </div><pre class="screen">~]$ <code
class="command">ssh-add</code>
+Enter passphrase for /home/john/.ssh/id_rsa:</pre><div
class="para">
+ Note that when you log out, your passphrase will be forgotten. You must execute the
command each time you log in to a virtual console or a terminal window.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-requiring.html"><strong>Prev</strong>9.2.3. Requiring
SSH for Remote Connections</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-ssh-clients.html"><strong>Next</strong>9.3. OpenSSH
Clients</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-requiring.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-requiring.html
new file mode 100644
index 0000000..e52f4c8
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-requiring.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>9.2.3. Requiring SSH for Remote 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-ssh-configuration.html" title="9.2. An OpenSSH Configuration"
/><link rel="prev" href="s2-ssh-configuration-sshd.html"
title="9.2.2. Starting an OpenSSH Server" /><link rel="next"
href="s2-ssh-configuration-keypairs.html" title="9.2.4. Using a Key-Based
Authentication" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-sshd.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n"
href="s2-ssh-configuration-keypairs.html"><strong>Next</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"
id="s2-ssh-configuration-requiring">9.2.3. Requiring SSH for Remote
Connections</h3></div></div></div><a id="id535871"
class="indexterm"></a><a id="id535883"
class="indexterm"></a><div class="para">
+ For SSH to be truly effective, using insecure connection protocols should be
prohibited. Otherwise, a user's password may be protected using SSH for one session,
only to be captured later while logging in using Telnet. Some services to disable include
<code class="command">telnet</code>, <code
class="command">rsh</code>, <code
class="command">rlogin</code>, and <code
class="command">vsftpd</code>.
+ </div><div class="para">
+ To make sure these services are not running, type the following commands at a shell
prompt:
+ </div><pre class="screen"><code
class="command">systemctl stop telnet.service</code>
+<code class="command">systemctl stop rsh.service</code>
+<code class="command">systemctl stop rlogin.service</code>
+<code class="command">systemctl stop
vsftpd.service</code></pre><div class="para">
+ To disable running these services at startup, type:
+ </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">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s2-ssh-configuration-sshd.html"><strong>Prev</strong>9.2.2. Starting
an OpenSSH Server</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-configuration-keypairs.html"><strong>Next</strong>9.2.4. Using
a Key-Based Authentication</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-sshd.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-sshd.html
new file mode 100644
index 0000000..8824142
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s2-ssh-configuration-sshd.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>9.2.2. Starting an OpenSSH 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-ssh-configuration.html" title="9.2. An OpenSSH Configuration"
/><link rel="prev" href="s1-ssh-configuration.html"
title="9.2. An OpenSSH Configuration" /><link rel="next"
href="s2-ssh-configuration-requiring.html" title="9.2.3. Requiring SSH for
Remote 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="s1-ssh-configuration.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n"
href="s2-ssh-configuration-requiring.html"><strong>Next</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"
id="s2-ssh-configuration-sshd">9.2.2. Starting an OpenSSH
Server</h3></div></div></div><a id="id604516"
class="indexterm"></a><div class="note"><div
class="admonition_header"><h2>Make sure you have relevant packages
installed</h2></div><div class="admonition"><div
class="para">
+ To run an OpenSSH server, you must have the <span
class="package">openssh-server</span> and <span
class="package">openssh</span> packages installed. Refer to <a
class="xref" href="sec-Installing.html">Section 4.2.4, “Installing
Packages”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><a id="id478347"
class="indexterm"></a><div class="para">
+ To start the <code class="command">sshd</code> daemon, type the
following at a shell prompt:
+ </div><pre class="screen"><code
class="command">systemctl start sshd.service</code></pre><a
id="id478376" class="indexterm"></a><div
class="para">
+ To stop the running <code class="command">sshd</code> daemon,
use the following command:
+ </div><pre class="screen"><code
class="command">systemctl stop sshd.service</code></pre><div
class="para">
+ If you want the daemon to start automatically at the boot time, type:
+ </div><pre class="screen"><code
class="command">systemctl enable sshd.service</code></pre><div
class="para">
+ Refer to <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> for more information on how to configure services in Fedora.
+ </div><div class="para">
+ Note that if you reinstall the system, a new set of identification keys will be
created. As a result, clients who had connected to the system with any of the OpenSSH
tools before the reinstall will see the following message:
+ </div><pre
class="screen">@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
+Someone could be eavesdropping on you right now (man-in-the-middle attack)!
+It is also possible that the RSA host key has just been changed.</pre><div
class="para">
+ To prevent this, you can back up the relevant files from the <code
class="filename">/etc/ssh/</code> directory (see <a
class="xref"
href="s1-ssh-configuration.html#table-ssh-configuration-configs-system">Table 9.1,
“System-wide configuration files”</a> for a complete list), and restore them
whenever you reinstall the system.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s1-ssh-configuration.html"><strong>Prev</strong>9.2. An
OpenSSH Configuration</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ssh-configuration-requiring.html"><strong>Next</strong>9.2.3. Requiring
SSH for Remote Connections</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-ftp-vsftpd-conf.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-ftp-vsftpd-conf.html
new file mode 100644
index 0000000..b5b13ee
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-ftp-vsftpd-conf.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>15.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-FTP.html" title="15.2. FTP" /><link
rel="prev" href="s2-ftp-servers.html" title="15.2.2. FTP
Servers" /><link rel="next" href="s2-ftp-vsftpd-start.html"
title="15.2.4. Starting and Stopping 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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-vsftpd-start.html"><stro
ng>Next</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"
id="s3-ftp-vsftpd-conf">15.2.3. Files Installed with <code
class="command">vsftpd</code>
</h3></div></div></div><a id="id629008"
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">Section 15.2.4,
“Starting and Stopping <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 15 <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">Section 15.2.5, “
<code class="command">vsftpd</code> Configuration Options”</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>Prev</strong>15.2.2. FTP
Servers</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-ftp-vsftpd-start.html"><strong>Next</strong>15.2.4. Starting
and Stopping vsftpd </a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-restarting.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-restarting.html
new file mode 100644
index 0000000..2594049
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-restarting.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Restarting the 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-services-running.html" title="7.2. Running Services"
/><link rel="prev" href="s3-services-running-stopping.html"
title="7.2.3. Stopping the Service" /><link rel="next"
href="s1-services-additional-resources.html" title="7.3. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="s3-services-running-stopping.html"><strong>Prev</strong></a></li><li
clas
s="next"><a accesskey="n"
href="s1-services-additional-resources.html"><strong>Next</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"
id="s3-services-running-restarting">7.2.4. Restarting the
Service</h3></div></div></div><div class="para">
+ To restart a service, use the <code
class="command">systemctl</code> command in the following form:
+ </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="para">
+ For example, to restart the <code
class="systemitem">httpd</code> service, type the following at a shell
prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl restart
httpd.service</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s3-services-running-stopping.html"><strong>Prev</strong>7.2.3. Stopping
the Service</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-services-additional-resources.html"><strong>Next</strong>7.3. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-running.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-running.html
new file mode 100644
index 0000000..7d0b91b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-running.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Running the 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-services-running.html" title="7.2. Running Services"
/><link rel="prev" href="s1-services-running.html"
title="7.2. Running Services" /><link rel="next"
href="s3-services-running-stopping.html" title="7.2.3. Stopping the
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-services-running.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s3-services-running-stopping.html"><strong>Next</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"
id="s3-services-running-running">7.2.2. Running the
Service</h3></div></div></div><div class="para">
+ To run a service, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to start the <code class="systemitem">httpd</code>
service, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl start
httpd.service</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s1-services-running.html"><strong>Prev</strong>7.2. Running
Services</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s3-services-running-stopping.html"><strong>Next</strong>7.2.3. Stopping
the Service</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-stopping.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-stopping.html
new file mode 100644
index 0000000..2d2884f
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/s3-services-running-stopping.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Stopping the 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-services-running.html" title="7.2. Running Services"
/><link rel="prev" href="s3-services-running-running.html"
title="7.2.2. Running the Service" /><link rel="next"
href="s3-services-running-restarting.html" title="7.2.4. Restarting the
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="s3-services-running-running.html"><strong>Prev</strong></a></li><li
class
="next"><a accesskey="n"
href="s3-services-running-restarting.html"><strong>Next</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"
id="s3-services-running-stopping">7.2.3. Stopping the
Service</h3></div></div></div><div class="para">
+ To stop a service, use the <code
class="command">systemctl</code> command in the following form:
+ </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">
+ For example, to stop the <code class="systemitem">httpd</code>
service, type the following at a shell prompt as <code
class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code
class="command">systemctl stop
httpd.service</code></pre></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="s3-services-running-running.html"><strong>Prev</strong>7.2.2. Running
the Service</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s3-services-running-restarting.html"><strong>Next</strong>7.2.4. Restarting
the Service</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Additional_Resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Additional_Resources.html
new file mode 100644
index 0000000..5b37da4
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Additional_Resources.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>4.5. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-yum.html" title="Chapter 4. Yum" /><link
rel="prev" href="sec-Plugin_Descriptions.html"
title="4.4.3. Plugin Descriptions" /><link rel="next"
href="ch-PackageKit.html" title="Chapter 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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch-PackageKit.html">
<strong>Next</strong></a></li></ul><div
class="section" id="sec-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-Additional_Resources">4.5. Additional
Resources</h2></div></div></div><a id="id624389"
class="indexterm"></a><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl...
</span></dt><dd><div class="para">
+ The <code class="literal">Yum Guides</code> section of the
<span class="application"><strong>Yum</strong></span>
wiki contains more documentation.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Plugin_Descriptions.html"><strong>Prev</strong>4.4.3. Plugin
Descriptions</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-PackageKit.html"><strong>Next</strong>Chapter 5. PackageKit</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Configuration_File_Changes.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Configuration_File_Changes.html
new file mode 100644
index 0000000..a593647
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Configuration_File_Changes.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>A.2.3. Configuration File Changes</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-rpm-using.html" title="A.2. Using RPM" /><link
rel="prev" href="sec-Installing_and_Upgrading.html"
title="A.2.2. Installing and Upgrading" /><link rel="next"
href="s2-rpm-uninstalling.html" title="A.2.4. Uninstalling"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" hre
f="s2-rpm-uninstalling.html"><strong>Next</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"
id="sec-Configuration_File_Changes">A.2.3. Configuration File
Changes</h3></div></div></div><a id="id595708"
class="indexterm"></a><a id="id631430"
class="indexterm"></a><div class="para">
+ Because RPM performs intelligent upgrading of packages with configuration files
+ <a id="id631448" 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.fc15.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.fc15.x86_64.rpm</code>
+</pre></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Installing_and_Upgrading.html"><strong>Prev</strong>A.2.2. Installing
and Upgrading</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s2-rpm-uninstalling.html"><strong>Next</strong>A.2.4. Uninstalling</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
new file mode 100644
index 0000000..53d85ce
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.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.3. Configuring Yum and Yum Repositories</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-yum.html" title="Chapter 4. Yum" /><link
rel="prev" href="sec-Removing.html" title="4.2.5. Removing
Packages" /><link rel="next"
href="sec-Setting_repository_Options.html" title="4.3.2. Setting
[repository] Options" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Removing.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="sec-Setting_re
pository_Options.html"><strong>Next</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"
id="sec-Configuring_Yum_and_Yum_Repositories">4.3. Configuring Yum and Yum
Repositories</h2></div></div></div><a id="id614220"
class="indexterm"></a><a id="id614232"
class="indexterm"></a><div class="para">
+ This section shows you how to:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ set global <span
class="application"><strong>Yum</strong></span> options by
editing the <code class="literal">[main]</code> section of the
<code class="filename">/etc/yum.conf</code> configuration file;
+ </div></li><li class="listitem"><div
class="para">
+ set options for individual repositories by editing the <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections in <code class="filename">/etc/yum.conf</code> and <code
class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code> directory;
+ </div></li><li class="listitem"><div
class="para">
+ use <span
class="application"><strong>Yum</strong></span> variables
in <code class="filename">/etc/yum.conf</code> and files in <code
class="filename">/etc/yum.repos.d/</code> so that dynamic version and
architecture values are handled correctly; and,
+ </div></li><li class="listitem"><div
class="para">
+ set up your own custom <span
class="application"><strong>Yum</strong></span>
repository.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">/etc/yum.conf</code> configuration
file contains one mandatory <code class="literal">[main]</code>
section under which you can set <span
class="application"><strong>Yum</strong></span> options.
The values that you define in the <code
class="literal">[main]</code> section of <code
class="filename">yum.conf</code> have global effect, and may override
values set in individual <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections. You can also add <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections to <code class="filename">/etc/yum.conf</code>; however,
best practice is to define individual repositories in new or existing <code
class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code>directory. Refer to <a
class="xref"
href="sec-Setting_repository_Options.html">Section 4.3.2, “Setting
[repository] Options”</a> if you need to add or
edit repository-specific information.
+ </div><div class="section"
id="sec-Setting_main_Options"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Setting_main_Options">4.3.1. Setting [main]
Options</h3></div></div></div><a id="id614404"
class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/yum.conf</code> configuration
file contains exactly one <code class="literal">[main]</code>
section. You can add many additional options under the <code
class="literal">[main]</code> section heading in <code
class="filename">/etc/yum.conf</code>. Some of the key-value pairs in
the <code class="literal">[main]</code> section affect how <code
class="command">yum</code> operates; others affect how <span
class="application"><strong>Yum</strong></span> treats
repositories. The best source of information for all <span
class="application"><strong>Yum</strong></span> options is
in the <code class="literal">[main] OPTIONS</code> and <code
class="literal">[repository] OPTIONS</code> sections of <code
class="command">man yum.conf</code>.
+ </div><div class="para">
+ A sample <code class="filename">/etc/yum.conf</code>
configuration file can look like this:
+ </div><pre class="screen">[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">[comments abridged]</span></em>
+# PUT YOUR REPOS HERE OR IN separate files named file.repo
+# in /etc/yum.repos.d</pre><div class="para">
+ The following is a list of the most commonly-used options in the <code
class="literal">[main]</code> section, and descriptions for each:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">assumeyes=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — <code
class="command">yum</code> should prompt for confirmation of critical
actions it performs. This is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — Do not prompt for
confirmation of critical <code class="command">yum</code> actions.
If <code class="literal">assumeyes=1</code> is set, <code
class="command">yum</code> behaves in the same way that the command
line option <code class="option">-y</code> does.
+ </div></dd><dt class="varlistentry"><span
class="term">cachedir=<code
class="filename">/var/cache/yum/$basearch/$releasever</code></span></dt><dd><div
class="para">
+ This option specifies the directory where <span
class="application"><strong>Yum</strong></span> should
store its cache and database files. By default, <span
class="application"><strong>Yum</strong></span>'s cache
directory is <code
class="filename">/var/cache/yum/$basearch/$releasever</code>. See <a
class="xref" href="sec-Using_Yum_Variables.html">Section 4.3.3,
“Using Yum Variables”</a> for descriptions of the <code
class="varname">$basearch</code> and <code
class="varname">$releasever</code> <span
class="application"><strong>Yum</strong></span> variables.
+ </div></dd><dt class="varlistentry"><span
class="term">debuglevel=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is an integer
between <code class="constant">1</code> and <code
class="constant">10</code>. Setting a higher <code
class="literal">debuglevel</code> value causes <code
class="command">yum</code> to display more detailed debugging output.
<code class="literal">debuglevel=0</code> disables debugging output,
while <code class="literal">debuglevel=2</code> is the default.
+ </div></dd><dt class="varlistentry"><span
class="term">exactarch=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Do not take into account
the exact architecture when updating packages.
+ </div><div class="para">
+ <code class="constant">1</code> — Consider the exact
architecture when updating packages. With this setting, <code
class="command">yum</code> will not install an i686 package to update
an i386 package already installed on the system. This is the default.
+ </div></dd><dt class="varlistentry"><span
class="term">exclude=<em
class="replaceable"><code>package_name</code></em> [<span
class="optional"><em
class="replaceable"><code>more_package_names</code></em></span>]</span></dt><dd><div
class="para">
+ This option allows you to exclude packages by keyword during installation/updates.
Listing multiple packages for exclusion can be accomplished by quoting a space-delimited
list of packages. Shell globs using wildcards (for example, <code
class="literal">*</code> and <code
class="literal">?</code>) are allowed.
+ </div></dd><dt class="varlistentry"><span
class="term">gpgcheck=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable GPG
signature-checking on packages in all repositories, including local package installation.
+ </div><div class="para">
+ <code class="constant">1</code> — Enable GPG
signature-checking on all packages in all repositories, including local package
installation. <code class="literal">gpgcheck=1</code> is the
default, and thus all packages' signatures are checked.
+ </div><div class="para">
+ If this option is set in the <code
class="literal">[main]</code> section of the <code
class="filename">/etc/yum.conf</code> file, it sets the GPG-checking
rule for all repositories. However, you can also set <code
class="literal">gpgcheck=</code><em
class="replaceable"><code>value</code></em> for individual
repositories instead; i.e., you can enable GPG-checking on one repository while disabling
it on another. Setting <code class="literal">gpgcheck=<em
class="replaceable"><code>value</code></em></code>
for an individual repository in its corresponding <code
class="filename">.repo</code> file overrides the default if it is
present in <code class="filename">/etc/yum.conf</code>. Refer to
<a class="xref" href="s1-check-rpm-sig.html">Section A.3,
“Checking a Package's Signature”</a> for further information on GPG
signature-checking.
+ </div></dd><dt class="varlistentry"><span
class="term">groupremove_leaf_only=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — <code
class="command">yum</code> should <span
class="emphasis"><em>not</em></span> check the dependencies
of each package when removing a package group. With this setting, <code
class="command">yum</code> removes all packages in a package group,
regardless of whether those packages are required by other packages or groups. <code
class="literal">groupremove_leaf_only=0</code> is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — <code
class="command">yum</code> should check the dependencies of each
package when removing a package group, and remove only those packages which are not not
required by any other package or group.
+ </div><div class="para">
+ For more information on removing packages, refer to <a class="xref"
href="sec-Removing.html#important-Package_Group_Removal">Intelligent package
group removal</a>.
+ </div></dd><dt class="varlistentry"><span
class="term">installonlypkgs=<em
class="replaceable"><code>space</code></em> <em
class="replaceable"><code>separated</code></em> <em
class="replaceable"><code>list</code></em> <em
class="replaceable"><code>of</code></em> <em
class="replaceable"><code>packages</code></em></span></dt><dd><div
class="para">
+ Here you can provide a space-separated list of packages which <code
class="command">yum</code> can <span
class="emphasis"><em>install</em></span>, but will never
<span class="emphasis"><em>update</em></span>. Refer to
<code class="command">man yum.conf</code> for the list of packages
which are install-only by default. If you add the <code
class="literal">installonlypkgs</code> directive to <code
class="filename">/etc/yum.conf</code>, you should ensure that you list
<span class="emphasis"><em>all</em></span> of the
packages that should be install-only, including any of those listed under the <code
class="literal">installonlypkgs</code> section of <code
class="command">man yum.conf</code>. In particular, kernel packages
should always be listed in <code
class="literal">installonlypkgs</code> (as they are by default), and
<code class="literal">installonly_limit</code> should always be set
to a value greater than <code class="constant">2</code> so that a
backup kernel is a
lways available in case the default one fails to boot. Refer to <a
class="xref"
href="sec-Configuring_Yum_and_Yum_Repositories.html#varentry-installonly_limit_value">installonly_limit=<em
class="replaceable"><code>value</code></em></a> for
details on the <code class="literal">installonly_limit</code>
directive.
+ </div></dd><dt class="varlistentry"
id="varentry-installonly_limit_value"><span
class="term">installonly_limit=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is an integer
representing the maximum number of versions that can be installed simultaneously for any
single package listed in the <code
class="literal">installonlypkgs</code> directive. The defaults for the
<code class="literal">installonlypkgs</code> directive include
several different kernel packages, so be aware that changing the value of <code
class="literal">installonly_limit</code> will also affect the maximum
number of installed versions of any single kernel package. The default value listed in
<code class="filename">/etc/yum.conf</code> is <code
class="literal">installonly_limit=3</code>, and it is not recommended
to decrease this value, particularly below <code
class="constant">2</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">keepcache=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Do not retain the cache of
headers and packages after a successful installation. This is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — Retain the cache after a
successful installation.
+ </div></dd><dt class="varlistentry"><span
class="term">logfile=<code
class="filename">/var/log/yum.log</code></span></dt><dd><div
class="para">
+ This option specifies where <code class="command">yum</code>
should send its logging output. By default, <code
class="command">yum</code> logs to <code
class="filename">/var/log/yum.log</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">multilib_policy=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <strong
class="userinput"><code>best</code></strong> — install the
best-choice architecture for this system. For example, setting <code
class="literal">multilib_policy=best</code> on an AMD64 system causes
<code class="command">yum</code> to install 64-bit versions of all
packages.
+ </div><div class="para">
+ <strong
class="userinput"><code>all</code></strong> — always
install every possible architecture for every package. For example, with <code
class="literal">multilib_policy</code> set to <code
class="literal">all</code> on an AMD64 system, <code
class="command">yum</code> would install both the i686 and AMD64
versions of a package, if both were available.
+ </div></dd><dt class="varlistentry"><span
class="term">obsoletes=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable <code
class="command">yum</code>'s obsoletes processing logic when
performing updates.
+ </div><div class="para">
+ <code class="constant">1</code> — Enable <code
class="command">yum</code>'s obsoletes processing logic when
performing updates. When one package declares in its spec file that it <em
class="firstterm">obsoletes</em> another package, the latter package
will be replaced by the former package when the former package is installed. Obsoletes are
declared, for example, when a package is renamed. <code
class="literal">obsoletes=1</code> the default.
+ </div></dd><dt class="varlistentry"><span
class="term">plugins=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable all <span
class="application"><strong>Yum</strong></span> plugins
globally.
+ </div><div class="important"
id="important-Disabling_all_plugins_is_not_advised-main_options"><div
class="admonition_header"><h2>Disabling all plugins is not
advised</h2></div><div class="admonition"><div
class="para">
+ Disabling all plugins is not advised, because certain plugins provide important
<code class="command">Yum</code> services. Disabling plugins
globally is provided as a convenience option, and is generally only recommended when
diagnosing a potential problem with <code
class="command">Yum</code>.
+ </div></div></div><div class="para">
+ <code class="constant">1</code> — Enable all <span
class="application"><strong>Yum</strong></span> plugins
globally. With <code class="literal">plugins=1</code>, you can still
disable a specific <span
class="application"><strong>Yum</strong></span> plugin by
setting <code class="literal">enabled=0</code> in that plugin's
configuration file. Refer to <a class="xref"
href="sec-Yum_Plugins.html">Section 4.4, “Yum Plugins”</a> for more
information about various <span
class="application"><strong>Yum</strong></span> plugins, or
to <a class="xref"
href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Section 4.4.1,
“Enabling, Configuring and Disabling Yum Plugins”</a> for further information on
controlling plugins.
+ </div></dd><dt class="varlistentry"><span
class="term">reposdir=<em
class="replaceable"><code>/absolute/path/to/directory/containing/repo/files</code></em></span></dt><dd><div
class="para">
+ This option allows you to specify a directory where <code
class="filename">.repo</code> files are located. All <code
class="filename">.repo</code> files contain repository information
(similar to the <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections of <code class="filename">/etc/yum.conf</code>). <code
class="command">yum</code> collects all repository information from
<code class="filename">.repo</code> files and the <code
class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section of the <code class="filename">/etc/yum.conf</code> file to
create a master list of repositories to use for transactions. Refer to <a
class="xref"
href="sec-Setting_repository_Options.html">Section 4.3.2, “Setting
[repository] Options”</a> for more information about options you can use for both
the <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section and <code class="filename">.
repo</code> files. If <code class="literal">reposdir</code>
is not set, <code class="command">yum</code> uses the default
directory <code class="filename">/etc/yum.repos.d/</code>.
+ </div></dd><dt class="varlistentry"><span
class="term">retries=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is an integer
<code class="constant">0</code> or greater. This value sets the
number of times <code class="command">yum</code> should attempt to
retrieve a file before returning an error. Setting this to <code
class="constant">0</code> makes <code
class="command">yum</code> retry forever. The default value is <code
class="constant">10</code>.
+ </div></dd></dl></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Removing.html"><strong>Prev</strong>4.2.5. Removing
Packages</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Setting_repository_Options.html"><strong>Next</strong>4.3.2. Setting
[repository] Options</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Creating_a_Yum_Repository.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Creating_a_Yum_Repository.html
new file mode 100644
index 0000000..dcc3663
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Creating_a_Yum_Repository.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>4.3.4. Creating a Yum 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Configuring_Yum_and_Yum_Repositories.html"
title="4.3. Configuring Yum and Yum Repositories" /><link
rel="prev" href="sec-Using_Yum_Variables.html"
title="4.3.3. Using Yum Variables" /><link rel="next"
href="sec-Yum_Plugins.html" title="4.4. Yum Plugins"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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_Yum_Variables.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Yum_Plugins.html"><strong>Next</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"
id="sec-Creating_a_Yum_Repository">4.3.4. Creating a Yum
Repository</h3></div></div></div><a id="id419703"
class="indexterm"></a><div class="para">
+ To set up a <span
class="application"><strong>Yum</strong></span> repository,
follow these steps:
+ </div><div class="procedure"
id="procedure-Setting_Up_a_Yum_repository"><ol
class="1"><li class="step"><div
class="para">
+ Install the <span class="package">createrepo</span> package:
+ </div><pre class="screen">~]# <code
class="command">yum install
createrepo</code></pre></li><li class="step"><div
class="para">
+ Copy all of the packages into one directory, such as <code
class="filename">/mnt/local_repo/</code>.
+ </div></li><li class="step"><div
class="para">
+ Run the <code class="command">createrepo --database</code>
command on that directory:
+ </div><pre class="screen">~]# <code
class="command">createrepo --database
/mnt/local_repo/</code></pre></li></ol></div><div
class="para">
+ This will create the necessary metadata for your <span
class="application"><strong>Yum</strong></span> 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-Using_Yum_Variables.html"><strong>Prev</strong>4.3.3. Using
Yum Variables</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Yum_Plugins.html"><strong>Next</strong>4.4. Yum
Plugins</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Displaying_Information_About_a_Module.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Displaying_Information_About_a_Module.html
new file mode 100644
index 0000000..513db73
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Displaying_Information_About_a_Module.html
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. Working with
Kernel Modules" /><link rel="prev"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. Working with
Kernel Modules" /><link rel="next"
href="sec-Loading_a_Module.html" title="21.3. Loading 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="ch-Working_with_Kernel_Modules.html"><stron
g>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Loading_a_Module.html"><strong>Next</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"
id="sec-Displaying_Information_About_a_Module">21.2. Displaying Information
About a Module</h2></div></div></div><a id="id465871"
class="indexterm"></a><a id="id635836"
class="indexterm"></a><a id="id596237"
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>Example 21.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, &lt;linux.nics(a)intel.com&gt;
+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><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>Example 21.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>Prev</strong>Chapter 21. Working
with Kernel Modules</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Loading_a_Module.html"><strong>Next</strong>21.3. Loading
a Module</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Displaying_Package_Information.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Displaying_Package_Information.html
new file mode 100644
index 0000000..c44e64c
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Displaying_Package_Information.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.2.3. Displaying Package Information</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="4.2. Packages and
Package Groups" /><link rel="prev"
href="sec-Listing_Packages.html" title="4.2.2. Listing Packages"
/><link rel="next" href="sec-Installing.html"
title="4.2.4. Installing Packages" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Listing_Packages.html"><strong>Prev</strong></a></li><li
class="next"><a ac
cesskey="n"
href="sec-Installing.html"><strong>Next</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"
id="sec-Displaying_Package_Information">4.2.3. Displaying Package
Information</h3></div></div></div><a id="id427119"
class="indexterm"></a><a id="id427135"
class="indexterm"></a><div class="para">
+ The <code class="command">yum info <em
class="replaceable"><code>package_name</code></em>
[<span class="optional"><em
class="replaceable"><code>more_names</code></em></span>]</code>
command displays information about one or more packages (glob expressions are valid here
as well). For example, to display information about the <span
class="package">abrt</span> package, type:
+ </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><div class="para">
+ <code class="command">yum info <em
class="replaceable"><code>package_name</code></em></code>
is similar to the <code class="command">rpm -q --info <em
class="replaceable"><code>package_name</code></em></code>
command, but provides as additional information the ID of the <span
class="application"><strong>Yum</strong></span> repository
the RPM package is found in (look for the <code
class="computeroutput">From repo</code> line in the output).
+ </div><div class="para">
+ The <code class="command">yumdb info <em
class="replaceable"><code>package_name</code></em>
[<span class="optional"><em
class="replaceable"><code>more_names</code></em></span>]</code>
command can be used to query the <span
class="application"><strong>Yum</strong></span> database
for alternative and useful information about a package, including the checksum of the
package (and algorithm used to produce it, such as SHA-256), the command given on the
command line that was invoked to install the package (if any), and the reason that the
package is installed on the system (where <code
class="computeroutput">user</code> indicates it was installed by the
user, and <code class="computeroutput">dep</code> means it was
brought in as a dependency). For example, to display additional information about the
<span class="package">yum</span> package, type:
+ </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">
+ For more information on the <code class="command">yumdb</code>
command, see <code class="command">man yumdb</code>.
+ </div><div class="para">
+ Finally, the <code class="command">yum history</code> command
can be used to show a timeline of <span
class="application"><strong>Yum</strong></span>
transactions, the dates and times on when they occurred, the number of packages affected,
whether transactions succeeded or were aborted, and if the RPM database was changed
between transactions. Refer to the <code
class="computeroutput">history</code> section of <code
class="command">man yum</code> for details.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Listing_Packages.html"><strong>Prev</strong>4.2.2. Listing
Packages</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing.html"><strong>Next</strong>4.2.4. Installing
Packages</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Finding_Packages_with_Filters.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Finding_Packages_with_Filters.html
new file mode 100644
index 0000000..3dd2b81
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Finding_Packages_with_Filters.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>5.2.2. Finding Packages with Filters</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Using_Add_Remove_Software.html" title="5.2. Using Add/Remove
Software" /><link rel="prev"
href="sec-Using_Add_Remove_Software.html" title="5.2. Using Add/Remove
Software" /><link rel="next"
href="sec-Installing_and_Removing_Packages_and_Dependencies.html"
title="5.2.3. Installing and Removing Packages (and Dependencies)"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" hr
ef="sec-Using_Add_Remove_Software.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>Next</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"
id="sec-Finding_Packages_with_Filters">5.2.2. Finding Packages with
Filters</h3></div></div></div><a id="id614886"
class="indexterm"></a><div class="para">
+ You can view the list of all <span
class="emphasis"><em>configured</em></span> and unfiltered
(see below) <span
class="application"><strong>Yum</strong></span>
repositories by opening <span class="guilabel"><strong>Add/Remove
Software</strong></span> and clicking <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software
Sources</strong></span>. Once the software sources have been updated, it is
often beneficial to apply some filters so that <span
class="application"><strong>PackageKit</strong></span>
retrieves the results of our <span
class="guilabel"><strong>Find</strong></span> queries
faster. This is especially helpful when performing many package searches. Four of the
filters in the <span
class="guimenu"><strong>Filters</strong></span> drop-down
menu are used to split results by matching or not matching a single criterion. By default
when <span
class="application"><strong>PackageKit</strong></span>
starts, these filters are a
ll unapplied (<span class="guibutton"><strong>No
Filter</strong></span>), but once you do filter by one of them, that filter
remains set until you either change it or close <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Because you are usually searching for available packages that are <span
class="emphasis"><em>not</em></span> installed on the
system, click <span
class="guimenu"><strong>Filters</strong></span> → <span
class="guimenuitem"><strong>Installed</strong></span> and
select the <span class="guimenuitem"><strong>Only
Available</strong></span> radio button.
+ <a id="id614969" class="indexterm"></a>
+ <a id="id614985" class="indexterm"></a>
+ <a id="id614997" class="indexterm"></a>
+ <a id="id615013" class="indexterm"></a>
+ <a id="id615028" 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="Filtering out
already-installed packages" /><div class="longdesc"><div
class="para">
+ filtering out packages which are already installed
+ </div></div></div></div><h6>Figure 5.5. Filtering out
already-installed packages</h6></div><br class="figure-break"
/><div class="para">
+ <a id="id534686" class="indexterm"></a>
+ <a id="id534702" class="indexterm"></a>
+ <a id="id534718" class="indexterm"></a>
+ Also, unless we require development files such as C header files, we can filter for
<span class="guimenu"><strong>Only End User
Files</strong></span> and, in doing so, filter out all of the <code
class="filename"><em
class="replaceable"><code>package_name</code></em>-devel</code>
packages we are not interested in.
+ </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="Filtering out
development packages from the list of Find results" /><div
class="longdesc"><div class="para">
+ filtering out development packages from our results
+ </div></div></div></div><h6>Figure 5.6. Filtering out
development packages from the list of Find results</h6></div><br
class="figure-break" /><div class="para">
+ The two remaining filters with submenus are:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <span
class="guisubmenu"><strong>Graphical</strong></span> <a
id="id534796" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Narrows the search to either applications which provide a GUI interface (<span
class="guibutton"><strong>Only Graphical</strong></span>)
or those that do not. This filter is useful when browsing for GUI applications that
perform a specific function.
+ </div></dd><dt class="varlistentry"><span
class="term"> <span
class="guisubmenu"><strong>Free</strong></span> <a
id="id534836" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Search for packages which are considered to be free software Refer to the <a
href="https://fedoraproject.org/wiki/Licensing#SoftwareLicenses"...
Licensing List</a> for details on approved licenses.
+ </div></dd></dl></div><div class="para">
+ The remaining checkbox filters are always either checked or unchecked. They are:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <span
class="guimenuitem"><strong>Hide
Subpackages</strong></span> </span></dt><dd><div
class="para">
+ Checking the <span class="guimenuitem"><strong>Hide
Subpackages</strong></span> <a id="id534896"
class="indexterm"></a>
+ checkbox filters out generally-uninteresting packages that are typically only
dependencies of other packages that we want. For example, checking <span
class="guimenuitem"><strong>Hide
Subpackages</strong></span> and searching for <code
class="filename"><em
class="replaceable"><code>package</code></em> </code>
would cause the following related packages to be filtered out of the <span
class="guibutton"><strong>Find</strong></span> results (if
it exists):
+ </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>Only Newest
Packages</strong></span> </span></dt><dd><div
class="para">
+ Checking <span class="guimenuitem"><strong>Only Newest
Packages</strong></span> <a id="id535019"
class="indexterm"></a>
+ filters out all older versions of the same package from the list of results,
which is generally what we want.
+ </div><div class="important"
id="important-Using_the_Only_newest_items_filter"><div
class="admonition_header"><h2>Using the Only Newest Packages
filter</h2></div><div class="admonition"><div
class="para">
+ Checking <span class="guimenuitem"><strong>Only Newest
Packages</strong></span> filters out all but the most recent version of any
package from the results list. This filter is often combined with the <span
class="guimenuitem"><strong>Only Available</strong></span>
filter to search for the latest available versions of new (not installed) packages.
+ </div></div></div></dd><dt
class="varlistentry"><span class="term">Only native
packages</span></dt><dd><div class="para">
+ Checking the <span class="guimenuitem"><strong>Only Native
Packages</strong></span> <a id="id535078"
class="indexterm"></a>
+ box on a multilib system causes <span
class="application"><strong>PackageKit</strong></span> to
omit listing results for packages compiled for the architecture that runs in <span
class="emphasis"><em>compatibility mode</em></span>. For
example, enabling this filter on a 64-bit system with an AMD64 CPU would cause all
packages built for the 32-bit x86 CPU architecture not to be shown in the list of results,
even though those packages are able to run on an AMD64 machine. Packages which are
architecture-agnostic (i.e. <em class="firstterm">noarch</em>
packages such as <code
class="filename">crontabs-1.10-32.1.el6.noarch.rpm</code>) are never
filtered out by checking <span class="guimenuitem"><strong>Only
Native Packages</strong></span>. This filter has no affect on non-multilib
systems, such as x86 machines.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Using_Add_Remove_Software.html"><strong>Prev</strong>5.2. Using
Add/Remove Software</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>Next</strong>5.2.3. Installing
and Removing Packages (and
Depe...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing.html
new file mode 100644
index 0000000..9d9e177
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.2.4. Installing Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="4.2. Packages and
Package Groups" /><link rel="prev"
href="sec-Displaying_Package_Information.html" title="4.2.3. Displaying
Package Information" /><link rel="next"
href="sec-Removing.html" title="4.2.5. Removing Packages"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Displaying_Package_Information.html"><strong>Prev</
strong></a></li><li class="next"><a
accesskey="n"
href="sec-Removing.html"><strong>Next</strong></a></li></ul><div
class="section" id="sec-Installing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Installing">4.2.4. Installing
Packages</h3></div></div></div><a id="id613645"
class="indexterm"></a><a id="id613657"
class="indexterm"></a><div class="para">
+ You can install a package and all of its non-installed dependencies by entering:
+ </div><pre class="screen"><code
class="command">yum install <em
class="replaceable"><code>package_name</code></em></code></pre><div
class="para">
+ You can install multiple packages simultaneously by appending their names as
arguments:
+ </div><pre class="screen"><code
class="command">yum install <em
class="replaceable"><code>package_name</code></em>
[<span class="optional"><em
class="replaceable"><code>more_names</code></em></span>]</code></pre><div
class="para">
+ If you are installing packages on a <em
class="firstterm">multilib</em> system, such as an AMD64 or Intel 64
machine, you can specify the architecture of the package (as long as it is available in an
enabled repository) by appending <em
class="replaceable"><code>.arch</code></em> to the package
name. For example, to install the <span
class="package">sqlite2</span> package for <code
class="systemitem">i686</code>, type:
+ </div><pre class="screen">~]# <code
class="command">yum install sqlite2.i686</code></pre><div
class="para">
+ You can use glob expressions to quickly install multiple similarly-named packages:
+ </div><pre class="screen">~]# <code
class="command">yum install
audacious-plugins-\*</code></pre><div class="para">
+ In addition to package names and glob expressions, you can also provide file names to
<code class="command">yum install</code>. If you know the name of
the binary you want to install, but not its package name, you can give <code
class="command">yum install</code> the path name:
+ </div><pre class="screen">~]# <code
class="command">yum install /usr/sbin/named</code></pre><div
class="para">
+ <code class="command">yum</code> then searches through its
package lists, finds the package which provides <code
class="filename">/usr/sbin/named</code>, if any, and prompts you as to
whether you want to install it.
+ </div><div class="note"
id="note-Finding_which_package_owns_a_file"><div
class="admonition_header"><h2>Finding which package owns a
file</h2></div><div class="admonition"><div
class="para">
+ If you know you want to install the package that contains the <code
class="filename">named</code> binary, but you do not know in which
<code class="filename">bin</code> or <code
class="filename">sbin</code> directory is the file installed, use the
<code class="command">yum provides</code> command with a glob
expression:
+ </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>
is a common and useful trick to find the packages that contain <em
class="replaceable"><code>file_name</code></em>.
+ </div></div></div><h4> Installing a Package Group
</h4><a id="id613828" class="indexterm"></a><a
id="id613840" class="indexterm"></a><div
class="para">
+ A package group is similar to a package: it is not useful by itself, but installing
one pulls a group of dependent packages that serve a common purpose. A package group has a
name and a <em class="firstterm">groupid</em>. The <code
class="command">yum grouplist -v</code> command lists the names of all
package groups, and, next to each of them, their groupid in parentheses. The groupid is
always the term in the last pair of parentheses, such as <code
class="literal">kde-desktop</code> in the following example:
+ </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">
+ You can install a package group by passing its full group name (without the groupid
part) to <code class="command">groupinstall</code>, for example:
+ </div><pre class="screen">~]# <code
class="command">yum groupinstall "KDE Software
Compilation"</code></pre><div class="para">
+ You can also install by groupid:
+ </div><pre class="screen">~]# <code
class="command">yum groupinstall kde-desktop</code></pre><div
class="para">
+ You can even pass the groupid (or quoted name) to the <code
class="command">install</code> command if you prepend it with an
<span class="keysym">@</span>-symbol (which tells <code
class="command">yum</code> that you want to perform a <code
class="command">groupinstall</code>):
+ </div><pre class="screen">~]# <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>Prev</strong>4.2.3. Displaying
Package Information</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Removing.html"><strong>Next</strong>4.2.5. Removing
Packages</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.html
new file mode 100644
index 0000000..2f1958e
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.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>4.4.2. Installing Additional Yum Plugins</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Yum_Plugins.html" title="4.4. Yum Plugins" /><link
rel="prev" href="sec-Yum_Plugins.html" title="4.4. Yum
Plugins" /><link rel="next"
href="sec-Plugin_Descriptions.html" title="4.4.3. Plugin Descriptions"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="sec-Plugin_Description
s.html"><strong>Next</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"
id="sec-Installing_More_Yum_Plugins">4.4.2. Installing Additional Yum
Plugins</h3></div></div></div><div class="para">
+ <span
class="application"><strong>Yum</strong></span> plugins
usually adhere to the <code class="filename">yum-plugin-<em
class="replaceable"><code>plugin_name</code></em></code>
package-naming convention, but not always: the package which provides the <span
class="application"><strong>presto</strong></span> plugin
is named <code class="filename">yum-presto</code>, for example. You
can install a <span
class="application"><strong>Yum</strong></span> plugin in
the same way you install other packages. For instance, to install the <span
class="application"><strong>security</strong></span>
plugin, type the following at a shell prompt:
+ </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>Prev</strong>4.4. Yum
Plugins</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Plugin_Descriptions.html"><strong>Next</strong>4.4.3. Plugin
Descriptions</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.html
new file mode 100644
index 0000000..05e31fb
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.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>5.2.4. Installing and Removing Package Groups</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Using_Add_Remove_Software.html" title="5.2. Using Add/Remove
Software" /><link rel="prev"
href="sec-Installing_and_Removing_Packages_and_Dependencies.html"
title="5.2.3. Installing and Removing Packages (and Dependencies)" /><link
rel="next" href="sec-Viewing_the_Transaction_Log.html"
title="5.2.5. Viewing the Transaction Log" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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_Removing_Packages_and_Dependencies.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Viewing_the_Transaction_Log.html"><strong>Next</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"
id="sec-Installing_and_Removing_Package_Groups">5.2.4. Installing and
Removing Package Groups</h3></div></div></div><a
id="id544981" class="indexterm"></a><a
id="id544993" class="indexterm"></a><a
id="id545005" class="indexterm"></a><a
id="id545016" class="indexterm"></a><div
class="para">
+ <span
class="application"><strong>PackageKit</strong></span> also
has the ability to install <span
class="application"><strong>Yum</strong></span> package
groups, which it calls <span class="guilabel"><strong>Package
collections</strong></span>. Clicking on <span
class="guilabel"><strong>Package
collections</strong></span> in the top-left list of categories in the <span
class="guilabel"><strong>Software Updates</strong></span>
window allows us to scroll through and find the package group we want to install. In this
case, we want to install Czech language support (the <span
class="guilabel"><strong>Czech Support</strong></span>
group). Checking the box and clicking <span
class="guibutton"><strong>Apply</strong></span> informs us
how many <span
class="emphasis"><em>additional</em></span> packages must
be installed in order to fulfill the dependencies of the package group.
+ </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="Installing the
Czech Support package group" /><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>Figure 5.9. Installing
the Czech Support package group</h6></div><br
class="figure-break" /><div class="para">
+ Similarly, installed package groups can be uninstalled by selecting <span
class="guilabel"><strong>Package
collections</strong></span>, unchecking the appropriate checkbox, and
applying.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>Prev</strong>5.2.3. Installing
and Removing Packages (and Depe...</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Viewing_the_Transaction_Log.html"><strong>Next</strong>5.2.5. Viewing
the Transaction Log</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html
new file mode 100644
index 0000000..e17581a
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.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>5.2.3. Installing and Removing Packages (and
Dependencies)</title><link rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Using_Add_Remove_Software.html" title="5.2. Using Add/Remove
Software" /><link rel="prev"
href="sec-Finding_Packages_with_Filters.html" title="5.2.2. Finding
Packages with Filters" /><link rel="next"
href="sec-Installing_and_Removing_Package_Groups.html"
title="5.2.4. Installing and Removing Package Groups" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Findin
g_Packages_with_Filters.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing_and_Removing_Package_Groups.html"><strong>Next</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"
id="sec-Installing_and_Removing_Packages_and_Dependencies">5.2.3. Installing
and Removing Packages (and
Dependencies)</h3></div></div></div><a id="id535129"
class="indexterm"></a><a id="id535140"
class="indexterm"></a><div class="para">
+ With the two filters selected, <span
class="guibutton"><strong>Only Available</strong></span>
and <span class="guibutton"><strong>Only End User
Files</strong></span>, search for the <span
class="application"><strong>htop</strong></span>
interactive process viewer and highlight the package. You now have access to some very
useful information about it, including: a clickable link to the project homepage; the
<span class="application"><strong>Yum</strong></span>
package group it is found in, if any; the license of the package; a pointer to the GNOME
menu location from where the application can be opened, if applicable; and the size of the
package, which is relevant when we download and install it.
+ </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="Viewing and installing a
package with PackageKit's Add/Remove Software window" /><div
class="longdesc"><div class="para">
+ Viewing and installing a package with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>Figure 5.7. Viewing and
installing a package with PackageKit's Add/Remove Software
window</h6></div><br class="figure-break" /><div
class="para">
+ When the checkbox next to a package or group is checked, then that item is already
installed on the system. Checking an unchecked box causes it to be <span
class="emphasis"><em>marked</em></span> for installation,
which only occurs when the <span
class="guibutton"><strong>Apply</strong></span> button is
clicked. In this way, you can search for and select multiple packages or package groups
before performing the actual installation transactions. Additionally, you can remove
installed packages by unchecking the checked box, and the removal will occur along with
any pending installations when <span
class="guibutton"><strong>Apply</strong></span> is pressed.
Dependency resolution
+ <a id="id544804" class="indexterm"></a>
+ , which may add additional packages to be installed or removed, is performed after
pressing <span
class="guibutton"><strong>Apply</strong></span>. <span
class="application"><strong>PackageKit</strong></span> will
then display a window listing those additional packages to install or remove, and ask for
confirmation to proceed.
+ </div><div class="para">
+ Check <span
class="application"><strong>htop</strong></span> and click
the <span
class="guibutton"><strong>Apply</strong></span> button. You
will then be prompted for the superuser password; enter it, and <span
class="application"><strong>PackageKit</strong></span> will
install <span
class="application"><strong>htop</strong></span>. One nice
feature of <span
class="application"><strong>PackageKit</strong></span> is
that, following installation, it sometimes presents you with a list of your
newly-installed applications and offer you the choice of running them immediately.
Alternatively, you will remember that finding a package and selecting it in the <span
class="guilabel"><strong>Add/Remove
Software</strong></span> window shows you the <span
class="guilabel"><strong>Location</strong></span> of where
in the GNOME menus its application shortcut is located, which is helpful when you want to
run it.
+ </div><div class="para">
+ Once it is installed, you can run <code
class="command">htop</code>, a colorful and enhanced version of the
<code class="command">top</code> process viewer, by opening a shell
prompt and entering:
+ </div><pre class="screen"><code
class="command">htop</code></pre><div
class="para">
+ <span
class="application"><strong>htop</strong></span> is nifty,
but we decide that <code class="command">top</code> is good enough
for us and we want to uninstall it. Remembering that we need to change the <span
class="guibutton"><strong>Only Available</strong></span>
filter we recently used to install it to <span
class="guibutton"><strong>Only Installed</strong></span> in
<span class="guimenu"><strong>Filters</strong></span> →
<span
class="guimenuitem"><strong>Installed</strong></span>, we
search for <span
class="application"><strong>htop</strong></span> again and
uncheck it. The program did not install any dependencies of its own; if it had, those
would be automatically removed as well, as long as they were not also dependencies of any
other packages still installed on our system.
+ </div><div class="warning"
id="warning-PackageKit-Removing_a_Package_Without_Removing_Packages_Depending_on_It"><div
class="admonition_header"><h2>Removing a package when other packages
depend on it</h2></div><div class="admonition"><div
class="para">
+ Although <span
class="application"><strong>PackageKit</strong></span>
automatically resolves dependencies during package installation and removal, it is unable
to remove a package without also removing packages which depend on it. This type of
operation can only be performed by <span
class="application"><strong>RPM</strong></span>, is not
advised, and can potentially leave your system in a non-functioning state or cause
applications to misbehave and/or crash.
+ </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="Removing a package with
PackageKit's Add/Remove Software window" /><div
class="longdesc"><div class="para">
+ Removing the htop package with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>Figure 5.8. Removing a
package with PackageKit's Add/Remove Software window</h6></div><br
class="figure-break" /></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Finding_Packages_with_Filters.html"><strong>Prev</strong>5.2.2. Finding
Packages with Filters</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing_and_Removing_Package_Groups.html"><strong>Next</strong>5.2.4. Installing
and Removing Package Groups</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Upgrading.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Upgrading.html
new file mode 100644
index 0000000..b36fca9
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Installing_and_Upgrading.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>A.2.2. Installing and Upgrading</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="s1-rpm-using.html" title="A.2. Using RPM" /><link
rel="prev" href="s1-rpm-using.html" title="A.2. Using RPM"
/><link rel="next" href="sec-Configuration_File_Changes.html"
title="A.2.3. Configuration File Changes" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" href="sec-Configuration_Fil
e_Changes.html"><strong>Next</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"
id="sec-Installing_and_Upgrading">A.2.2. Installing and
Upgrading</h3></div></div></div><a id="id612352"
class="indexterm"></a><a id="id631419"
class="indexterm"></a><a id="id594643"
class="indexterm"></a><a id="id676152"
class="indexterm"></a><div class="para">
+ RPM packages typically have file names
+ <a id="id637232" class="indexterm"></a>
+ like <code
class="filename">tree-1.5.3-2.fc15.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">fc15</code>) and CPU architecture (<code
class="filename">x86_64</code>).
+ </div><div class="para">
+ You can use <code class="command">rpm</code>'s <code
class="option">-U</code> option to:
+ </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.fc15.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.fc15.x86_64.rpm</code>
+</pre><div class="note"
id="note-Use_-Uvh_for_nicely-formatted_RPM_installs"><div
class="admonition_header"><h2>Use -Uvh for nicely-formatted RPM
installs</h2></div><div class="admonition"><div
class="para">
+ The <code class="option">-v</code> and <code
class="option">-h</code> options (which are combined with <code
class="option">-U</code>) cause <span
class="application"><strong>rpm</strong></span> to print
more verbose output and display a progress meter using hash signs.
+ </div></div></div><div class="para">
+ If the upgrade/installation is successful, the following output is displayed:
+ </div><pre class="screen">Preparing...
########################################### [100%]
+ 1:tree ###########################################
[100%]</pre><div class="warning"
id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages"><div
class="admonition_header"><h2>Always use the -i (install) option to
install new kernel packages!</h2></div><div
class="admonition"><div class="para">
+ <code class="command">rpm</code> provides two different
options for installing packages: the aforementioned <code
class="option">-U</code> option (which historically stands for <span
class="emphasis"><em>upgrade</em></span>), and the <code
class="option">-i</code> option, 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">Chapter 20, <em>Manually
Upgrading the Kernel</em></a>.
+ </div></div></div><div class="para">
+ The signature of a package is checked automatically when installing or upgrading a
package. The signature confirms that the package was signed by an authorized party. For
example, if the verification of the signature fails, an error message such as the
following is displayed:
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc15.x86_64.rpm:
Header V3 RSA/SHA256 signature: BAD, key ID
+d22e77f2</pre><div class="para">
+ If it is a new, header-only, signature, an error message such as the following is
displayed:
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc15.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.fc15.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">Section A.3, “Checking a Package's
Signature”</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"
id="s3-rpm-errors">A.2.2.1. Package Already
Installed</h4></div></div></div><div
class="para">
+ If a package of the same name and version is already installed
+ <a id="id529013" class="indexterm"></a>
+ <a id="id529025" class="indexterm"></a>
+ , the following output is displayed:
+ </div><pre class="screen">Preparing...
########################################### [100%]
+ package tree-1.5.3-2.fc15.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.fc15.x86_64.rpm</code>
+</pre><div class="para">
+ This option is helpful if files installed from the RPM were deleted or if you want
the original configuration files from the RPM to be installed.
+ </div></div><div class="section"
id="s3-rpm-conflicting-files"><div
class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="s3-rpm-conflicting-files">A.2.2.2. Conflicting
Files</h4></div></div></div><a id="id421295"
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="id703953" class="indexterm"></a>
+ <a id="id703965" class="indexterm"></a>
+ , the following is displayed:
+ </div><pre class="screen">Preparing...
##################################################
+ file /usr/bin/foobar from install of foo-1.0-1.fc15.x86_64 conflicts
+with file from package bar-3.1.1.fc15.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.fc15.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"
id="s3-rpm-unresolved-dependency">A.2.2.3. Unresolved
Dependency</h4></div></div></div><a id="id420915"
class="indexterm"></a><a id="id675572"
class="indexterm"></a><div class="para">
+ RPM packages may sometimes depend on other packages
+ <a id="id579356" class="indexterm"></a>
+ <a id="id579368" 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.fc15.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.fc15.x86_64.rpm
bar-3.1.1.fc15.x86_64.rpm</code>
+</pre><div class="para">
+ If installation of both packages is successful, output similar to the following is
displayed:
+ </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">
+ If the package that contains <code
class="filename">bar.so.3</code> is in the RPM database, the name of
the package is displayed:
+ </div><pre
class="screen">bar-3.1.1.fc15.i586.rpm</pre><div
class="warning"
id="warning-install-Warning-Forcing_Package_Installation"><div
class="admonition_header"><h2>Warning: Forcing Package
Installation</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>Prev</strong>A.2. Using
RPM</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Configuration_File_Changes.html"><strong>Next</strong>A.2.3. Configuration
File Changes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Listing_Packages.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Listing_Packages.html
new file mode 100644
index 0000000..12b379c
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Listing_Packages.html
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Listing Packages</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="4.2. Packages and
Package Groups" /><link rel="prev"
href="sec-Packages_and_Package_Groups.html" title="4.2. Packages and
Package Groups" /><link rel="next"
href="sec-Displaying_Package_Information.html" title="4.2.3. Displaying
Package Information" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Packages_and_Package_Gro
ups.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Displaying_Package_Information.html"><strong>Next</strong></a></li></ul><div
class="section" id="sec-Listing_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Listing_Packages">4.2.2. Listing
Packages</h3></div></div></div><a id="id529814"
class="indexterm"></a><a id="id529830"
class="indexterm"></a><div class="para">
+ <code class="command">yum list</code> and related commands
provide information about packages, package groups, and repositories.
+ </div><div class="para">
+ All of <span
class="application"><strong>Yum</strong></span>'s list
commands allow you to filter the results by appending one or more <em
class="firstterm">glob expressions</em> as arguments. Glob expressions
are normal strings of characters which contain one or more of the wildcard characters
<code class="command">*</code> (which expands to match any character
multiple times) and <code class="command">?</code> (which expands to
match any one character).
+ </div><div class="note"
id="note-Tip-Filtering_Results_with_Glob_Expressions"><div
class="admonition_header"><h2>Filtering results with glob
expressions</h2></div><div class="admonition"><a
id="id529882" class="indexterm"></a><a
id="id529898" class="indexterm"></a><div
class="para">
+ Be careful to escape the glob expressions when passing them as arguments to a
<code class="command">yum</code> command, otherwise the Bash shell
will interpret these expressions as <em class="firstterm">pathname
expansions</em>, and potentially pass all files in the current directory that match
the globs to <code class="command">yum</code>. To make sure the glob
expressions are passed to <code class="command">yum</code> as
intended, either:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ escape the wildcard characters by preceding them with a backslash character
+ </div></li><li class="listitem"><div
class="para">
+ double-quote or single-quote the entire glob expression.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref"
href="sec-Listing_Packages.html#ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions">Example 4.1,
“Listing all ABRT addons and plugins using glob expressions”</a> and <a
class="xref"
href="sec-Listing_Packages.html#ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards">Example 4.4,
“Listing available packages using a single glob expression with escaped wildcard
characters”</a> for an example usage of both these methods.
+ </div></div></div><div
class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="command">yum list <em
class="replaceable"><code>glob_expr</code></em> [<span
class="optional"><em
class="replaceable"><code>more_glob_exprs</code></em></span>]</code>
</span></dt><dd><div class="para">
+ Lists information on installed and available packages matching all glob
expressions.
+ </div><div class="example"
id="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions"><h6>Example 4.1. Listing
all ABRT addons and plugins using glob expressions</h6><div
class="example-contents"><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="id530027"
class="indexterm"></a>
+ <a id="id426751" class="indexterm"></a>
+ <code class="command">yum list all</code>
</span></dt><dd><div class="para">
+ Lists all installed <span
class="emphasis"><em>and</em></span> available packages.
+ </div><div class="example"
id="ex-Listing_all_installed_and_available_packages"><h6>Example 4.2. Listing
all installed and available packages</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">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="id426817" class="indexterm"></a>
+ <a id="id426833" class="indexterm"></a>
+ <code class="command">yum list installed</code>
</span></dt><dd><div class="para">
+ Lists all packages installed on your system. The rightmost column in the output
lists the repository from which the package was retrieved.
+ </div><div class="example"
id="ex-Listing_installed_packages_using_a_double-quoted_glob_expression"><h6>Example 4.3. Listing
installed packages using a double-quoted glob expression</h6><div
class="example-contents"><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="id426890"
class="indexterm"></a>
+ <a id="id426906" class="indexterm"></a>
+ <code class="command">yum list available</code>
</span></dt><dd><div class="para">
+ Lists all available packages in all enabled repositories.
+ </div><div class="example"
id="ex-Listing_available_packages_using_a_single_glob_expression_with_escaped_wildcards"><h6>Example 4.4. Listing
available packages using a single glob expression with escaped wildcard
characters</h6><div class="example-contents"><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="id426966"
class="indexterm"></a>
+ <a id="id426982" class="indexterm"></a>
+ <code class="command">yum grouplist</code>
</span></dt><dd><div class="para">
+ Lists all package groups.
+ </div><div class="example"
id="ex-Listing_all_package_groups"><h6>Example 4.5. Listing all package
groups</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">[output
truncated]</span></em></pre></div></div><br
class="example-break" /></dd><dt
class="varlistentry"><span class="term"> <a
id="id427039" class="indexterm"></a>
+ <a id="id427055" class="indexterm"></a>
+ <code class="command">yum repolist</code>
</span></dt><dd><div class="para">
+ Lists the repository ID, name, and number of packages it provides for each
<span class="emphasis"><em>enabled</em></span>
repository.
+ </div><div class="example"
id="ex-Listing_enabled_repositories"><h6>Example 4.6. Listing enabled
repositories</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>Prev</strong>4.2. Packages
and Package Groups</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Displaying_Package_Information.html"><strong>Next</strong>4.2.3. Displaying
Package Information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Loading_a_Module.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Loading_a_Module.html
new file mode 100644
index 0000000..31e36d4
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Loading_a_Module.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>21.3. Loading 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.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. Working with
Kernel Modules" /><link rel="prev"
href="sec-Displaying_Information_About_a_Module.html"
title="21.2. Displaying Information About a Module" /><link
rel="next" href="sec-Unloading_a_Module.html"
title="21.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_Informatio
n_About_a_Module.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Unloading_a_Module.html"><strong>Next</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"
id="sec-Loading_a_Module">21.3. Loading a
Module</h2></div></div></div><a id="id440503"
class="indexterm"></a><a id="id563063"
class="indexterm"></a><a id="id431992"
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="id446399"
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>Example 21.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="id669530" class="indexterm"></a><a
id="id628016" 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>Prev</strong>21.2. Displaying
Information About a Module</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Unloading_a_Module.html"><strong>Next</strong>21.4. Unloading
a Module</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-PackageKit_Architecture.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-PackageKit_Architecture.html
new file mode 100644
index 0000000..7999885
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-PackageKit_Architecture.html
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-PackageKit.html" title="Chapter 5. PackageKit" /><link
rel="prev" href="sec-Viewing_the_Transaction_Log.html"
title="5.2.5. Viewing the Transaction Log" /><link rel="next"
href="ch-Graphical_Package_Management-sec-Additional_Resources.html"
title="5.4. Additional Resources" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Viewing_the_Transaction_Log.html"><stron
g>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="sec-PackageKit_Architecture"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-PackageKit_Architecture">5.3. PackageKit
Architecture</h2></div></div></div><a id="id545274"
class="indexterm"></a><div class="para">
+ Fedora provides the <span
class="application"><strong>PackageKit</strong></span>
suite of applications for viewing, updating, installing and uninstalling packages and
package groups compatible with your system. Architecturally, <span
class="application"><strong>PackageKit</strong></span>
consists of several graphical front ends that communicate with the <code
class="command">packagekitd</code> daemon back end, which communicates
with a package manager-specific back end that utilizes <span
class="application"><strong>Yum</strong></span> to perform
the actual transactions, such as installing and removing packages, etc.
+ </div><div class="para">
+ <a class="xref"
href="sec-PackageKit_Architecture.html#table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands">Table 5.1,
“PackageKit GUI windows, menu locations, and shell prompt commands”</a> shows the
name of the GUI window, how to start the window from the GNOME desktop or from the
<span class="guilabel"><strong>Add/Remove
Software</strong></span> window, and the name of the command line application
that opens that window.
+ </div><div class="table"
id="table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands"><h6>Table 5.1. PackageKit
GUI windows, menu locations, and shell prompt commands</h6><div
class="table-contents"><table summary="PackageKit GUI windows, menu
locations, and shell prompt commands" 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 align="left">
+ Window Title
+ </th><th align="left">
+ Function
+ </th><th align="left">
+ How to Open
+ </th><th align="left">
+ Shell Command
+ </th></tr></thead><tbody><tr><td
align="left">
+ Add/Remove Software
+ </td><td align="left">
+ Install, remove or view package info
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Administration</strong></span>
→ <span class="guimenuitem"><strong>Add/Remove
Software</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-application
+ </td></tr><tr><td align="left">
+ Software Update
+ </td><td align="left">
+ Perform package updates
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Administration</strong></span>
→ <span class="guimenuitem"><strong>Software
Update</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-update-viewer
+ </td></tr><tr><td align="left">
+ Software Sources
+ </td><td align="left">
+ Enable and disable <span
class="application"><strong>Yum</strong></span>
repositories
+ </td><td align="left">
+ <div class="para">
+ From <span class="guilabel"><strong>Add/Remove
Software</strong></span>: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software
Sources</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-repo
+ </td></tr><tr><td align="left">
+ Software Log Viewer
+ </td><td align="left">
+ View the transaction log
+ </td><td align="left">
+ <div class="para">
+ From <span class="guilabel"><strong>Add/Remove
Software</strong></span>: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software Log</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-log
+ </td></tr><tr><td align="left">
+ Software Update Preferences
+ </td><td align="left">
+ Set <span
class="application"><strong>PackageKit</strong></span>
preferences
+ </td><td align="left">
+ </td><td align="left">
+ gpk-prefs
+ </td></tr><tr><td align="left">
+ (Notification Area Alert)
+ </td><td align="left">
+ Alerts you when updates are available
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Preferences</strong></span> →
<span class="guimenuitem"><strong>Startup
Applications</strong></span>, <span
class="guilabel"><strong>Startup Programs</strong></span>
tab
+ </div>
+
+ </td><td align="left">
+ gpk-update-icon
+ </td></tr></tbody></table></div></div><br
class="table-break" /><div class="para">
+ The <code class="command">packagekitd</code> daemon runs outside
the user session and communicates with the various graphical front ends. The <code
class="command">packagekitd</code> daemon<sup>[<a
id="footnote-Daemons" href="#ftn.footnote-Daemons"
class="footnote">1</a>]</sup> communicates via the <span
class="application"><strong>DBus</strong></span> system
message bus with another back end, which utilizes <span
class="application"><strong>Yum</strong></span>'s
Python API to perform queries and make changes to the system. On Linux systems other than
Red Hat Enterprise Linux and Fedora, <code
class="command">packagekitd</code> can communicate with other back ends
that are able to utilize the native package manager for that system. This modular
architecture provides the abstraction necessary for the graphical interfaces to work with
many different package managers to perform essentially the same types of package
management tasks. Learning how to use the <span class="appli
cation"><strong>PackageKit</strong></span> front ends means
that you can use the same familiar graphical interface across many different Linux
distributions, even when they utilize a native package manager other than <span
class="application"><strong>Yum</strong></span>.
+ </div><div class="para">
+ In addition, <span
class="application"><strong>PackageKit</strong></span>'s
separation of concerns provides reliability in that a crash of one of the GUI windows—or
even the user's X Window session—will not affect any package management tasks being
supervised by the <code class="command">packagekitd</code> daemon,
which runs outside of the user session.
+ </div><div class="para">
+ All of the front end graphical applications discussed in this chapter are provided by
the <code class="filename">gnome-packagekit</code> package instead
of by <span
class="application"><strong>PackageKit</strong></span> and
its dependencies. Users working in a KDE environment may prefer to install the <code
class="filename">kpackagekit</code> package, which provides a KDE
interface for <span
class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Finally, <span
class="application"><strong>PackageKit</strong></span> also
comes with a console-based front end called <code
class="command">pkcon</code>.
+ </div><div class="footnotes"><br /><hr /><div
class="footnote" id="footnote-Daemons"><div
class="para"><sup>[<a id="ftn.footnote-Daemons"
href="#footnote-Daemons" class="para">1</a>] </sup>
+ System daemons are typically long-running processes that provide services to the user
or to other programs, and which are started, often at boot time. Daemons respond to the
<code class="command">systemctl</code> command and can be turned on
or off permanently by using the <code class="command">systemctl
enable</code> or <code class="command">systemctl
disable</code>commands. They can typically be recognized by a <span
class="quote">“<span class="quote"><span
class="emphasis"><em>d</em></span></span>”</span>
appended to their name, such as the <code
class="command">packagekitd</code> daemon. Refer to <a
class="xref" href="ch-Services_and_Daemons.html">Chapter 7,
<em>Services and Daemons</em></a> for information about system
services.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Viewing_the_Transaction_Log.html"><strong>Prev</strong>5.2.5. Viewing
the Transaction Log</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>Next</strong>5.4. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Packages_and_Package_Groups.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Packages_and_Package_Groups.html
new file mode 100644
index 0000000..79fa5bc
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Packages_and_Package_Groups.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>4.2. Packages and Package Groups</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-yum.html" title="Chapter 4. Yum" /><link
rel="prev" href="ch-yum.html" title="Chapter 4. Yum"
/><link rel="next" href="sec-Listing_Packages.html"
title="4.2.2. Listing Packages" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-yum.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Listing_Packages.html"><strong>Next</strong></a></li>
</ul><div class="section"
id="sec-Packages_and_Package_Groups"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-Packages_and_Package_Groups">4.2. Packages and Package
Groups</h2></div></div></div><a id="id443702"
class="indexterm"></a><a id="id443714"
class="indexterm"></a><div class="section"
id="sec-Searching_Packages"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Searching_Packages">4.2.1. Searching
Packages</h3></div></div></div><a id="id529729"
class="indexterm"></a><a id="id529744"
class="indexterm"></a><div class="para">
+ You can search all <acronym class="acronym">RPM</acronym>
package names, descriptions and summaries by using the <code
class="command">yum search <em
class="replaceable"><code>term</code></em> [<span
class="optional"><em
class="replaceable"><code>more_terms</code></em></span>]</code>
command. <code class="command">yum</code> displays the list of
matches for each term, for example:
+ </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><div class="para">
+ The <code class="command">yum search</code> command is useful
for searching for packages you do not know the name of, but for which you know a related
term.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-yum.html"><strong>Prev</strong>Chapter 4. Yum</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Listing_Packages.html"><strong>Next</strong>4.2.2. Listing
Packages</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Persistent_Module_Loading.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Persistent_Module_Loading.html
new file mode 100644
index 0000000..68c93de
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Persistent_Module_Loading.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.6. 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. Working with
Kernel Modules" /><link rel="prev"
href="sec-Setting_Module_Parameters.html" title="21.5. Setting Module
Parameters" /><link rel="next"
href="sec-Specific_Kernel_Module_Capabilities.html" title="21.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-Setting_Mod
ule_Parameters.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Specific_Kernel_Module_Capabilities.html"><strong>Next</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"
id="sec-Persistent_Module_Loading">21.6. Persistent Module
Loading</h2></div></div></div><a id="id670690"
class="indexterm"></a><a id="id670706"
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">Example 21.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>Example 21.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>Prev</strong>21.5. Setting
Module Parameters</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Specific_Kernel_Module_Capabilities.html"><strong>Next</strong>21.7. Specific
Kernel Module Capabilities</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Plugin_Descriptions.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Plugin_Descriptions.html
new file mode 100644
index 0000000..4a80801
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Plugin_Descriptions.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>4.4.3. Plugin Descriptions</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Yum_Plugins.html" title="4.4. Yum Plugins" /><link
rel="prev" href="sec-Installing_More_Yum_Plugins.html"
title="4.4.2. Installing Additional Yum Plugins" /><link
rel="next" href="sec-Additional_Resources.html"
title="4.5. Additional Resources" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Installing_More_Yum_Plugins.html"><strong>Prev</strong></a></li><li
cl
ass="next"><a accesskey="n"
href="sec-Additional_Resources.html"><strong>Next</strong></a></li></ul><div
class="section" id="sec-Plugin_Descriptions"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Plugin_Descriptions">4.4.3. Plugin
Descriptions</h3></div></div></div><div
class="para">
+ The following are descriptions of a few commonly installed <span
class="application"><strong>Yum</strong></span> plugins:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <a
id="id420203" class="indexterm"></a>
+ <span
class="application"><strong>presto</strong></span>
(<span class="package">yum-presto</span>)
</span></dt><dd><div class="para">
+ The <span
class="application"><strong>presto</strong></span> plugin
adds support to <span
class="application"><strong>Yum</strong></span> for
downloading <em class="firstterm">delta RPM</em> packages, during
updates, from repositories which have <span
class="application"><strong>presto</strong></span> metadata
enabled. Delta RPMs contain only the differences between the version of the package
installed on the client requesting the RPM package and the updated version in the
repository.
+ </div><div class="para">
+ Downloading a delta RPM is much quicker than downloading the entire updated
package, and can speed up updates considerably. Once the delta RPMs are downloaded, they
must be rebuilt to apply the difference to the currently-installed package and thus create
the full, updated package. This process takes CPU time on the installing machine. Using
delta RPMs is therefore a tradeoff between time-to-download, which depends on the network
connection, and time-to-rebuild, which is CPU-bound. Using the <span
class="application"><strong>presto</strong></span> plugin
is recommended for fast machines and systems with slower network connections, while slower
machines on very fast connections <span
class="emphasis"><em>may</em></span> benefit more from
downloading normal RPM packages, that is, by disabling <span
class="application"><strong>presto</strong></span>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id420300"
class="indexterm"></a>
+ <span
class="application"><strong>refresh-packagekit</strong></span>
(<span class="package">PackageKit-yum-plugin</span>)
</span></dt><dd><div class="para">
+ The <span
class="application"><strong>refresh-packagekit</strong></span>
plugin updates metadata for <span
class="application"><strong>PackageKit</strong></span>
whenever <code class="command">yum</code> is run. The <span
class="application"><strong>refresh-packagekit</strong></span>
plugin is installed by default.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id420357"
class="indexterm"></a>
+ <span
class="application"><strong>rhnplugin</strong></span>
(<span class="package">yum-rhn-plugin</span>)
</span></dt><dd><div class="para">
+ The <span
class="application"><strong>rhnplugin</strong></span>
provides support for connecting to <code class="systemitem">RHN
Classic</code>. This allows systems registered with <code
class="systemitem">RHN Classic</code> to update and install packages
from this system.
+ </div><div class="para">
+ Refer to <code class="command">man rhnplugin</code> for more
information about the plugin.
+ </div></dd><dt class="varlistentry"><span
class="term"> <a id="id420423"
class="indexterm"></a>
+ <span
class="application"><strong>security</strong></span>
(<span class="package">yum-plugin-security</span>)
</span></dt><dd><div class="para">
+ Discovering information about and applying security updates easily and often is
important to all system administrators. For this reason <span
class="application"><strong>Yum</strong></span> provides
the <span
class="application"><strong>security</strong></span>
plugin, which extends <code class="command">yum</code> with a set of
highly-useful security-related commands, subcommands and options.
+ </div><div class="para">
+ You can check for security-related updates as follows:
+ </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">[output
truncated]</span></em></pre><div class="para">
+ You can then use either <code class="command">yum update
--security</code> or <code class="command">yum update-minimal
--security</code> to update those packages which are affected by security
advisories. Both of these commands update all packages on the system for which a security
advisory has been issued. <code class="command">yum update-minimal
--security</code> updates them to the latest packages which were released as part of
a security advisory, while <code class="command">yum update
--security</code> will update all packages affected by a security advisory <span
class="emphasis"><em>to the latest version of that package
available</em></span>.
+ </div><div class="para">
+ In other words, if:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ the <span class="package">kernel-2.6.38.4-20</span>
package is installed on your system;
+ </div></li><li class="listitem"><div
class="para">
+ the <span class="package">kernel-2.6.38.6-22</span>
package was released as a security update;
+ </div></li><li class="listitem"><div
class="para">
+ then <span class="package">kernel-2.6.38.6-26</span> was
released as a bug fix update,
+ </div></li></ul></div><div class="para">
+ ...then <code class="command">yum update-minimal
--security</code> will update you to <span
class="package">kernel-2.6.38.6-22</span>, and <code
class="command">yum update --security</code> will update you to
<span class="package">kernel-2.6.38.6-26</span>. Conservative system
administrators may want to use <code
class="command">update-minimal</code> to reduce the risk incurred by
updating packages as much as possible.
+ </div><div class="para">
+ Refer to <code class="command">man yum-security</code> for
usage details and further explanation of the enhancements the <span
class="application"><strong>security</strong></span> plugin
adds to <code class="command">yum</code>.
+ </div></dd></dl></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Installing_More_Yum_Plugins.html"><strong>Prev</strong>4.4.2. Installing
Additional Yum Plugins</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Additional_Resources.html"><strong>Next</strong>4.5. Additional
Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Removing.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Removing.html
new file mode 100644
index 0000000..2402eb6
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Removing.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>4.2.5. Removing Packages</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Packages_and_Package_Groups.html" title="4.2. Packages and
Package Groups" /><link rel="prev"
href="sec-Installing.html" title="4.2.4. Installing Packages"
/><link rel="next"
href="sec-Configuring_Yum_and_Yum_Repositories.html"
title="4.3. Configuring Yum and Yum Repositories" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Installing.html"><strong>Prev</strong
</a></li><li class="next"><a
accesskey="n"
href="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>Next</strong></a></li></ul><div
class="section" id="sec-Removing"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sec-Removing">4.2.5. Removing
Packages</h3></div></div></div><a id="id613943"
class="indexterm"></a><a id="id613954"
class="indexterm"></a><a id="id613966"
class="indexterm"></a><a id="id613982"
class="indexterm"></a><div class="para">
+ The
<code class="command">yum remove <em
class="replaceable"><code>package_name</code></em></code>
uninstalls (removes in <span
class="application"><strong>RPM</strong></span> and
<span class="application"><strong>Yum</strong></span>
terminology) the package, as well as any packages that depend on it. As when you install
multiple packages, you can remove several at once by adding more package names to the
command. For example, to remove <span class="package">totem</span>,
<span class="package">rhythmbox</span>, and <span
class="package">sound-juicer</span>, type the following at a shell
prompt:
+ </div><pre class="screen">~]# <code
class="command">yum remove totem rhythmbox
sound-juicer</code></pre><div class="para">
+ Similar to <code class="command">install</code>, <code
class="command">remove</code> can take these arguments:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ package names
+ </div></li><li class="listitem"><div
class="para">
+ glob expressions
+ </div></li><li class="listitem"><div
class="para">
+ file lists
+ </div></li><li class="listitem"><div
class="para">
+ package provides
+ </div></li></ul></div><div class="warning"
id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It"><div
class="admonition_header"><h2>Removing a package when other packages
depend on it</h2></div><div class="admonition"><div
class="para">
+ <span
class="application"><strong>Yum</strong></span> is not able
to remove a package without also removing packages which depend on it. This type of
operation can only be performed by <span
class="application"><strong>RPM</strong></span>, is not
advised, and can potentially leave your system in a non-functioning state or cause
applications to misbehave and/or crash. For further information, refer to <a
class="xref" href="s2-rpm-uninstalling.html">Section A.2.4,
“Uninstalling”</a> in the <span
class="application"><strong>RPM</strong></span> chapter.
+ </div></div></div><h4> Removing a Package Group
</h4><div class="para">
+ You can remove a package group using syntax congruent with the <code
class="command">install</code> syntax. The following are alternative
but equivalent ways of removing the <code class="literal">KDE Software
Compilation</code> group:
+ </div><pre class="screen">~]# <code
class="command">yum groupremove "KDE Software
Compilation"</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>Intelligent package group
removal</h2></div><div class="admonition"><a
id="id614155" class="indexterm"></a><a
id="id614167" class="indexterm"></a><div
class="para">
+ When you tell <span
class="application"><strong>yum</strong></span> to remove a
package group, it will remove every package in that group, even if those packages are
members of other package groups or dependencies of other installed packages. However, you
can instruct <code class="command">yum</code> to remove only those
packages which are not required by any other packages or groups by adding the <code
class="option">groupremove_leaf_only=1</code> directive to the <code
class="literal">[main]</code> section of the <code
class="filename">/etc/yum.conf</code> configuration file. For more
information on this directive, refer to <a class="xref"
href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">Section 4.3.1,
“Setting [main] Options”</a>.
+ </div></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sec-Installing.html"><strong>Prev</strong>4.2.4. Installing
Packages</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>Next</strong>4.3. Configuring
Yum and Yum Repositories</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Setting_Module_Parameters.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Setting_Module_Parameters.html
new file mode 100644
index 0000000..4f28f88
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Setting_Module_Parameters.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>21.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. Working with
Kernel Modules" /><link rel="prev"
href="sec-Unloading_a_Module.html" title="21.4. Unloading a Module"
/><link rel="next" href="sec-Persistent_Module_Loading.html"
title="21.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>Prev</strong
</a></li><li class="next"><a
accesskey="n"
href="sec-Persistent_Module_Loading.html"><strong>Next</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"
id="sec-Setting_Module_Parameters">21.5. Setting Module
Parameters</h2></div></div></div><a id="id675477"
class="indexterm"></a><a id="id471693"
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">Section 21.6, “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>Procedure 21.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">Section 21.4, “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<sup>[<a
id="footnote-Energy_Efficient_Ethernet"
href="#ftn.footnote-Energy_Efficient_Ethernet"
class="footnote">3</a>]</sup> , 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 class="footnote"
id="footnote-Energy_Efficient_Ethernet"><div
class="para"><sup>[<a
id="ftn.footnote-Energy_Efficient_Ethernet"
href="#footnote-Energy_Efficient_Ethernet"
class="para">3</a>] </sup>
+ 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>Prev</strong>21.4. Unloading
a Module</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Persistent_Module_Loading.html"><strong>Next</strong>21.6. Persistent
Module Loading</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Setting_repository_Options.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Setting_repository_Options.html
new file mode 100644
index 0000000..30a54e3
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Setting_repository_Options.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.3.2. Setting [repository] Options</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Configuring_Yum_and_Yum_Repositories.html"
title="4.3. Configuring Yum and Yum Repositories" /><link
rel="prev" href="sec-Configuring_Yum_and_Yum_Repositories.html"
title="4.3. Configuring Yum and Yum Repositories" /><link
rel="next" href="sec-Using_Yum_Variables.html"
title="4.3.3. Using Yum Variables" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Configurin
g_Yum_and_Yum_Repositories.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_Yum_Variables.html"><strong>Next</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"
id="sec-Setting_repository_Options">4.3.2. Setting [repository]
Options</h3></div></div></div><a id="id477352"
class="indexterm"></a><div class="para">
+ The <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
sections (where <em
class="replaceable"><code>repository</code></em> is a
unique repository ID, such as <code
class="literal">my_personal_repo</code>) allow you to define individual
<span class="application"><strong>Yum</strong></span>
repositories. To define a new repository, either add this section to the <code
class="filename">/etc/yum.conf</code> file, or to a <code
class="filename">.repo</code> file in the <code
class="filename">/etc/yum.repos.d/</code> directory.
+ </div><div class="para">
+ All <code class="filename">.repo</code> files in <code
class="filename">/etc/yum.repos.d/</code>are read by <code
class="command">yum</code>, which allows you to create new, custom
<code class="filename">.repo</code> files in this directory. Best
practice is to define your repositories here instead of in <code
class="filename">/etc/yum.conf</code>.
+ </div><div class="para">
+ The following is a (bare-minimum) example of the form a <code
class="filename">.repo</code> file takes:
+ </div><pre class="screen">[repository_ID]
+name=A Repository Name
+baseurl=http://path/to/repo or ftp://path/to/repo or
file:///path/to/local/repo</pre><div class="para">
+ Every <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
section must contain the following minimum directives:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">[<em
class="replaceable"><code>repository_ID</code></em>]</span></dt><dd><div
class="para">
+ The repository ID is a unique, one-word (no spaces; underscores are allowed)
string of characters (enclosed by brackets) that serves as a repository identifier.
+ </div></dd><dt class="varlistentry"><span
class="term">name=<em class="replaceable"><code>A
Repository Name</code></em></span></dt><dd><div
class="para">
+ This is a human-readable string describing the repository.
+ </div></dd><dt class="varlistentry"><span
class="term">baseurl=<em
class="replaceable"><code>http://path/to/repo, ftp://path/to/repo,
file:///path/to/local/repo</code></em></span></dt><dd><div
class="para">
+ This is a URL to the directory where the repodata directory of a repository is
located. Usually this URL is an HTTP link, such as:
+ </div><pre
class="screen">baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</pre><div
class="para">
+ Note that <span
class="application"><strong>Yum</strong></span> always
expands the <code class="varname">$releasever</code>, <code
class="varname">$arch</code> and <code
class="varname">$basearch</code> variables in URLs. See <a
class="xref" href="sec-Using_Yum_Variables.html">Section 4.3.3,
“Using Yum Variables”</a> for explanations of all <span
class="application"><strong>Yum</strong></span> variables.
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ If the repository is available over FTP, use: <code
class="literal">ftp://path/to/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If the repository is local to the machine, use <code
class="literal">file:///path/to/local/repo</code>
+ </div></li><li class="listitem"><div
class="para">
+ If a specific online repository requires basic HTTP authentication, you can
specify your username and password in the <code
class="literal">http://path/to/repo</code> by prepending it as <code
class="command"><em
class="replaceable"><code>username</code></em>:<em
class="replaceable"><code>password</code></em>@<em
class="replaceable"><code>link</code></em></code>.
For example, if a repository on
http://www.example.com/repo/ requires a username of
<span class="quote">“<span
class="quote">user</span>”</span> and a password of <span
class="quote">“<span
class="quote">password</span>”</span>, then the <code
class="literal">baseurl</code> link could be specified as:
+ </div><pre class="screen">baseurl=http://<strong
class="userinput"><code>user</code></strong>:<strong
class="userinput"><code>password</code></strong>@www.example.com/repo/</pre></li></ul></div></dd></dl></div><div
class="para">
+ The following is another useful <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
directive:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term">enabled=<em
class="replaceable"><code>value</code></em></span></dt><dd><div
class="para">
+ ...where <em
class="replaceable"><code>value</code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — do not include this
repository as a package source when performing updates and installs. This is an easy way
of quickly turning repositories on and off, which is useful when you desire a single
package from a repository that you do not want to enable for updates or installs.
+ </div><div class="para">
+ <code class="constant">1</code> — include this repository as
a package source.
+ </div><div class="para">
+ Turning repositories on and off can also be performed by passing either the
<code class="option">--enablerepo=<em
class="replaceable"><code>repo_name</code></em></code>
or <code class="option">--disablerepo=<em
class="replaceable"><code>repo_name</code></em></code>
option to <code class="command">yum</code>, or through the <span
class="guilabel"><strong>Add/Remove
Software</strong></span> window of the <span
class="application"><strong>PackageKit</strong></span>
utility.
+ </div></dd></dl></div><div class="para">
+ Many more <code class="literal">[<em
class="replaceable"><code>repository</code></em>]</code>
options exist. Refer to the <code class="literal">[repository]
OPTIONS</code> section of <code class="command">man
yum.conf</code> for the exhaustive list and descriptions for each.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>Prev</strong>4.3. Configuring
Yum and Yum Repositories</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_Yum_Variables.html"><strong>Next</strong>4.3.3. Using
Yum Variables</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Specific_Kernel_Module_Capabilities.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Specific_Kernel_Module_Capabilities.html
new file mode 100644
index 0000000..024bc8b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Specific_Kernel_Module_Capabilities.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>21.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. Working with
Kernel Modules" /><link rel="prev"
href="sec-Persistent_Module_Loading.html" title="21.6. Persistent Module
Loading" /><link rel="next"
href="sec-Using_Channel_Bonding.html" title="21.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"><stro
ng>Prev</strong></a></li><li class="next"><a
accesskey="n"
href="sec-Using_Channel_Bonding.html"><strong>Next</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"
id="sec-Specific_Kernel_Module_Capabilities">21.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"
id="sec-Using_Multiple_Ethernet_Cards">21.7.1. Using Multiple Ethernet
Cards</h3></div></div></div><a id="id417811"
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&qu...;.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Persistent_Module_Loading.html"><strong>Prev</strong>21.6. Persistent
Module Loading</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Using_Channel_Bonding.html"><strong>Next</strong>21.7.2. Using
Channel Bonding</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Unloading_a_Module.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Unloading_a_Module.html
new file mode 100644
index 0000000..1d41aad
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Unloading_a_Module.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Working_with_Kernel_Modules.html" title="Chapter 21. Working with
Kernel Modules" /><link rel="prev"
href="sec-Loading_a_Module.html" title="21.3. Loading a Module"
/><link rel="next" href="sec-Setting_Module_Parameters.html"
title="21.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>Prev</strong></a><
/li><li class="next"><a accesskey="n"
href="sec-Setting_Module_Parameters.html"><strong>Next</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"
id="sec-Unloading_a_Module">21.4. Unloading a
Module</h2></div></div></div><a id="id465250"
class="indexterm"></a><a id="id465262"
class="indexterm"></a><a id="id623960"
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">Section 21.1,
“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>Example 21.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="id507009" class="indexterm"></a><a
id="id675833" 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>Prev</strong>21.3. Loading
a Module</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Setting_Module_Parameters.html"><strong>Next</strong>21.5. Setting
Module Parameters</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Add_Remove_Software.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Add_Remove_Software.html
new file mode 100644
index 0000000..b9b942f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Add_Remove_Software.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>5.2. Using Add/Remove Software</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-PackageKit.html" title="Chapter 5. PackageKit" /><link
rel="prev" href="ch-PackageKit.html"
title="Chapter 5. PackageKit" /><link rel="next"
href="sec-Finding_Packages_with_Filters.html" title="5.2.2. Finding
Packages with Filters" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n" hr
ef="sec-Finding_Packages_with_Filters.html"><strong>Next</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"
id="sec-Using_Add_Remove_Software">5.2. Using Add/Remove
Software</h2></div></div></div><a id="id614729"
class="indexterm"></a><a id="id614741"
class="indexterm"></a><div class="para">
+ <span
class="application"><strong>PackageKit</strong></span>'s
<span class="application"><strong>Software
Update</strong></span> GUI window is a separate application from its <span
class="guilabel"><strong>Add/Remove
Software</strong></span> application, although the two have intuitively
similar interfaces. To find and install a new package, select <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>Add/Remove
Software</strong></span> from the <span
class="guimenu"><strong>Activities</strong></span> menu, or
run the <code class="command">gpk-application</code> command at the
shell prompt.
+ </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's Add/Remove
Software window" /><div class="longdesc"><div
class="para">
+ Viewing PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>Figure 5.4. PackageKit's
Add/Remove Software window</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"
id="sec-Refreshing_Software_Sources_Yum_Repositories">5.2.1. Refreshing
Software Sources (Yum Repositories)</h3></div></div></div><div
class="para">
+ To enable or disable a <span
class="application"><strong>Yum</strong></span> repository,
open a dialog box by sclicking <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software
Sources</strong></span>, and select the <span
class="guilabel"><strong>Software Sources</strong></span>
tab. Refer to <a class="xref"
href="ch-PackageKit.html#sec-Setting_preferences_for_software_sources">Section 5.1.2,
“Setting the Software Sources”</a> for more information on available configuration
options.
+ </div><div class="para">
+ After enabling and/or disabling the correct <span
class="application"><strong>Yum</strong></span>
repositories, make sure that you have the latest list of available packages. Click on
<span class="guimenu"><strong>System</strong></span> →
<span class="guimenuitem"><strong>Refresh Package
Lists</strong></span> and <span
class="application"><strong>PackageKit</strong></span> will
obtain the latest lists of packages from all enabled software sources, that is, <span
class="application"><strong>Yum</strong></span>
repositories.
+ </div></div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-PackageKit.html"><strong>Prev</strong>Chapter 5. PackageKit</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Finding_Packages_with_Filters.html"><strong>Next</strong>5.2.2. Finding
Packages with Filters</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Channel_Bonding.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Channel_Bonding.html
new file mode 100644
index 0000000..abb4619
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Channel_Bonding.html
@@ -0,0 +1,192 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>21.7.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Specific_Kernel_Module_Capabilities.html" title="21.7. Specific
Kernel Module Capabilities" /><link rel="prev"
href="sec-Specific_Kernel_Module_Capabilities.html" title="21.7. Specific
Kernel Module Capabilities" /><link rel="next"
href="s1-kernel-modules-additional-resources.html" title="21.8. Additional
Resources" /></head><body class="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left"
href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="s
ec-Specific_Kernel_Module_Capabilities.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-modules-additional-resources.html"><strong>Next</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"
id="sec-Using_Channel_Bonding">21.7.2. Using Channel
Bonding</h3></div></div></div><a id="id479732"
class="indexterm"></a><a id="id593016"
class="indexterm"></a><a id="id593028"
class="indexterm"></a><a id="id643375"
class="indexterm"></a><a id="id640754"
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="id557893"
class="indexterm"></a><a id="id557905"
class="indexterm"></a><div class="para">
+ To channel bond multiple network interfaces, the administrator must perform the
following steps:
+ </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">Section 6.2.2, “Channel Bonding
Interfaces”</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">Section 21.7.2.1,
“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"
id="s3-modules-bonding-directives">21.7.2.1. Bonding Module
Directives</h4></div></div></div><a id="id638765"
class="indexterm"></a><a id="id567198"
class="indexterm"></a><a id="id567213"
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">Section 6.2.2, “Channel Bonding
Interfaces”</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">[output truncated]</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">Section 6.2.2, “Channel Bonding
Interfaces”</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">Section 21.8, “Additional
Resources”</a>).
+ </div><div class="variablelist"><h6>Bonding Interface
Parameters</h6><dl><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>Note</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>Prev</strong>21.7. Specific
Kernel Module Capabilities</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-modules-additional-resources.html"><strong>Next</strong>21.8. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Yum_Variables.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Yum_Variables.html
new file mode 100644
index 0000000..5e5329d
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Using_Yum_Variables.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>4.3.3. Using Yum Variables</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Configuring_Yum_and_Yum_Repositories.html"
title="4.3. Configuring Yum and Yum Repositories" /><link
rel="prev" href="sec-Setting_repository_Options.html"
title="4.3.2. Setting [repository] Options" /><link rel="next"
href="sec-Creating_a_Yum_Repository.html" title="4.3.4. Creating a Yum
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-Setting_reposi
tory_Options.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Creating_a_Yum_Repository.html"><strong>Next</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"
id="sec-Using_Yum_Variables">4.3.3. Using Yum
Variables</h3></div></div></div><a id="id477756"
class="indexterm"></a><div class="para">
+ You can use and reference the following built-in variables in <code
class="command">yum</code> commands and in all <span
class="application"><strong>Yum</strong></span>
configuration files (that is, <code
class="filename">/etc/yum.conf</code> and all <code
class="filename">.repo</code> files in the <code
class="filename">/etc/yum.repos.d/</code> directory):
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"> <code
class="varname">$releasever</code>
</span></dt><dd><div class="para">
+ You can use this variable to reference the release version of Fedora. <span
class="application"><strong>Yum</strong></span> obtains the
value of <code class="varname">$releasever</code> from the <code
class="literal">distroverpkg=<em
class="replaceable"><code>value</code></em></code>
line in the <code class="filename">/etc/yum.conf</code>
configuration file. If there is no such line in <code
class="filename">/etc/yum.conf</code>, then <code
class="command">yum</code> infers the correct value by deriving the
version number from the <span class="package">redhat-release</span>
package.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="varname">$arch</code>
</span></dt><dd><div class="para">
+ You can use this variable to refer to the system's CPU architecture as
returned when calling Python's <code
class="methodname">os.uname()</code> function. Valid values for
<code class="varname">$arch</code> include: <code
class="literal">i586</code>, <code
class="literal">i686</code>, and <code
class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="varname">$basearch</code>
</span></dt><dd><div class="para">
+ You can use <code class="varname">$basearch</code> to
reference the base architecture of the system. For example, i686 and i586 machines both
have a base architecture of <code class="literal">i386</code>, and
AMD64 and Intel 64 machines have a base architecture of <code
class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="varname">$uuid</code>
</span></dt><dd><div class="para">
+ You can use this variable to refer to a <em
class="firstterm">universally unique identifier</em> (UUID) for the
machine.
+ </div></dd><dt class="varlistentry"><span
class="term"> <code class="varname">$YUM0-9</code>
</span></dt><dd><div class="para">
+ These ten variables are each replaced with the value of any shell environment
variables with the same name. If one of these variables is referenced (in <code
class="filename">/etc/yum.conf</code> for example) and a shell
environment variable with the same name does not exist, then the configuration file
variable is not replaced.
+ </div></dd></dl></div><div class="para">
+ To define a custom variable or to override the value of an existing one, create a
file with the same name as the variable (without the <span
class="quote">“<span class="quote"><code
class="literal">$</code></span>”</span> sign) in the
<code class="filename">/etc/yum/vars/</code> directory, and add the
desired value on its first line.
+ </div><div class="example"
id="exam-Using_Yum_Variables"><h6>Example 4.7. Using a custom <span
class="application">Yum</span> variable</h6><div
class="example-contents"><div class="para">
+ Repository descriptions often include the operating system name. To define a new
variable called <code class="varname">$osname</code>, create a new
file with <span class="quote">“<span
class="quote">Fedora</span>”</span> on the first line and save it
as <code class="filename">/etc/yum/vars/osname</code>. For example:
+ </div><pre class="screen">~]# <code
class="command">echo "Fedora" >
/etc/yum/vars/osname</code></pre><div class="para">
+ Instead of <span class="quote">“<span
class="quote">Fedora 15</span>”</span>, you can now use the
following in the <code class="filename">.repo</code> files:
+ </div><pre class="screen">name=$osname
$releasever</pre></div></div><br class="example-break"
/></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Setting_repository_Options.html"><strong>Prev</strong>4.3.2. Setting
[repository] Options</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Creating_a_Yum_Repository.html"><strong>Next</strong>4.3.4. Creating
a Yum Repository</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
new file mode 100644
index 0000000..7e65845
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.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>20.5. Verifying the Initial RAM Disk Image</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 20. Manually
Upgrading the Kernel" /><link rel="prev"
href="s1-kernel-perform-upgrade.html" title="20.4. Performing the
Upgrade" /><link rel="next"
href="s1-kernel-boot-loader.html" title="20.6. Verifying the 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-perform-upgrade.html"><strong>Prev</
strong></a></li><li class="next"><a
accesskey="n"
href="s1-kernel-boot-loader.html"><strong>Next</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"
id="sec-Verifying_the_Initial_RAM_Disk_Image">20.5. Verifying the Initial RAM
Disk Image</h2></div></div></div><a id="id609210"
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 15 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">Section 20.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">
+ 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">grub.conf</code> configuration file by
following this procedure:
+ </div><div class="procedure"
id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>Procedure 20.1. Verifying
the Initial RAM Disk Image</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-2.6.38.6-26.fc15.x86_64
+config-2.6.38.6-27.fc15.x86_64
+efi
+elf-memtest86+-4.10
+grub
+initramfs-2.6.38.6-26.fc15.x86_64.img
+initramfs-2.6.38.6-27.fc15.x86_64.img
+lost+found
+memtest86+-4.10
+System.map-2.6.38.6-26.fc15.x86_64
+System.map-2.6.38.6-27.fc15.x86_64
+vmlinuz-2.6.38.6-26.fc15.x86_64
+vmlinuz-2.6.38.6-27.fc15.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-2.6.38.6-27.fc15.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-2.6.38.6-27.fc15.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>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">Chapter 22, <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-2.6.38.6-26.fc15.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>:
+ </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-2.6.38.6-26.fc15.x86_64.img</code>
+/boot/initramfs-2.6.38.6-26.fc15.x86_64.img:
+========================================================================
+dracut-009-10.fc15
+========================================================================
+drwxr-xr-x 23 root root 0 May 20 14:45 .
+drwxr-xr-x 2 root root 0 May 20 14:45 bin
+-rwxr-xr-x 1 root root 38400 Feb 8 12:46 bin/rmdir
+-rwxr-xr-x 1 root root 116632 Feb 8 12:46 bin/ls
+-rwxr-xr-x 1 root root 39568 Feb 8 03:27 bin/setfont
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</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">grub.conf</code>
configuration file in the <code class="filename">/boot/grub/</code>
directory to ensure that an <code class="computeroutput">initrd <code
class="filename">initramfs-<em
class="replaceable"><code>kernel_version</code></em>.img</code></code>
exists for the kernel version you are booting. Refer to <a class="xref"
href="s1-kernel-boot-loader.html">Section 20.6, “Verifying the Boot
Loader”</a> for more information.
+ </div></li></ol></div><h3>Verifying the Initial RAM
Disk Image and Kernel on IBM eServer System i</h3><a id="id641877"
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, use the command <code
class="command">ls -l /boot/</code> to make sure the <code
class="filename">/boot/vmlinitrd-<em
class="replaceable"><code>kernel_version</code></em></code>
file already exists (the <code class="filename"><em
class="replaceable"><code>kernel_version</code></em></code>
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>Prev</strong>20.4. Performing
the Upgrade</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-kernel-boot-loader.html"><strong>Next</strong>20.6. Verifying
the Boot Loader</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.html
new file mode 100644
index 0000000..459156b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>5.2.5. Viewing the Transaction Log</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sec-Using_Add_Remove_Software.html" title="5.2. Using Add/Remove
Software" /><link rel="prev"
href="sec-Installing_and_Removing_Package_Groups.html"
title="5.2.4. Installing and Removing Package Groups" /><link
rel="next" href="sec-PackageKit_Architecture.html"
title="5.3. PackageKit 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-Installing_and_Remov
ing_Package_Groups.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sec-PackageKit_Architecture.html"><strong>Next</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"
id="sec-Viewing_the_Transaction_Log">5.2.5. Viewing the Transaction
Log</h3></div></div></div><div class="para">
+ <span
class="application"><strong>PackageKit</strong></span>
maintains a log of the transactions
+ <a id="id545124" class="indexterm"></a>
+ <a id="id545136" class="indexterm"></a>
+ that it performs. To view the log, from the <span
class="guilabel"><strong>Add/Remove
Software</strong></span> window, click <span
class="guimenu"><strong>System</strong></span> → <span
class="guimenuitem"><strong>Software Log</strong></span>,
or run the <code class="command">gpk-log</code> command at the shell
prompt.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Software Log
Viewer</strong></span> shows the <span
class="guilabel"><strong>Action</strong></span>, such as
<code class="literal">Updated Packages</code> or <code
class="literal">Installed Packages</code>, the <span
class="guilabel"><strong>Date</strong></span> on which that
action was performed, the <span
class="guilabel"><strong>Username</strong></span> of the
user who performed the action, and the front end <span
class="guilabel"><strong>Application</strong></span> the
user used (such as <code class="literal">Add/Remove Software</code>,
or <code class="literal">Update System</code>). The <span
class="guilabel"><strong>Details</strong></span> column
provides the types of the transactions, such as <code
class="literal">Updated</code>, <code
class="literal">Installed</code>, or <code
class="literal">Removed</code>, as well as the list of packages the
transactions were performed on.
+ </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="Viewing the log of package
management transactions with the Software Log Viewer" /><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>Figure 5.10. Viewing the
log of package management transactions with the Software Log
Viewer</h6></div><br class="figure-break" /><div
class="para">
+ Typing the name of a package in the top text entry field filters the list of
transactions to those which affected that package.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="sec-Installing_and_Removing_Package_Groups.html"><strong>Prev</strong>5.2.4. Installing
and Removing Package Groups</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-PackageKit_Architecture.html"><strong>Next</strong>5.3. PackageKit
Architecture</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Yum_Plugins.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Yum_Plugins.html
new file mode 100644
index 0000000..2698530
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sec-Yum_Plugins.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.4. Yum Plugins</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-yum.html" title="Chapter 4. Yum" /><link
rel="prev" href="sec-Creating_a_Yum_Repository.html"
title="4.3.4. Creating a Yum Repository" /><link rel="next"
href="sec-Installing_More_Yum_Plugins.html" title="4.4.2. Installing
Additional Yum Plugins" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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"><strong>Prev</strong></a></li><li
cl
ass="next"><a accesskey="n"
href="sec-Installing_More_Yum_Plugins.html"><strong>Next</strong></a></li></ul><div
class="section" id="sec-Yum_Plugins"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sec-Yum_Plugins">4.4. Yum
Plugins</h2></div></div></div><a id="id419809"
class="indexterm"></a><div class="para">
+ <span
class="application"><strong>Yum</strong></span> provides
plugins that extend and enhance its operations. Certain plugins are installed by default.
<span class="application"><strong>Yum</strong></span>
always informs you which plugins, if any, are loaded and active whenever you call any
<code class="command">yum</code> command:
+ </div><pre class="screen">~]# <code
class="command">yum info yum</code>
+Loaded plugins: langpacks, presto, refresh-packagekit
+<em class="lineannotation"><span
class="lineannotation">[output
truncated]</span></em></pre><div class="para">
+ Note that the plugin names which follow <code class="command">Loaded
plugins</code> are the names you can provide to the <code
class="option">--disableplugins=<em
class="replaceable"><code>plugin_name</code></em></code>
option.
+ </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"
id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins">4.4.1. Enabling,
Configuring and Disabling Yum Plugins</h3></div></div></div><a
id="id419870" class="indexterm"></a><a
id="id419882" class="indexterm"></a><a
id="id419894" class="indexterm"></a><div
class="para">
+ To enable <span
class="application"><strong>Yum</strong></span> plugins,
ensure that a line beginning with <code
class="command">plugins=</code> is present in the <code
class="literal">[main]</code> section of <code
class="filename">/etc/yum.conf</code>, and that its value is set to
<code class="constant">1</code>:
+ </div><pre class="screen">plugins=1</pre><div
class="para">
+ You can disable all plugins by changing this line to <code
class="command">plugins=0</code>.
+ </div><div class="important"
id="important-Disabling_all_plugins_is_not_advised-plugins"><div
class="admonition_header"><h2>Disabling all plugins is not
advised</h2></div><div class="admonition"><div
class="para">
+ Disabling all plugins is not advised because certain plugins provide important
<code class="command">Yum</code> services. Disabling plugins
globally is provided as a convenience option, and is generally only recommended when
diagnosing a potential problem with <code
class="command">Yum</code>.
+ </div></div></div><div class="para">
+ Every installed plugin has its own configuration file in the <code
class="filename">/etc/yum/pluginconf.d/</code> directory. You can set
plugin-specific options in these files. For example, the following is the content of
<code class="filename">refresh-packagekit.conf</code>, the
configuration file for the <span
class="application"><strong>refresh-packagekit</strong></span>
plugin:
+ </div><pre class="screen">[main]
+enabled=1</pre><div class="para">
+ Plugin configuration files always contain a <code
class="literal">[main]</code> section (similar to <span
class="application"><strong>Yum</strong></span>'s
<code class="filename">/etc/yum.conf</code> file) in which there is
(or you can place if it is missing) an <code
class="literal">enabled=</code> option that controls whether the plugin
is enabled when you run <code class="command">yum</code> commands.
+ </div><div class="para">
+ If you disable all plugins by setting <code
class="command">enabled=0</code> in <code
class="filename">/etc/yum.conf</code>, then all plugins are disabled
regardless of whether they are enabled in their individual configuration files.
+ </div><div class="para">
+ If you merely want to disable all <span
class="application"><strong>Yum</strong></span> plugins for
a single <code class="command">yum</code> command, use the <code
class="option">--noplugins</code> option.
+ </div><div class="para">
+ If you want to disable one or more <span
class="application"><strong>Yum</strong></span> plugins for
a single <code class="command">yum</code> command, add the <code
class="option">--disableplugin=<em
class="replaceable"><code>plugin_name</code></em></code>
option to the command. For example, to disable the <span
class="application"><strong>presto</strong></span> plugin
while updating a system, type:
+ </div><pre class="screen">~]# <code
class="command">yum update
--disableplugin=presto</code></pre><div class="para">
+ The plugin names you provide to the <code
class="option">--disableplugin=</code> option are the same names listed
after the <code class="command">Loaded plugins</code> line in the
output of any <code class="command">yum</code> command. You can
disable multiple plugins by separating their names with commas. In addition, you can match
multiple plugin names or shorten long ones by using glob expressions:
+ </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>Prev</strong>4.3.4. Creating
a Yum Repository</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sec-Installing_More_Yum_Plugins.html"><strong>Next</strong>4.4.2. Installing
Additional Yum Plugins</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html
new file mode 100644
index 0000000..9d8bc65
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.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>10.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-DHCP_Servers.html" title="Chapter 10. DHCP Servers"
/><link rel="prev" href="s1-dhcp-configuring-client.html"
title="10.3. Configuring a DHCP Client" /><link rel="next"
href="s1-dhcp_for_ipv6_dhcpv6.html" title="10.5. DHCP for IPv6
(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>Prev</strong></a></li><li
class="nex
t"><a accesskey="n"
href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>Next</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"
id="sect-Configuring_a_Multihomed_DHCP_Server">10.4. Configuring a Multihomed
DHCP Server</h2></div></div></div><a id="id479974"
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><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">
+ The <code class="computeroutput">option subnet-mask</code>
option defines a subnet mask, and overrides the <code
class="computeroutput">netmask</code> value in the <code
class="computeroutput">subnet</code> declaration. In simple cases, the
subnet and netmask values are the same.
+ </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">
+ The <code class="computeroutput">range</code> option
specifies the pool of available IP addresses. Systems are assigned an address from the
range of specified IP addresses.
+ </div></dd></dl></div><div class="para">
+ For further information, refer to the <code
class="computeroutput">dhcpd.conf(5)</code> man page.
+ </div><div class="warning"><div
class="admonition_header"><h2>Do not use alias
interfaces</h2></div><div class="admonition"><div
class="para">
+ Alias interfaces are not supported by DHCP. If an alias interface is the only
interface, in the only subnet specified in <code
class="filename">/etc/dhcp/dhcpd.conf</code>, the DHCP daemon fails to
start.
+ </div></div></div><div class="section"
id="sect-dns_Host_Configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sect-dns_Host_Configuration">10.4.1. Host
Configuration</h3></div></div></div><a id="id442810"
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="id442836">Configuring a single system for
multiple networks</h5>
+ The following <code
class="filename">/etc/dhcp/dhcpd.conf</code> example creates two
subnets, and configures an IP address for the same system, depending on which network it
connects to:
+ </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><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="id438336">Configuring systems with multiple network
interfaces</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>Prev</strong>10.3. Configuring
a DHCP Client</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>Next</strong>10.5. DHCP
for IPv6 (DHCPv6)</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Additional_Resources.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Additional_Resources.html
new file mode 100644
index 0000000..c9dacbe
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Additional_Resources.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>2.3. Additional Resources</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Date_and_Time_Configuration.html" title="Chapter 2. Date and Time
Configuration" /><link rel="prev"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"
title="2.2.2. Configuring the Network Time Protocol" /><link
rel="next" href="ch-Managing_Users_and_Groups.html"
title="Chapter 3. Managing Users and Groups" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class=
"previous"><a accesskey="p"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Managing_Users_and_Groups.html"><strong>Next</strong></a></li></ul><div
class="section"
id="sect-Date_and_Time_Configuration-Additional_Resources"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Date_and_Time_Configuration-Additional_Resources">2.3. Additional
Resources</h2></div></div></div><div
class="para">
+ For more information about the date and time configuration, refer to the following
resources.
+ </div><div class="section"
id="sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sect-Date_and_Time_Configuration-Additional_Resources-Installed_Documentation">2.3.1. Additional
Resources</h3></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div
class="para">
+ <code class="literal">date</code>(1) — The manual page for
the <span
class="application"><strong>date</strong></span> utility.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">ntpdate</code>(8) — The manual page for
the <span
class="application"><strong>ntpdate</strong></span>
utility.
+ </div></li><li class="listitem"><div
class="para">
+ <code class="literal">ntpd</code>(8) — The manual page for
the <code class="systemitem">ntpd</code> service.
+ </div></li></ul></div></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"><strong>Prev</strong>2.2.2. Configuring
the Network Time Protocol</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Managing_Users_and_Groups.html"><strong>Next</strong>Chapter 3. Managing
Users and Groups</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html
new file mode 100644
index 0000000..cb52d3b
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. Configuring the 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"
title="2.2. Command Line Configuration" /><link rel="prev"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"
title="2.2. Command Line Configuration" /><link rel="next"
href="sect-Date_and_Time_Configuration-Additional_Resources.html"
title="2.3. Additional Resources" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="
previous"><a accesskey="p"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Date_and_Time_Configuration-Additional_Resources.html"><strong>Next</strong></a></li></ul><div
class="section"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">2.2.2. Configuring
the Network Time Protocol</h3></div></div></div><a
id="id484098" class="indexterm"></a><a
id="id484110" class="indexterm"></a><a
id="id484118" class="indexterm"></a><a
id="id484131" class="indexterm"></a><div
class="para">
+ As opposed to the manual setup described above, you can also synchronize the system
clock with a remote server over the Network Time Protocol (<acronym
class="acronym">NTP</acronym>). For the one-time synchronization only,
use the <span
class="application"><strong>ntpdate</strong></span>
command:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Check whether the selected NTP server is accessible by using the <code
class="command">ntpdate</code> command in the following form:
+ </div><pre class="screen"><code
class="command">ntpdate -q <em
class="replaceable"><code>server_address</code></em></code></pre><div
class="para">
+ For example, to connect to <code
class="systemitem">0.fedora.pool.ntp.org</code>, type:
+ </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
+23 May 01:05:54 ntpdate[10619]: step time server 204.15.208.61 offset -39.275438
sec</pre></li><li class="step"><div
class="para">
+ When you find a satisfactory server, run the <span
class="application"><strong>ntpdate</strong></span> command
followed with one or more server addresses:
+ </div><pre class="screen"><code
class="command">ntpdate <em
class="replaceable"><code>server_address...</code></em></code></pre><div
class="para">
+ For instance:
+ </div><pre class="screen">~]# <code
class="command">ntpdate
0.fedora.pool.ntp.org
1.fedora.pool.ntp.org</code>
+23 May 01:07:13 ntpdate[10669]: step time server 204.15.208.61 offset -39.275436
sec</pre><div class="para">
+ Unless an error message is displayed, the system time should now be set. You can
check the current by setting typing <code
class="command">date</code> without any additional arguments as shown
in <a class="xref"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">Section 2.2.1,
“Configuring the Date and Time”</a>.
+ </div></li><li class="step"><div
class="para">
+ In most cases, these steps are sufficient. Only if you really need one or more
system services to always use the correct time, enable running the <span
class="application"><strong>ntpdate</strong></span> at boot
time:
+ </div><pre class="screen"><code
class="command">systemctl enable
ntpdate.service</code></pre><div class="para">
+ For more information about system services and their setup, refer to <a
class="xref" href="ch-Services_and_Daemons.html">Chapter 7,
<em>Services and Daemons</em></a>.
+ </div><div class="note"><div
class="admonition_header"><h2>Note</h2></div><div
class="admonition"><div class="para">
+ If the synchronization with the time server at boot time keeps failing, that is,
you find a relevant error message in the <code
class="filename">/var/log/boot.log</code> system log, try to add the
following line to <code
class="filename">/etc/sysconfig/network</code>:
+ </div><pre
class="screen">NETWORKWAIT=1</pre></div></div></li></ol></div><a
id="id504222" class="indexterm"></a><a
id="id504234" class="indexterm"></a><a
id="id504242" class="indexterm"></a><a
id="id504256" class="indexterm"></a><div
class="para">
+ However, the more convenient way is to set the <code
class="systemitem">ntpd</code> daemon to synchronize the time at boot
time automatically:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ Open the NTP configuration file <code
class="filename">/etc/ntp.conf</code> in a text editor, creating a new
one if it does not already exist.
+ </div></li><li class="step"><div
class="para">
+ Add or edit the list of public NTP servers. If you are using Fedora 15, the file
should already contain the following lines, but feel free to change or expand these
according to your needs:
+ </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>Speeding up initial
synchronization</h2></div><div class="admonition"><div
class="para">
+ To speed the initial synchronization up, it is recommended that the <code
class="command">iburst</code> directive is added at the end of each
server line.
+ </div></div></div></li><li
class="step"><div class="para">
+ In the same file, set the proper permissions, giving the unrestricted access to
localhost only:
+ </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">
+ Save the changes, exit the editor, and restart the NTP daemon:
+ </div><pre class="screen"><code
class="command">systemctl restart
ntpd.service</code></pre></li><li class="step"><div
class="para">
+ Additionally, make sure that <code
class="command">ntpd</code> daemon is started at boot time:
+ </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-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Prev</strong>2.2. Command
Line Configuration</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Date_and_Time_Configuration-Additional_Resources.html"><strong>Next</strong>2.3. Additional
Resources</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.html
new file mode 100644
index 0000000..197c128
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.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>2.2. Command Line 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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Date_and_Time_Configuration.html" title="Chapter 2. Date and Time
Configuration" /><link rel="prev"
href="ch-Date_and_Time_Configuration.html" title="Chapter 2. Date and Time
Configuration" /><link rel="next"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"
title="2.2.2. Configuring the 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/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li cl
ass="previous"><a accesskey="p"
href="ch-Date_and_Time_Configuration.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"><strong>Next</strong></a></li></ul><div
class="section"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration">2.2. Command
Line Configuration</h2></div></div></div><div
class="para">
+ In case your system does not have the <span
class="application"><strong>Date/Time
Properties</strong></span> tool installed, or the <span
class="emphasis"><em>X Window Server</em></span> is not
running, you can change the system date and time on the command line. Note that in order
to perform actions described in this section, you have to be logged in as <code
class="systemitem">root</code>. To do so, type the following at a shell
prompt:
+ </div><pre class="screen"><code
class="command">su -</code></pre><div
class="section"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">2.2.1. Configuring
the Date and Time</h3></div></div></div><a
id="id480550" class="indexterm"></a><a
id="id480558" class="indexterm"></a><div
class="para">
+ The <code class="command">date</code> command allows the
superuser to set the system date and time manually:
+ </div><div class="procedure"><ol
class="1"><li class="step"><div
class="para">
+ To change the current date, type the command in the following form at a shell
prompt, replacing the <em
class="replaceable"><code>YYYY</code></em> with a
four-digit year, <em
class="replaceable"><code>MM</code></em> with a two-digit
month, and <em class="replaceable"><code>DD</code></em>
with a two-digit day of the month:
+ </div><pre class="screen"><code
class="command">date +%D -s <em
class="replaceable"><code>YYYY-MM-DD</code></em></code></pre><div
class="para">
+ For example, to set the date to 2 June 2010, type:
+ </div><pre class="screen">~]# <code
class="command">date +%D -s
2010-06-02</code></pre></li><li class="step"><div
class="para">
+ To change the current date, use the following command, where <em
class="replaceable"><code>HH</code></em> stands for an
hour, <em class="replaceable"><code>MM</code></em> is a
minute, and <em class="replaceable"><code>SS</code></em>
is a second, all typed in a two-digit form:
+ </div><pre class="screen"><code
class="command">date +%T -s <em
class="replaceable"><code>HH:MM:SS</code></em></code></pre><div
class="para">
+ If your system clock is set to use <acronym
class="acronym">UTC</acronym> (Coordinated Universal Time), add the
following option:
+ </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">
+ For instance, to set the system clock to 11:26 PM using the <acronym
class="acronym">UTC</acronym>, type:
+ </div><pre class="screen">~]# <code
class="command">date +%T -s 23:26:00
-u</code></pre></li></ol></div><div
class="para">
+ You can check your current settings by typing <code
class="command">date</code> without any additional argument, for
example:
+ </div><pre class="screen">~]$ <code
class="command">date</code>
+Wed Jun 2 11:58:48 CEST 2010</pre></div></div><ul
class="docnav"><li class="previous"><a
accesskey="p"
href="ch-Date_and_Time_Configuration.html"><strong>Prev</strong>Chapter 2. Date
and Time Configuration</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"><strong>Next</strong>2.2.2. Configuring
the Network Time Protocol</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Language_and_Keyboard_Configuration-Layouts.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Language_and_Keyboard_Configuration-Layouts.html
new file mode 100644
index 0000000..8231b5e
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Language_and_Keyboard_Configuration-Layouts.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>1.2. Changing the Keyboard Layout</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="ch-Language_and_Keyboard_Configuration.html"
title="Chapter 1. Language and Keyboard Configuration" /><link
rel="prev" href="ch-Language_and_Keyboard_Configuration.html"
title="Chapter 1. Language and Keyboard Configuration" /><link
rel="next" href="ch-Date_and_Time_Configuration.html"
title="Chapter 2. Date and Time 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 access
key="p"
href="ch-Language_and_Keyboard_Configuration.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Date_and_Time_Configuration.html"><strong>Next</strong></a></li></ul><div
class="section"
id="sect-Language_and_Keyboard_Configuration-Layouts"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Language_and_Keyboard_Configuration-Layouts">1.2. Changing the
Keyboard Layout</h2></div></div></div><a
id="id443908" class="indexterm"></a><a
id="id432463" class="indexterm"></a><div
class="para">
+ Although the installation program allows a system administrator to configure a
keyboard layout during the system installation, the default settings may not always suit
your current needs. To add a new keyboard layout, open the <span
class="application"><strong>System Settings</strong></span>
window by selecting <span
class="guimenu"><strong>Applications</strong></span> →
<span class="guisubmenu"><strong>System
Tools</strong></span> → <span
class="guimenuitem"><strong>System Settings</strong></span>
from the <span
class="guimenu"><strong>Activities</strong></span> menu,
click the <span class="guimenuitem"><strong>Region and
Language</strong></span> icon, and select the <span
class="guilabel"><strong>Layouts</strong></span> tab.
+ </div><div class="figure"
id="fig-Language_and_Keyboard_Configuration-Layouts"><div
class="figure-contents"><div class="mediaobject"><img
src="images/region-and-language-layouts.png" alt="Changing the keyboard
layout" /><div class="longdesc"><div
class="para">
+ Changing the keyboard layout
+ </div></div></div></div><h6>Figure 1.2. Changing the
keyboard layout</h6></div><br class="figure-break" /><div
class="para">
+ The left part of the window provides a list of currently enabled layouts, while the
right part allows you to choose whether to use the same keyboard layout for all windows,
or if you prefer to use a different layout for each window.
+ </div><div class="para">
+ To add a keyboard layout, click the <span
class="guibutton"><strong>+</strong></span> (that is, the
plus sign) button below the list. A dialog box will appear, allowing you to select the
desired layout. The input field in the bottom part of the dialog box allows you to reduce
the number of displayed items by typing part of the layout name (such as <span
class="quote">“<span
class="quote">slov</span>”</span> for Slovak layouts) in it. Once
you are done, click the <span
class="guibutton"><strong>Add</strong></span> button to
confirm your choice.
+ </div><div class="figure"
id="fig-Language_and_Keyboard_Configuration-Layouts-Add"><div
class="figure-contents"><div class="mediaobject"><img
src="images/region-and-language-layouts-add.png" alt="Adding a keyboard
layout" /><div class="longdesc"><div
class="para">
+ Adding a keyboard layout
+ </div></div></div></div><h6>Figure 1.3. Adding a
keyboard layout</h6></div><br class="figure-break" /><div
class="para">
+ To remove a keyboard layout, click the <span
class="guibutton"><strong>−</strong></span> (that is, the
minus sign) button below the list.
+ </div><div class="para">
+ When more than one layout is enabled, a keyboard indicator appears on the panel in
order to allow you to switch between the layouts, and the first layout in the list is
considered the default. To move a particular layout up or down in the list, select it from
the list and click the <span
class="guibutton"><strong>↑</strong></span> (the upwards
arrow) or <span
class="guibutton"><strong>↓</strong></span> (the downwards
arrow) buttons respectively.
+ </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="The keyboard
layout indicator" /><div class="longdesc"><div
class="para">
+ The keyboard layout indicator
+ </div></div></div></div><h6>Figure 1.4. The keyboard
layout indicator</h6></div><br class="figure-break" /><div
class="para">
+ The changes take effect immediately.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="ch-Language_and_Keyboard_Configuration.html"><strong>Prev</strong>Chapter 1. Language
and Keyboard Configuration</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-Date_and_Time_Configuration.html"><strong>Next</strong>Chapter 2. Date
and Time Configuration</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Preface-Book_Organization.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Preface-Book_Organization.html
new file mode 100644
index 0000000..ab44ebb
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Preface-Book_Organization.html
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/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. How to Read this Book</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="pr01.html" title="Preface" /><link rel="prev"
href="pr01.html" title="Preface" /><link rel="next"
href="pr01s03.html" title="3. Document Conventions"
/></head><body class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03.html"><strong>Next</strong></a></li></ul><div
class="section" id="sect-Preface-Book_Or
ganization"><div class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Preface-Book_Organization">2. How to Read this
Book</h2></div></div></div><div class="para">
+ This manual is divided into the following main categories:
+ </div><div class="variablelist"><dl><dt
class="varlistentry"><span class="term"><a
class="xref" href="part-Basic_System_Configuration.html">Part I,
“Basic System Configuration”</a></span></dt><dd><div
class="para">
+ This part covers basic system administration tasks such as keyboard configuration,
date and time configuration, and managing users and groups.
+ </div><div class="para">
+ <a class="xref"
href="ch-Language_and_Keyboard_Configuration.html">Chapter 1,
<em>Language and Keyboard Configuration</em></a> covers basic language
and keyboard setup. Read this chapter if you need to configure the language of your
desktop, change the keyboard layout, or add the keyboard layout indicator to the panel.
+ </div><div class="para">
+ <a class="xref"
href="ch-Date_and_Time_Configuration.html">Chapter 2, <em>Date and Time
Configuration</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">Chapter 3, <em>Managing Users
and Groups</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">Part II, “Package
Management”</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">Chapter 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">Chapter 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">Part III,
“Networking”</a></span></dt><dd><div
class="para">
+ This part describes how to configure the network on Fedora.
+ </div><div class="para">
+ <a class="xref"
href="ch-Network_Interfaces.html">Chapter 6, <em>Network
Interfaces</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">Part IV, “Infrastructure
Services”</a></span></dt><dd><div class="para">
+ This part provides information how to configure services and daemons, configure
authentication, and enable remote logins.
+ </div><div class="para">
+ <a class="xref"
href="ch-Services_and_Daemons.html">Chapter 7, <em>Services and
Daemons</em></a> explains the concept of runlevels, and describes how to set
the default one. It also covers the configuration of the services to be run in each of
these runlevels, and provides information on how to start, stop, and restart a service.
Read this chapter to learn how to manage services on your system.
+ </div><div class="para">
+ <a class="xref"
href="ch-Configuring_Authentication.html">Chapter 8, <em>Configuring
Authentication</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">Chapter 9,
<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">Part V,
“Servers”</a></span></dt><dd><div class="para">
+ This part discusses various topics related to servers such as how to set up a Web
server or share files and directories over the network.
+ </div><div class="para">
+ <a class="xref" href="ch-DHCP_Servers.html">Chapter 10,
<em>DHCP Servers</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">Chapter 11,
<em>DNS Servers</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">Chapter 12,
<em>Web Servers</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">Chapter 13,
<em>Mail Servers</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">Chapter 14, <em>Directory
Servers</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">Chapter 15, <em>File
Servers</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. Read this chapter if you need to configure a file
server on your system.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="part-Monitoring_and_Automation.html">Part VI, “Monitoring and
Automation”</a></span></dt><dd><div class="para">
+ This part describes various tools that allow system administrators to monitor
system performance, automate system tasks, and report bugs.
+ </div><div class="para">
+ <a class="xref"
href="ch-System_Monitoring_Tools.html">Chapter 16, <em>System
Monitoring Tools</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">Chapter 17, <em>Viewing
and Managing Log Files</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">Chapter 18, <em>Automating
System Tasks</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-abrt.html">Chapter 19,
<em>Automatic Bug-Reporting Tool (ABRT)</em></a> concentrates on
<span class="application"><strong>ABRT</strong></span>,
a system service and a set of tools to collect crash data and send a report to the
relevant issue tracker. Read this chapter to learn how to use <span
class="application"><strong>ABRT</strong></span> on your
system.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="part-Kernel_Module_and_Driver_Configuration.html">Part VII, “Kernel,
Module and Driver Configuration”</a></span></dt><dd><div
class="para">
+ This part covers various tools that assist administrators with kernel
customization.
+ </div><div class="para">
+ <a class="xref"
href="ch-Manually_Upgrading_the_Kernel.html">Chapter 20, <em>Manually
Upgrading the Kernel</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">Chapter 21, <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">Chapter 22,
<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="ch-RPM.html">Appendix A,
<em>RPM</em></a></span></dt><dd><div
class="para">
+ This appendix concentrates on the RPM Package Manager (RPM), an open packaging
system used by Fedora, and the use of the <code
class="command">rpm</code> utility. Read this appendix if you need to
use <code class="command">rpm</code> instead of <code
class="command">yum</code>.
+ </div></dd><dt class="varlistentry"><span
class="term"><a class="xref"
href="ch-The_sysconfig_Directory.html">Appendix B, <em>The sysconfig
Directory</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">Appendix C, <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>Prev</strong>Preface</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="pr01s03.html"><strong>Next</strong>3. Document
Conventions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Preface-Feedback.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Preface-Feedback.html
new file mode 100644
index 0000000..376d5cc
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-Preface-Feedback.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>4. Feedback</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="pr01.html" title="Preface" /><link rel="prev"
href="pr01s03s03.html" title="3.3. Notes and Warnings" /><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>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="pref-Acknowledgments.html"><strong>Next</strong></a></li>
</ul><div xml:lang="en-US" class="section"
id="sect-Preface-Feedback" lang="en-US"><div
class="titlepage"><div><div
keep-together.within-column="always"><h2 class="title"
id="sect-Preface-Feedback">4. Feedback</h2></div></div></div><a
id="id535472" 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">
+ When submitting a bug report, be sure to provide the following information:
+ </div><div class="itemizedlist"><ul><li
class="listitem"><div class="para">
+ Manual's identifier: <code
class="literal">deployment-guide</code>
+ </div></li><li class="listitem"><div
class="para">
+ Version number: <code class="literal">15</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>Prev</strong>3.3. Notes and
Warnings</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="pref-Acknowledgments.html"><strong>Next</strong>5. Acknowledgments</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html
new file mode 100644
index 0000000..3e562ef
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.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>8.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="prev"
href="chap-SSSD_User_Guide-Configuring_Domains.html"
title="8.2.5. Configuring Domains" /><link rel="next"
href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html"
title="8.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="pre
vious"><a accesskey="p"
href="chap-SSSD_User_Guide-Configuring_Domains.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html"><strong>Next</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"
id="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">8.2.6. Setting
Up Kerberos Authentication</h3></div></div></div><a
id="id603756" 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@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">Section 8.2.3.2.4.1,
“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"
id="sect-setting-up-sasl-gssapi-authentication">8.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="important"><div
class="admonition_header"><h2>Setting up the SASL/GSSAPI authentication
on Fedora 6.0</h2></div><div class="admonition"><div
class="para">
+ The following setup works correctly on all Fedora 6.1 systems and any systems
released after it. However, when using Fedora 6.0, you must correctly configure the
<code class="option">default_realm</code> option in the <code
class="option">[libdefaults]</code> section and <code
class="option">kdc</code> option for your realm in the <code
class="option">[realms]</code> section in the <code
class="filename">/etc/krb5.conf</code> configuration file not only on
the directory server and the KDC but also on the client running SSSD. For more information
on various <code class="filename">/etc/krb5.conf</code> options,
refer to <code class="command">man krb5.conf</code>
+ </div></div></div><div
class="variablelist"><dl><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><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(a)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>Prev</strong>8.2.5. Configuring
Domains</a></li><li class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html"><strong>Next</strong>8.2.7. Configuring
a Proxy Domain</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.html
new file mode 100644
index 0000000..d1f5c63
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain.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>8.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="prev"
href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"
title="8.2.6. Setting Up Kerberos Authentication" /><link
rel="next" href="chap-SSSD_User_Guide-Troubleshooting.html"
title="8.2.8. Troubleshooting" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site"
/></a></p><ul class="docnav"><li class="prev
ious"><a accesskey="p"
href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Troubleshooting.html"><strong>Next</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"
id="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">8.2.7. Configuring
a Proxy Domain</h3></div></div></div><a id="id572970"
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"
id="sect-SSSD-proxy-krb5">8.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">Section 8.2.6,
“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"
id="sect-SSSD-LDAP-proxy">8.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">Section 8.2.5.2,
“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"
id="sect-SSSD-proxy-proxy">8.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>Prev</strong>8.2.6. Setting
Up Kerberos Authentication</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Troubleshooting.html"><strong>Next</strong>8.2.8. Troubleshooting</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html
new file mode 100644
index 0000000..c6c312f
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.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>8.2.2. SSSD Features</title><link rel="stylesheet"
type="text/css" href="Common_Content/css/default.css" /><link
rel="stylesheet" media="print"
href="Common_Content/css/print.css" type="text/css" /><meta
name="generator" content="publican 2.5" /><meta
name="package" content="Fedora-Deployment_Guide-15-en-US-1-0"
/><script type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="prev"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="next"
href="chap-SSSD_User_Guide-Setting_Up_SSSD.html" title="8.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" href="chap-SS
SD_User_Guide-Introduction.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Setting_Up_SSSD.html"><strong>Next</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"
id="sect-SSSD_User_Guide-Introduction-SSSD_Features">8.2.2. SSSD
Features</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"
id="sect-SSSD_User_Guide-SSSD_Features-Offline_Authentication">8.2.2.1. Offline
Authentication</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"
id="sect-SSSD_User_Guide-SSSD_Features-Server_Load_Reduction">8.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"
id="sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">8.2.2.3. Support
for Multiple Domains</h4></div></div></div><a
id="id632380" 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="id632337">Considerations Associated with
Deleting Cache Files</h5><a id="id632332"
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"><div class="titlepage"><div><div
keep-together.within-column="always"><h4 class="title"
id="id632284">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id632282">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id632257">8.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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id632265">8.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"
id="sect-SSSD_User_Guide-SSSD_Features-Differentiating_Like_named_Users">8.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(a)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"
id="sect-SSSD_User_Guide-SSSD_Features-Integration_with_IPA">8.2.2.6. Integration
with 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"><div
class="titlepage"><div><div
keep-together.within-column="always"><h5 class="title"
id="id634549">8.2.2.6.1. Support for Dynamic DNS
Updates</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="id552764">Setting up Dynamic DNS
Updates</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>Prev</strong>8.2. The
System Security Services Daemon (SSSD)</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="chap-SSSD_User_Guide-Setting_Up_SSSD.html"><strong>Next</strong>8.2.3. Setting
Up SSSD</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html
new file mode 100644
index 0000000..513d570
--- /dev/null
+++
b/public_html/en-US/Fedora/15/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.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>8.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.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System
Security Services Daemon (SSSD)" /><link rel="prev"
href="chap-SSSD_User_Guide-Troubleshooting.html"
title="8.2.8. Troubleshooting" /><link rel="next"
href="ch-OpenSSH.html" title="Chapter 9. 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-Troubleshooting.html"><strong>Prev</s
trong></a></li><li class="next"><a
accesskey="n"
href="ch-OpenSSH.html"><strong>Next</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"
id="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">8.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>Prev</strong>8.2.8. Troubleshooting</a></li><li
class="up"><a accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="ch-OpenSSH.html"><strong>Next</strong>Chapter 9. OpenSSH</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/15/html/Deployment_Guide/testing-upload-method.html
b/public_html/en-US/Fedora/15/html/Deployment_Guide/testing-upload-method.html
new file mode 100644
index 0000000..b4b3a7b
--- /dev/null
+++ b/public_html/en-US/Fedora/15/html/Deployment_Guide/testing-upload-method.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"
standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html
xmlns="http://www.w3.org/1999/xhtml"><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>19.7.2. Testing the Upload Method</title><link
rel="stylesheet" type="text/css"
href="Common_Content/css/default.css" /><link rel="stylesheet"
media="print" href="Common_Content/css/print.css"
type="text/css" /><meta name="generator" content="publican
2.5" /><meta name="package"
content="Fedora-Deployment_Guide-15-en-US-1-0" /><script
type="text/javascript"
src="../../../../../toc.js"></script><script
type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.15');
+
+ addID('Fedora.15.books');
+ addID('Fedora.15.Deployment_Guide');
+ </script><link rel="home" href="index.html"
title="Deployment Guide" /><link rel="up"
href="configuring-centralized-crash-collection.html"
title="19.7. Configuring Centralized Crash Collection" /><link
rel="prev" href="configuring-centralized-crash-collection.html"
title="19.7. Configuring Centralized Crash Collection" /><link
rel="next" href="configuring-automatic-reporting.html"
title="19.8. Configuring Automatic Reporting" /></head><body
class="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a
class="left" href="http://www.fedoraproject.org"><img
src="Common_Content/images/image_left.png" alt="Product Site"
/></a><a class="right"
href="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="configuring-centralized-crash-collection.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n"
href="configuring-automatic-reporting.html"><strong>Next</strong></a></li></ul><div
class="section" id="testing-upload-method"><div
class="titlepage"><div><div
keep-together.within-column="always"><h3 class="title"
id="testing-upload-method">19.7.2. Testing the Upload
Method</h3></div></div></div><div class="para">
+ Test your upload method from a client system to ensure that it works. For example,
upload a file using the interactive <code
class="systemitem">FTP</code> client:
+ </div><pre class="screen">~]$ <code
class="command">ftp</code>
+ftp> open SERVERNAME
+Name: USERNAME
+Password: PASSWORD
+ftp> cd /var/spool/abrt-upload
+250 Operation successful
+ftp> put TESTFILE
+ftp> quit</pre><div class="para">
+ Check whether <code class="filename">TESTFILE</code> appeared
in the correct directory on the server system.
+ </div></div><ul class="docnav"><li
class="previous"><a accesskey="p"
href="configuring-centralized-crash-collection.html"><strong>Prev</strong>19.7. Configuring
Centralized Crash Collection</a></li><li class="up"><a
accesskey="u"
href="#"><strong>Up</strong></a></li><li
class="home"><a accesskey="h"
href="index.html"><strong>Home</strong></a></li><li
class="next"><a accesskey="n"
href="configuring-automatic-reporting.html"><strong>Next</strong>19.8. Configuring
Automatic Reporting</a></li></ul></body></html>
diff --git
a/public_html/en-US/Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf
b/public_html/en-US/Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf
new file mode 100644
index 0000000..cdb4175
Binary files /dev/null and
b/public_html/en-US/Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf
differ
diff --git a/public_html/en-US/opds-Fedora.xml b/public_html/en-US/opds-Fedora.xml
index af426e3..3da6b7a 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>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</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 873f18f..27cd469 100644
--- a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/en-US/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</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 5a43670..5342f8f 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>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</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 c99b28b..e14ed48 100644
--- a/public_html/en-US/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/en-US/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds.xml b/public_html/en-US/opds.xml
index 205666d..9af41a5 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>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/en-US/toc.html b/public_html/en-US/toc.html
index 89f286d..8328f3b 100644
--- a/public_html/en-US/toc.html
+++ b/public_html/en-US/toc.html
@@ -79,6 +79,14 @@
<div id='Fedora.15' class="version collapsed"
onclick="toggle(event, 'Fedora.15.books');">
<span class="version">15</span>
<div id='Fedora.15.books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book
collapsed">
+ <a class="type"
href="Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='./Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types"
onclick="work=0;">
+ <a class="type"
href="./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book
collapsed">
<a class="type"
href="Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='./Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types"
onclick="work=0;">
@@ -86,14 +94,6 @@
<a class="type"
href="./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book
collapsed">
- <a class="type"
href="Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='./Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types"
onclick="work=0;">
- <a class="type"
href="./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed">
<a class="type"
href="Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='./Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types"
onclick="work=0;">
@@ -780,7 +780,7 @@
<a class="type"
href="./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -991,7 +991,7 @@
<a class="type"
href="./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/es-ES/opds-Fedora.xml b/public_html/es-ES/opds-Fedora.xml
index 3d3db0b..4c0ea14 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>2011-05-24T13:34:14</updated>
+ <updated>2011-05-24T14:52:42</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 85be6bf..040e428 100644
--- a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:14</updated>
+ <updated>2011-05-24T14:52:42</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 d46ac65..588d21b 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>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</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 58933cb..c18a87d 100644
--- a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds.xml b/public_html/es-ES/opds.xml
index 2f3edd3..3bb0788 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>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:14</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:14</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/es-ES/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/es-ES/toc.html b/public_html/es-ES/toc.html
index ea42c91..2efa436 100644
--- a/public_html/es-ES/toc.html
+++ b/public_html/es-ES/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Aún sin traducir</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -190,7 +190,7 @@
<a class="type"
href="./Fedora/14/epub/Software_Management_Guide/Fedora-14-Software_Management_Guide-es-ES.epub"
>epub</a>
<a class="type"
href="./Fedora/14/html/Software_Management_Guide/index.html"
onclick="window.top.location='./Fedora/14/html/Software_Management_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/14/html-single/Software_Management_Guide/index.html"
onclick="window.top.location='./Fedora/14/html-single/Software_Management_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/14/pdf/Software_Management_Guide/Fedora-0.1-Software_Management_Guide-es-ES.pdf"
onclick="window.top.location='./Fedora/14/pdf/Software_Management_Guide/Fedora-0.1-Software_Management_Guide-es-ES.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/14/pdf/Software_Management_Guide/Fedora-14-Software_Management_Guide-es-ES.pdf"
onclick="window.top.location='./Fedora/14/pdf/Software_Management_Guide/Fedora-14-Software_Management_Guide-es-ES.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.14.User_Guide' class="book collapsed">
@@ -263,7 +263,7 @@
<a class="type"
href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.epub"
>epub</a>
<a class="type"
href="./Fedora/13/html/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/13/html-single/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-es-ES.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-es-ES.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book
collapsed">
@@ -625,7 +625,7 @@
<a class="type"
href="./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-es-ES.epub"
>epub</a>
<a class="type"
href="./Fedora/11/html/Security_Guide/index.html"
onclick="window.top.location='./Fedora/11/html/Security_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/11/html-single/Security_Guide/index.html"
onclick="window.top.location='./Fedora/11/html-single/Security_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-es-ES.pdf"
onclick="window.top.location='./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-es-ES.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-es-ES.pdf"
onclick="window.top.location='./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-es-ES.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed">
@@ -977,7 +977,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1223,7 +1223,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fa-IR/opds-Fedora.xml b/public_html/fa-IR/opds-Fedora.xml
index c172bf5..69064fb 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>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</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 1ac3597..83321cf 100644
--- a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Contributor_Documen...
<title>مستندات مشارکت کننده فدورا</title>
<subtitle>مستندات مشارکت کننده فدورا</subtitle>
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</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 0d020cf..82616bb 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>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</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 b1e43ee..7af7ecf 100644
--- a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds.xml b/public_html/fa-IR/opds.xml
index a72a386..ddeec54 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>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>مستندات مشارکت کننده فدورا</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/fa-IR/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fa-IR/toc.html b/public_html/fa-IR/toc.html
index 4e53520..60fb58c 100644
--- a/public_html/fa-IR/toc.html
+++ b/public_html/fa-IR/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -831,7 +831,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1077,7 +1077,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fi-FI/opds-Fedora.xml b/public_html/fi-FI/opds-Fedora.xml
index a329808..250e74b 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>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</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 42b623a..3e10a5d 100644
--- a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</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 f64211f..04076e9 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>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</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 8b59647..dacd9f6 100644
--- a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds.xml b/public_html/fi-FI/opds.xml
index 9ce6bae..3ca6065 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>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/fi-FI/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fi-FI/toc.html b/public_html/fi-FI/toc.html
index 867deb4..ecdacba 100644
--- a/public_html/fi-FI/toc.html
+++ b/public_html/fi-FI/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -535,7 +535,7 @@
<a class="type"
href="./Fedora/11/epub/Fedora_Live_images/Fedora-11-Fedora_Live_images-fi-FI.epub"
>epub</a>
<a class="type"
href="./Fedora/11/html/Fedora_Live_images/index.html"
onclick="window.top.location='./Fedora/11/html/Fedora_Live_images/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/11/html-single/Fedora_Live_images/index.html"
onclick="window.top.location='./Fedora/11/html-single/Fedora_Live_images/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/11/pdf/Fedora_Live_images/Fedora-13-Fedora_Live_Images-fi-FI.pdf"
onclick="window.top.location='./Fedora/11/pdf/Fedora_Live_images/Fedora-13-Fedora_Live_Images-fi-FI.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/11/pdf/Fedora_Live_images/Fedora-11-Fedora_Live_images-fi-FI.pdf"
onclick="window.top.location='./Fedora/11/pdf/Fedora_Live_images/Fedora-11-Fedora_Live_images-fi-FI.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.11' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.11.untrans_books');">
@@ -608,7 +608,7 @@
<a class="type"
href="./Fedora/10/epub/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-fi-FI.epub"
>epub</a>
<a class="type"
href="./Fedora/10/html/Fedora_Live_Images/index.html"
onclick="window.top.location='./Fedora/10/html/Fedora_Live_Images/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/10/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='./Fedora/10/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/10/pdf/Fedora_Live_Images/Fedora-13-Fedora_Live_Images-fi-FI.pdf"
onclick="window.top.location='./Fedora/10/pdf/Fedora_Live_Images/Fedora-13-Fedora_Live_Images-fi-FI.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/10/pdf/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-fi-FI.pdf"
onclick="window.top.location='./Fedora/10/pdf/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-fi-FI.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.10.Making_Fedora_Discs' class="book
collapsed">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fr-FR/opds-Fedora.xml b/public_html/fr-FR/opds-Fedora.xml
index ccb5e0b..8719d20 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>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</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 1d46b12..263c8d3 100644
--- a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</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 b9299cd..2710d60 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>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</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 cf150ea..3054b56 100644
--- a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds.xml b/public_html/fr-FR/opds.xml
index 3f80041..bb4b6a8 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>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/fr-FR/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fr-FR/toc.html b/public_html/fr-FR/toc.html
index 9d71b40..5a2d3bf 100644
--- a/public_html/fr-FR/toc.html
+++ b/public_html/fr-FR/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/gu-IN/opds-Fedora.xml b/public_html/gu-IN/opds-Fedora.xml
index 5d78315..227459f 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>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</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 4f151de..c95ab9e 100644
--- a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</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 21875e1..c9eeeca 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>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</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 426c87f..e297826 100644
--- a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds.xml b/public_html/gu-IN/opds.xml
index 4fb682d..60ca289 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>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/gu-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/gu-IN/toc.html b/public_html/gu-IN/toc.html
index dabe5da..9f6be49 100644
--- a/public_html/gu-IN/toc.html
+++ b/public_html/gu-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/he-IL/opds-Fedora.xml b/public_html/he-IL/opds-Fedora.xml
index a9242d5..9caf849 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>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</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 460744c..f6659d2 100644
--- a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</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 c3f97f7..00e6952 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>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</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 9b635b4..95e351c 100644
--- a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds.xml b/public_html/he-IL/opds.xml
index 057a45c..650f39f 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>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/he-IL/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/he-IL/toc.html b/public_html/he-IL/toc.html
index aa62cde..5989f6e 100644
--- a/public_html/he-IL/toc.html
+++ b/public_html/he-IL/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/hi-IN/opds-Fedora.xml b/public_html/hi-IN/opds-Fedora.xml
index 6b09d16..b997fb9 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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 11fff7f..0e67b95 100644
--- a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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 50d4aa9..26b309d 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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 e234f3c..3362945 100644
--- a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds.xml b/public_html/hi-IN/opds.xml
index 135c788..18686c2 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/hi-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/hi-IN/toc.html b/public_html/hi-IN/toc.html
index 6c99e4d..5377144 100644
--- a/public_html/hi-IN/toc.html
+++ b/public_html/hi-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/hu-HU/opds-Fedora.xml b/public_html/hu-HU/opds-Fedora.xml
index 3c4e797..69ac9c5 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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 bf94d73..6808fa6 100644
--- a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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 e55ff34..8c90c16 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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 e8ec4a4..854d0f6 100644
--- a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds.xml b/public_html/hu-HU/opds.xml
index bace18f..e81d19a 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/hu-HU/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/hu-HU/toc.html b/public_html/hu-HU/toc.html
index bc66e68..9885ed3 100644
--- a/public_html/hu-HU/toc.html
+++ b/public_html/hu-HU/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/id-ID/opds-Fedora.xml b/public_html/id-ID/opds-Fedora.xml
index 332808c..a516b06 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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 6df98d1..dfa3c90 100644
--- a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</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 6171467..7cd498c 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</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 fb224c5..44d48f8 100644
--- a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds.xml b/public_html/id-ID/opds.xml
index 513f96f..03ec023 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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/id-ID/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/id-ID/toc.html b/public_html/id-ID/toc.html
index 63ba991..41af582 100644
--- a/public_html/id-ID/toc.html
+++ b/public_html/id-ID/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/it-IT/opds-Fedora.xml b/public_html/it-IT/opds-Fedora.xml
index 6acc82d..1be36b6 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>2011-05-24T13:34:21</updated>
+ <updated>2011-05-24T14:52:43</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 3eb9e9b..f5786e3 100644
--- a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Contributor_Documen...
<title>Documentazione Collaboratori Fedora</title>
<subtitle>Documentazione Collaboratori Fedora</subtitle>
- <updated>2011-05-24T13:34:21</updated>
+ <updated>2011-05-24T14:52:43</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 1482514..0d5c907 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>2011-05-24T13:34:22</updated>
+ <updated>2011-05-24T14:52:43</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 f1a3711..f5d67a7 100644
--- a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:22</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds.xml b/public_html/it-IT/opds.xml
index ca778a8..8b76af1 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>2011-05-24T13:34:22</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:21</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Documentazione Collaboratori Fedora</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:21</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:22</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/it-IT/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:22</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/it-IT/toc.html b/public_html/it-IT/toc.html
index 1de1278..24b2173 100644
--- a/public_html/it-IT/toc.html
+++ b/public_html/it-IT/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -263,7 +263,7 @@
<a class="type"
href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-it-IT.epub"
>epub</a>
<a class="type"
href="./Fedora/13/html/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/13/html-single/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-it-IT.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-it-IT.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-it-IT.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-it-IT.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Fedora_Live_Images' class="book
collapsed">
@@ -995,7 +995,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1241,7 +1241,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ja-JP/opds-Fedora.xml b/public_html/ja-JP/opds-Fedora.xml
index 1c4a8d8..d9154f1 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>2011-05-24T13:34:23</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
index ff0aeeb..843b3be 100644
--- a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Contributor_Documen...
<title>Fedora コントリビュータ用ドキュメント</title>
<subtitle>Fedora コントリビュータ用ドキュメント</subtitle>
- <updated>2011-05-24T13:34:23</updated>
+ <updated>2011-05-24T14:52:43</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 9df08e1..258891d 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>2011-05-24T13:34:23</updated>
+ <updated>2011-05-24T14:52:43</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 5b41602..74cc7a7 100644
--- a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:23</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds.xml b/public_html/ja-JP/opds.xml
index af5d3f8..6f30a15 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>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:23</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora コントリビュータ用ドキュメント</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:23</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:23</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ja-JP/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:23</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ja-JP/toc.html b/public_html/ja-JP/toc.html
index a3bc2b6..f2607de 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">未翻訳</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/kn-IN/opds-Fedora.xml b/public_html/kn-IN/opds-Fedora.xml
index c33d0b5..c914b50 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>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</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 276c66f..4cd3d5d 100644
--- a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</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 ded2af6..b60e7d4 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>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</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 0543a48..23166b8 100644
--- a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds.xml b/public_html/kn-IN/opds.xml
index be6ab1d..656943a 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>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/kn-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/kn-IN/toc.html b/public_html/kn-IN/toc.html
index 2918ce6..b359196 100644
--- a/public_html/kn-IN/toc.html
+++ b/public_html/kn-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ko-KR/opds-Fedora.xml b/public_html/ko-KR/opds-Fedora.xml
index 472a1be..a79b836 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>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</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 df70c2f..da606d6 100644
--- a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</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 3c094e6..f5cd85d 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>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</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 1a1724e..7d3e763 100644
--- a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds.xml b/public_html/ko-KR/opds.xml
index 95b423e..ac81f28 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>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ko-KR/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ko-KR/toc.html b/public_html/ko-KR/toc.html
index c473e90..ce07b9c 100644
--- a/public_html/ko-KR/toc.html
+++ b/public_html/ko-KR/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ml-IN/opds-Fedora.xml b/public_html/ml-IN/opds-Fedora.xml
index 7d02c08..836a3ef 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>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</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 e668399..9f5b680 100644
--- a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</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 3a0b4f9..f3ad159 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>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</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 1edb3c4..5edf551 100644
--- a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds.xml b/public_html/ml-IN/opds.xml
index 94c3390..1ce2996 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>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ml-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ml-IN/toc.html b/public_html/ml-IN/toc.html
index 0ba133d..7e3751c 100644
--- a/public_html/ml-IN/toc.html
+++ b/public_html/ml-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/mr-IN/opds-Fedora.xml b/public_html/mr-IN/opds-Fedora.xml
index 8ef87d0..2e84dd1 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>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</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 31fbf07..8151aa0 100644
--- a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</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 6f526c4..f574c6f 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>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</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 2868596..6d7a1fc 100644
--- a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds.xml b/public_html/mr-IN/opds.xml
index 7ae2ded..9fa261c 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>2011-05-24T13:34:26</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/mr-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/mr-IN/toc.html b/public_html/mr-IN/toc.html
index bd8f411..8f8aa4d 100644
--- a/public_html/mr-IN/toc.html
+++ b/public_html/mr-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/nb-NO/opds-Fedora.xml b/public_html/nb-NO/opds-Fedora.xml
index 98bae5b..78aed1d 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>2011-05-24T13:34:27</updated>
+ <updated>2011-05-24T14:52:43</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 cbe37bf..dfa0a27 100644
--- a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:27</updated>
+ <updated>2011-05-24T14:52:43</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 4708845..466b83f 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>2011-05-24T13:34:27</updated>
+ <updated>2011-05-24T14:52:43</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 50540eb..ec805e5 100644
--- a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:27</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds.xml b/public_html/nb-NO/opds.xml
index 60d1144..8b0c277 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>2011-05-24T13:34:28</updated>
+ <updated>2011-05-24T14:52:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:27</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:27</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:27</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/nb-NO/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:27</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/nb-NO/toc.html b/public_html/nb-NO/toc.html
index 722e73f..98206fe 100644
--- a/public_html/nb-NO/toc.html
+++ b/public_html/nb-NO/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/nl-NL/opds-Fedora.xml b/public_html/nl-NL/opds-Fedora.xml
index 6f1dd4b..8313fda 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>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</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 697ce26..171b17c 100644
--- a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</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 53d6baa..70ae864 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>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</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 256f12d..01a0e65 100644
--- a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds.xml b/public_html/nl-NL/opds.xml
index 1125d99..72cf948 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>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/nl-NL/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/nl-NL/toc.html b/public_html/nl-NL/toc.html
index e534501..5f61dd4 100644
--- a/public_html/nl-NL/toc.html
+++ b/public_html/nl-NL/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Onvertaald</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -625,7 +625,7 @@
<a class="type"
href="./Fedora/11/epub/Security_Guide/Fedora-11-Security_Guide-nl-NL.epub"
>epub</a>
<a class="type"
href="./Fedora/11/html/Security_Guide/index.html"
onclick="window.top.location='./Fedora/11/html/Security_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/11/html-single/Security_Guide/index.html"
onclick="window.top.location='./Fedora/11/html-single/Security_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-nl-NL.pdf"
onclick="window.top.location='./Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-nl-NL.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-nl-NL.pdf"
onclick="window.top.location='./Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-nl-NL.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.11.User_Guide' class="book collapsed">
@@ -1013,7 +1013,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1259,7 +1259,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/opds.xml b/public_html/opds.xml
index 972ee8f..9179b33 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>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -16,7 +16,7 @@
<entry>
<title>অসমীয়া</title>
<id>as-IN/opds.xml</id>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bg-BG/opds.xml"/>
@@ -32,7 +32,7 @@
<entry>
<title>বাংলা</title>
<id>bn-IN/opds.xml</id>
- <updated>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:40</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>2011-05-24T13:34:07</updated>
+ <updated>2011-05-24T14:52:41</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>2011-05-24T13:34:08</updated>
+ <updated>2011-05-24T14:52:41</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>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</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>2011-05-24T13:34:09</updated>
+ <updated>2011-05-24T14:52:41</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>2011-05-24T13:34:10</updated>
+ <updated>2011-05-24T14:52:41</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>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</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>2011-05-24T13:34:11</updated>
+ <updated>2011-05-24T14:52:41</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>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</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>2011-05-24T13:34:15</updated>
+ <updated>2011-05-24T14:52:42</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>2011-05-24T13:34:16</updated>
+ <updated>2011-05-24T14:52:42</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>2011-05-24T13:34:17</updated>
+ <updated>2011-05-24T14:52:42</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>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</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>2011-05-24T13:34:18</updated>
+ <updated>2011-05-24T14:52:42</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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:42</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>Indonesia</title>
<id>id-ID/opds.xml</id>
- <updated>2011-05-24T13:34:19</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="id-ID/opds.xml"/>
@@ -168,7 +168,7 @@
<entry>
<title>Italiano</title>
<id>it-IT/opds.xml</id>
- <updated>2011-05-24T13:34:22</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="it-IT/opds.xml"/>
@@ -176,7 +176,7 @@
<entry>
<title>日本語</title>
<id>ja-JP/opds.xml</id>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ja-JP/opds.xml"/>
@@ -184,7 +184,7 @@
<entry>
<title>ಕನ್ನಡ</title>
<id>kn-IN/opds.xml</id>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="kn-IN/opds.xml"/>
@@ -192,7 +192,7 @@
<entry>
<title>한국어</title>
<id>ko-KR/opds.xml</id>
- <updated>2011-05-24T13:34:24</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ko-KR/opds.xml"/>
@@ -200,7 +200,7 @@
<entry>
<title>മലയാളം</title>
<id>ml-IN/opds.xml</id>
- <updated>2011-05-24T13:34:25</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ml-IN/opds.xml"/>
@@ -208,7 +208,7 @@
<entry>
<title>मराठी</title>
<id>mr-IN/opds.xml</id>
- <updated>2011-05-24T13:34:26</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="mr-IN/opds.xml"/>
@@ -216,7 +216,7 @@
<entry>
<title>Norsk (bokmål)</title>
<id>nb-NO/opds.xml</id>
- <updated>2011-05-24T13:34:28</updated>
+ <updated>2011-05-24T14:52:43</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nb-NO/opds.xml"/>
@@ -224,7 +224,7 @@
<entry>
<title>Nederlands</title>
<id>nl-NL/opds.xml</id>
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nl-NL/opds.xml"/>
@@ -232,7 +232,7 @@
<entry>
<title>ଓଡ଼ିଆ</title>
<id>or-IN/opds.xml</id>
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="or-IN/opds.xml"/>
@@ -240,7 +240,7 @@
<entry>
<title>ਪੰਜਾਬੀ</title>
<id>pa-IN/opds.xml</id>
- <updated>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pa-IN/opds.xml"/>
@@ -248,7 +248,7 @@
<entry>
<title>Polski</title>
<id>pl-PL/opds.xml</id>
- <updated>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pl-PL/opds.xml"/>
@@ -256,7 +256,7 @@
<entry>
<title>Português Brasileiro</title>
<id>pt-BR/opds.xml</id>
- <updated>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-BR/opds.xml"/>
@@ -264,7 +264,7 @@
<entry>
<title>Português</title>
<id>pt-PT/opds.xml</id>
- <updated>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-PT/opds.xml"/>
@@ -272,7 +272,7 @@
<entry>
<title>Русский</title>
<id>ru-RU/opds.xml</id>
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ru-RU/opds.xml"/>
@@ -280,7 +280,7 @@
<entry>
<title>Slovenščina</title>
<id>sk-SK/opds.xml</id>
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sk-SK/opds.xml"/>
@@ -288,7 +288,7 @@
<entry>
<title>Srpski (latinica)</title>
<id>sr-Latn-RS/opds.xml</id>
- <updated>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="sr-Latn-RS/opds.xml"/>
@@ -296,7 +296,7 @@
<entry>
<title>Српски</title>
<id>sr-RS/opds.xml</id>
- <updated>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-RS/opds.xml"/>
@@ -304,7 +304,7 @@
<entry>
<title>Svenska</title>
<id>sv-SE/opds.xml</id>
- <updated>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sv-SE/opds.xml"/>
@@ -312,7 +312,7 @@
<entry>
<title>தமிழ்</title>
<id>ta-IN/opds.xml</id>
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ta-IN/opds.xml"/>
@@ -320,7 +320,7 @@
<entry>
<title>తెలుగు</title>
<id>te-IN/opds.xml</id>
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="te-IN/opds.xml"/>
@@ -328,7 +328,7 @@
<entry>
<title>Українська</title>
<id>uk-UA/opds.xml</id>
- <updated>2011-05-24T13:34:48</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="uk-UA/opds.xml"/>
@@ -336,7 +336,7 @@
<entry>
<title>简体中文</title>
<id>zh-CN/opds.xml</id>
- <updated>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-CN/opds.xml"/>
@@ -344,7 +344,7 @@
<entry>
<title>繁體中文</title>
<id>zh-TW/opds.xml</id>
- <updated>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</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/opds-Fedora.xml b/public_html/or-IN/opds-Fedora.xml
index f5bd226..2f9bd1a 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>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</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 70ce968..4aafffa 100644
--- a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</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 12adbc7..2157b54 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>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</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 5175328..34d9148 100644
--- a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds.xml b/public_html/or-IN/opds.xml
index d604b74..ba75f1a 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>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/or-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:32</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/or-IN/toc.html b/public_html/or-IN/toc.html
index df2cd8b..24745f6 100644
--- a/public_html/or-IN/toc.html
+++ b/public_html/or-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pa-IN/opds-Fedora.xml b/public_html/pa-IN/opds-Fedora.xml
index f245195..658e28c 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>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</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 8fb0991..d49084c 100644
--- a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</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 3cd2e11..14e67eb 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>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</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 3e0d842..5aef7c1 100644
--- a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds.xml b/public_html/pa-IN/opds.xml
index dffdf2a..9d0c075 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>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/pa-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:33</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pa-IN/toc.html b/public_html/pa-IN/toc.html
index ceac308..45fa831 100644
--- a/public_html/pa-IN/toc.html
+++ b/public_html/pa-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pl-PL/opds-Fedora.xml b/public_html/pl-PL/opds-Fedora.xml
index f9f51db..c4618bd 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>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</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 31fff1e..e6820fc 100644
--- a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Contributor_Documen...
<title>Dokumentacja dla współtwórców Fedory</title>
<subtitle>Dokumentacja dla współtwórców Fedory</subtitle>
- <updated>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</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 cba24ba..e29d977 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>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</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 66ed633..61d2d53 100644
--- a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds.xml b/public_html/pl-PL/opds.xml
index b3aedf6..17ea04a 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>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Dokumentacja dla współtwórców Fedory</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/pl-PL/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:35</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pl-PL/toc.html b/public_html/pl-PL/toc.html
index 1482725..46d65b9 100644
--- a/public_html/pl-PL/toc.html
+++ b/public_html/pl-PL/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Nieprzetłumaczone</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -905,7 +905,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1151,7 +1151,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pt-BR/opds-Fedora.xml b/public_html/pt-BR/opds-Fedora.xml
index 594c318..261298b 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>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</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 b7abc5c..06003ad 100644
--- a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</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 363746e..3431231 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>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</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 caf83aa..df834b7 100644
--- a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds.xml b/public_html/pt-BR/opds.xml
index 8f09685..3d1e5c7 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>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/pt-BR/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:37</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pt-BR/toc.html b/public_html/pt-BR/toc.html
index 5605e46..7e34851 100644
--- a/public_html/pt-BR/toc.html
+++ b/public_html/pt-BR/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -842,7 +842,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1088,7 +1088,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pt-PT/opds-Fedora.xml b/public_html/pt-PT/opds-Fedora.xml
index 212f098..186e78b 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>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</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 654f4bd..54ad445 100644
--- a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</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 3e5f067..94e768a 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>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</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 b1c5792..9d2864f 100644
--- a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds.xml b/public_html/pt-PT/opds.xml
index 9463061..dae6290 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>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/pt-PT/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:39</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pt-PT/toc.html b/public_html/pt-PT/toc.html
index 2c86d92..d00b672 100644
--- a/public_html/pt-PT/toc.html
+++ b/public_html/pt-PT/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -263,7 +263,7 @@
<a class="type"
href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-pt-PT.epub"
>epub</a>
<a class="type"
href="./Fedora/13/html/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/13/html-single/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-pt-PT.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-pt-PT.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-pt-PT.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-pt-PT.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book
collapsed">
@@ -842,7 +842,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1078,7 +1078,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ru-RU/opds-Fedora.xml b/public_html/ru-RU/opds-Fedora.xml
index 1fb5981..995f05b 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>2011-05-24T13:34:40</updated>
+ <updated>2011-05-24T14:52:44</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 d042087..b11d84b 100644
--- a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Contributor_Documen...
<title>Документация участника Fedora</title>
<subtitle>Документация участника Fedora</subtitle>
- <updated>2011-05-24T13:34:40</updated>
+ <updated>2011-05-24T14:52:44</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 3193eb8..9aa498d 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>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:44</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 1da7e7f..726b5a6 100644
--- a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds.xml b/public_html/ru-RU/opds.xml
index bbb4d28..3e9c8a1 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>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:40</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Документация участника Fedora</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:40</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ru-RU/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:44</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ru-RU/toc.html b/public_html/ru-RU/toc.html
index ad0ca1d..cc32b0b 100644
--- a/public_html/ru-RU/toc.html
+++ b/public_html/ru-RU/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Не переведено</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sk-SK/opds-Fedora.xml b/public_html/sk-SK/opds-Fedora.xml
index 8b63d09..eb400ab 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>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</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 3bd670e..6c56dcb 100644
--- a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</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 85afa72..5f66013 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>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</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 d12b411..ca6a42b 100644
--- a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds.xml b/public_html/sk-SK/opds.xml
index 3ca7ec0..4a30479 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>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/sk-SK/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:41</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sk-SK/toc.html b/public_html/sk-SK/toc.html
index 728fd86..bc98385 100644
--- a/public_html/sk-SK/toc.html
+++ b/public_html/sk-SK/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sr-Latn-RS/opds-Fedora.xml
b/public_html/sr-Latn-RS/opds-Fedora.xml
index ad8dab0..7a68bfc 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>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</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 9346849..dfa1822 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Contributor_Do...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</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 6baa80f..d193c75 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Core.xml</i...
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</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 0aa8033..d6c7d92 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Draft_Document...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</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 a4467d3..477dd37 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>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora/opds-Fedora.xml<...
- <updated>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Contributor_Documen...
- <updated>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Core/opds-Fedora_Co...
- <updated>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Draft_Documentation...
- <updated>2011-05-24T13:34:42</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sr-Latn-RS/toc.html b/public_html/sr-Latn-RS/toc.html
index 5abaea6..7735cd7 100644
--- a/public_html/sr-Latn-RS/toc.html
+++ b/public_html/sr-Latn-RS/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sr-RS/opds-Fedora.xml b/public_html/sr-RS/opds-Fedora.xml
index 8e1b66c..20e8b2f 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>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</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 a7c41a3..a7e30c1 100644
--- a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</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 5501ab4..d3fc645 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>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</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 aa7b7cf..ecb2b12 100644
--- a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds.xml b/public_html/sr-RS/opds.xml
index 62ce135..6abcef8 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>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/sr-RS/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:44</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sr-RS/toc.html b/public_html/sr-RS/toc.html
index b5805ca..1bfa418 100644
--- a/public_html/sr-RS/toc.html
+++ b/public_html/sr-RS/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -842,7 +842,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1088,7 +1088,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sv-SE/opds-Fedora.xml b/public_html/sv-SE/opds-Fedora.xml
index 0cabfb1..4317cf1 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>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</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 c2c1462..977ea52 100644
--- a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</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 86da02b..16956bf 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>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</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 f20f1a0..420ada3 100644
--- a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds.xml b/public_html/sv-SE/opds.xml
index fc311c2..d7d5186 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>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/sv-SE/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:45</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sv-SE/toc.html b/public_html/sv-SE/toc.html
index 15c2129..670c1bf 100644
--- a/public_html/sv-SE/toc.html
+++ b/public_html/sv-SE/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -878,7 +878,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1124,7 +1124,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ta-IN/opds-Fedora.xml b/public_html/ta-IN/opds-Fedora.xml
index 8de57dc..1ecda38 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>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</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 aca0f2a..a425fc8 100644
--- a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</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 6e01739..2cedf71 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>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</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 4b38bec..b0acdee 100644
--- a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds.xml b/public_html/ta-IN/opds.xml
index 178bde9..b89a342 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>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/ta-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ta-IN/toc.html b/public_html/ta-IN/toc.html
index a48eda5..d545fe5 100644
--- a/public_html/ta-IN/toc.html
+++ b/public_html/ta-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/te-IN/opds-Fedora.xml b/public_html/te-IN/opds-Fedora.xml
index c81e0de..cfc1fcc 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>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</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 06f9de4..bb9cfcc 100644
--- a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</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 1cd324e..d8d14aa 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>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</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 3750495..669f891 100644
--- a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds.xml b/public_html/te-IN/opds.xml
index e525de0..aa36c58 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>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/te-IN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:46</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/te-IN/toc.html b/public_html/te-IN/toc.html
index a359a69..35591c7 100644
--- a/public_html/te-IN/toc.html
+++ b/public_html/te-IN/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/toc.html b/public_html/toc.html
index d127655..aed6775 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -1233,25 +1233,25 @@
<span class="version">15</span> <div
class="books">
<div class="book">
- <span id="Fedora_Live_Images" class="book">Fedora Live
Images</span>
+ <span id="Deployment_Guide" class="book">Deployment
Guide</span>
<div class="types">
- <a class="type"
href="./en-US/Fedora/15/html/Fedora_Live_Images/index.html">html</a>
+ <a class="type"
href="./en-US/Fedora/15/html/Deployment_Guide/index.html">html</a>
- <a class="type"
href="./en-US/Fedora/15/html-single/Fedora_Live_Images/index.html">html-single</a>
+ <a class="type"
href="./en-US/Fedora/15/html-single/Deployment_Guide/index.html">html-single</a>
+
+ <a class="type"
href="./en-US/Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf">pdf</a>
</div>
</div>
<div class="book">
- <span id="Installation_Guide" class="book">Installation
Guide</span>
+ <span id="Fedora_Live_Images" class="book">Fedora Live
Images</span>
<div class="types">
- <a class="type"
href="./en-US/Fedora/15/html/Installation_Guide/index.html">html</a>
-
- <a class="type"
href="./en-US/Fedora/15/html-single/Installation_Guide/index.html">html-single</a>
+ <a class="type"
href="./en-US/Fedora/15/html/Fedora_Live_Images/index.html">html</a>
- <a class="type"
href="./en-US/Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf">pdf</a>
+ <a class="type"
href="./en-US/Fedora/15/html-single/Fedora_Live_Images/index.html">html-single</a>
</div>
</div>
@@ -2349,7 +2349,7 @@
<a class="type"
href="./en-US/Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html">html-single</a>
- <a class="type"
href="./en-US/Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf">pdf</a>
+ <a class="type"
href="./en-US/Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -2656,7 +2656,7 @@
<a class="type"
href="./en-US/Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html">html-single</a>
- <a class="type"
href="./en-US/Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf">pdf</a>
+ <a class="type"
href="./en-US/Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -2822,7 +2822,7 @@
<a class="type"
href="./es-ES/Fedora/14/html-single/Software_Management_Guide/index.html">html-single</a>
- <a class="type"
href="./es-ES/Fedora/14/pdf/Software_Management_Guide/Fedora-0.1-Software_Management_Guide-es-ES.pdf">pdf</a>
+ <a class="type"
href="./es-ES/Fedora/14/pdf/Software_Management_Guide/Fedora-14-Software_Management_Guide-es-ES.pdf">pdf</a>
</div>
</div>
@@ -2855,7 +2855,7 @@
<a class="type"
href="./es-ES/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type"
href="./es-ES/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-es-ES.pdf">pdf</a>
+ <a class="type"
href="./es-ES/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.pdf">pdf</a>
</div>
</div>
@@ -3281,7 +3281,7 @@
<a class="type"
href="./es-ES/Fedora/11/html-single/Security_Guide/index.html">html-single</a>
- <a class="type"
href="./es-ES/Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-es-ES.pdf">pdf</a>
+ <a class="type"
href="./es-ES/Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-es-ES.pdf">pdf</a>
</div>
</div>
@@ -3799,7 +3799,7 @@
<a class="type"
href="./fi-FI/Fedora/11/html-single/Fedora_Live_images/index.html">html-single</a>
- <a class="type"
href="./fi-FI/Fedora/11/pdf/Fedora_Live_images/Fedora-13-Fedora_Live_Images-fi-FI.pdf">pdf</a>
+ <a class="type"
href="./fi-FI/Fedora/11/pdf/Fedora_Live_images/Fedora-11-Fedora_Live_images-fi-FI.pdf">pdf</a>
</div>
</div>
@@ -3817,7 +3817,7 @@
<a class="type"
href="./fi-FI/Fedora/10/html-single/Fedora_Live_Images/index.html">html-single</a>
- <a class="type"
href="./fi-FI/Fedora/10/pdf/Fedora_Live_Images/Fedora-13-Fedora_Live_Images-fi-FI.pdf">pdf</a>
+ <a class="type"
href="./fi-FI/Fedora/10/pdf/Fedora_Live_Images/Fedora-10-Fedora_Live_Images-fi-FI.pdf">pdf</a>
</div>
</div>
@@ -4737,7 +4737,7 @@
<a class="type"
href="./it-IT/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type"
href="./it-IT/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-it-IT.pdf">pdf</a>
+ <a class="type"
href="./it-IT/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-it-IT.pdf">pdf</a>
</div>
</div>
@@ -6603,7 +6603,7 @@
<a class="type"
href="./nl-NL/Fedora/11/html-single/Security_Guide/index.html">html-single</a>
- <a class="type"
href="./nl-NL/Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-nl-NL.pdf">pdf</a>
+ <a class="type"
href="./nl-NL/Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-nl-NL.pdf">pdf</a>
</div>
</div>
@@ -7962,7 +7962,7 @@
<a class="type"
href="./pt-PT/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type"
href="./pt-PT/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-pt-PT.pdf">pdf</a>
+ <a class="type"
href="./pt-PT/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-pt-PT.pdf">pdf</a>
</div>
</div>
@@ -10201,7 +10201,7 @@
<a class="type"
href="./uk-UA/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type"
href="./uk-UA/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-uk-UA.pdf">pdf</a>
+ <a class="type"
href="./uk-UA/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-uk-UA.pdf">pdf</a>
</div>
</div>
@@ -10600,7 +10600,7 @@
<a class="type"
href="./zh-CN/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type"
href="./zh-CN/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-zh-CN.pdf">pdf</a>
+ <a class="type"
href="./zh-CN/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-zh-CN.pdf">pdf</a>
</div>
</div>
diff --git a/public_html/uk-UA/opds-Fedora.xml b/public_html/uk-UA/opds-Fedora.xml
index c5ef6d0..378d264 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>2011-05-24T13:34:47</updated>
+ <updated>2011-05-24T14:52:45</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 5730da4..8ae60b8 100644
--- a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Contributor_Documen...
<title>Документація для учасника розробки Fedora</title>
<subtitle>Документація для учасника розробки Fedora</subtitle>
- <updated>2011-05-24T13:34:47</updated>
+ <updated>2011-05-24T14:52:45</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 a3f73d6..9b688ce 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>2011-05-24T13:34:47</updated>
+ <updated>2011-05-24T14:52:45</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 2c52851..0303074 100644
--- a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:47</updated>
+ <updated>2011-05-24T14:52:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds.xml b/public_html/uk-UA/opds.xml
index 225b6ed..2b40db6 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>2011-05-24T13:34:48</updated>
+ <updated>2011-05-24T14:52:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:47</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Документація для учасника розробки Fedora</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:47</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:47</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/uk-UA/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:47</updated>
+ <updated>2011-05-24T14:52:45</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/uk-UA/toc.html b/public_html/uk-UA/toc.html
index 007c08a..cd62d06 100644
--- a/public_html/uk-UA/toc.html
+++ b/public_html/uk-UA/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Не перекладено</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -263,7 +263,7 @@
<a class="type"
href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-uk-UA.epub"
>epub</a>
<a class="type"
href="./Fedora/13/html/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/13/html-single/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-uk-UA.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-uk-UA.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-uk-UA.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-uk-UA.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book
collapsed">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/zh-CN/opds-Fedora.xml b/public_html/zh-CN/opds-Fedora.xml
index cd5b353..2aacbd0 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>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</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 6adbbc9..580ec2d 100644
--- a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</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 0f836f5..6f68883 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>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</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 aed9ea4..7271a8e 100644
--- a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds.xml b/public_html/zh-CN/opds.xml
index a6cb6a0..07cfbe0 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>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/zh-CN/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:49</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/zh-CN/toc.html b/public_html/zh-CN/toc.html
index 4e8b9f0..4781c76 100644
--- a/public_html/zh-CN/toc.html
+++ b/public_html/zh-CN/toc.html
@@ -89,12 +89,12 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
@@ -263,7 +263,7 @@
<a class="type"
href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-zh-CN.epub"
>epub</a>
<a class="type"
href="./Fedora/13/html/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html/Accessibility_Guide/index.html';return
false;">html</a>
<a class="type"
href="./Fedora/13/html-single/Accessibility_Guide/index.html"
onclick="window.top.location='./Fedora/13/html-single/Accessibility_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-zh-CN.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-zh-CN.pdf';return
false;">pdf</a>
+ <a class="type"
href="./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-zh-CN.pdf"
onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-zh-CN.pdf';return
false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book
collapsed">
@@ -905,7 +905,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1151,7 +1151,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/zh-TW/opds-Fedora.xml b/public_html/zh-TW/opds-Fedora.xml
index ab035b1..e32e248 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>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</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 3d49d8b..651a519 100644
--- a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Contributor_Documen...
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</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 23c5c27..72006d1 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>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</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 f359841..650c229 100644
--- a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<
id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Draft_Documentation...
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml
index 7bc6b24..3404287 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>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora/opds-Fedora.xml</id>
- <updated>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora_Contributor_Documentatio...
- <updated>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora_Core/opds-Fedora_Core.xm...
- <updated>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<
id>http://docs.fedoraproject.org/zh-TW/Fedora_Draft_Documentation/opds...
- <updated>2011-05-24T13:34:50</updated>
+ <updated>2011-05-24T14:52:46</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml"
href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/zh-TW/toc.html b/public_html/zh-TW/toc.html
index 3ab0d88..c0f13bb 100644
--- a/public_html/zh-TW/toc.html
+++ b/public_html/zh-TW/toc.html
@@ -82,6 +82,14 @@
<div id='Fedora.15' class="version collapsed untranslated"
onclick="toggle(event, 'Fedora.15.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora.15.untrans_books' class="books hidden">
+ <div id='Fedora.15.Deployment_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
+ <a class="type"
href="../en-US/Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Deployment_Guide/index.html'"><span
class="book">Deployment Guide</span></a>
+ <div id='Fedora.15.Deployment_Guide.types' class="types
hidden" onclick="work=0;">
+ <a class="type"
href="../en-US/./Fedora/15/html/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Deployment_Guide/index.html';return
false;">html</a>
+ <a class="type"
href="../en-US/./Fedora/15/html-single/Deployment_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Deployment_Guide/index.html';return
false;">html-single</a>
+ <a class="type"
href="../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Deployment_Guide/Fedora-15-Deployment_Guide-en-US.pdf';return
false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Fedora_Live_Images.types');">
<a class="type"
href="../en-US/Fedora/15/html/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Fedora_Live_Images/index.html'"><span
class="book">Fedora Live Images</span></a>
<div id='Fedora.15.Fedora_Live_Images.types' class="types
hidden" onclick="work=0;">
@@ -89,14 +97,6 @@
<a class="type"
href="../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Fedora_Live_Images/index.html';return
false;">html-single</a>
</div>
</div>
- <div id='Fedora.15.Installation_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Installation_Guide.types');">
- <a class="type"
href="../en-US/Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Installation_Guide/index.html'"><span
class="book">Installation Guide</span></a>
- <div id='Fedora.15.Installation_Guide.types' class="types
hidden" onclick="work=0;">
- <a class="type"
href="../en-US/./Fedora/15/html/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html/Installation_Guide/index.html';return
false;">html</a>
- <a class="type"
href="../en-US/./Fedora/15/html-single/Installation_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora/15/html-single/Installation_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora/15/pdf/Installation_Guide/Fedora-15-Installation_Guide-en-US.pdf';return
false;">pdf</a>
- </div>
- </div>
<div id='Fedora.15.Musicians_Guide' class="book collapsed"
onclick="toggle(event, 'Fedora.15.Musicians_Guide.types');">
<a class="type"
href="../en-US/Fedora/15/html/Musicians_Guide/index.html"
onclick="window.top.location='../en-US/Fedora/15/html/Musicians_Guide/index.html'"><span
class="book">Musicians Guide</span></a>
<div id='Fedora.15.Musicians_Guide.types' class="types
hidden" onclick="work=0;">
@@ -833,7 +833,7 @@
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/epub/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Users_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Users_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>
@@ -1079,7 +1079,7 @@
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/epub/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.epub"
>epub</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html/OpenSSH_Guide/index.html';return
false;">html</a>
<a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/html-single/OpenSSH_Guide/index.html';return
false;">html-single</a>
- <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.2-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
+ <a class="type"
href="../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf"
onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.2/pdf/OpenSSH_Guide/Fedora_Draft_Documentation-0.1-OpenSSH_Guide-en-US.pdf';return
false;">pdf</a>
</div>
</div>
</div>